[Bug 8866] definition of "same-origin policy"

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8866


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




--- Comment #2 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-02-14 11:23:07 ---
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the tracker issue; or you may create a tracker issue
yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Partially Accepted
Change Description: see diff given below
Rationale: I removed that mention of the "same-origin policy", since it really
wasn't helping anything, and replaced it with a more helpful brief statement
explaining the implications of doing this.

I haven't defined "same-origin policy" anywhere because I really have no idea
how to do so. The whole HTML spec plus other specs like CORS, Web Storage, the
Web Sockets protocol, etc, together describe the same-origin policy. It's not
something that can be summarised in a few paragraphs.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Sunday, 14 February 2010 11:23:09 UTC