- From: Rik Cabanier <cabanier@gmail.com>
- Date: Fri, 7 Jun 2013 04:15:00 -0700
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: WHATWG <whatwg@whatwg.org>
Hi Anne, Your specification contains the following [1]: A response is either CORS-same-origin or CORS-cross-origin. Unless otherwise indicated a response is CORS-same-origin. but it doesn't say what the difference is between the two. The 'CO' in CORS stands for 'cross origin' so 'CORS-same-origin' would mean 'cross origin sharing for the same origin' which sounds a bit strange. 1: http://fetch.spec.whatwg.org/#cors-same-origin On Wed, May 22, 2013 at 2:50 AM, Anne van Kesteren <annevk@annevk.nl> wrote: > I'm reaching the point where I want to start integrating > http://fetch.spec.whatwg.org/ into http://xhr.spec.whatwg.org/ so I > can remove a lot of the duplicate requirements with respect to > networking and at the same time clarify a lot of the networking > behavior. > > And although http://fetch.spec.whatwg.org/ is pretty dry reading it > would be good if people could take a look at it as the idea is for it > to define the fetching behavior across the platform. This task is > currently divided between HTML, CORS, Web Origin Concept, and CSP > (integration hooks not yet in Fetch) and creates a real messy > situation for specifications building on top of them. The idea is to > remove that complexity and have a simple hook for fetching a request > and get a response in return. > > > -- > http://annevankesteren.nl/ >
Received on Friday, 7 June 2013 11:15:38 UTC