- From: Simon Pieters <simonp@opera.com>
- Date: Wed, 13 Jun 2012 18:24:56 +0200
- To: "Boris Zbarsky" <bzbarsky@mit.edu>
- Cc: whatwg@lists.whatwg.org
On Wed, 13 Jun 2012 18:09:22 +0200, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 6/13/12 4:55 AM, Simon Pieters wrote: >> If it redirects, it switches to CORS. However, there are some bugs in >> the spec... I just filed >> https://www.w3.org/Bugs/Public/show_bug.cgi?id=17478 now. > > Can we push this whole algorithm down into the CORS spec? It looks like > at this point fetching-resources.html and the XHR spec are both trying > to define the same algorithm (no CORS for same-origin, check origin on > redirect, switch to CORS as needed, etc), and it would be pretty nice if > they ended up actually defining it the same way. Simplest way to do > that is to define it in the CORS spec and just reference it in the > others, I'd think. Yeah or maybe even merge this algorithm, the fetch algorithm, and the cross-origin request algorithms. Currently it's extremely hard to follow. -- Simon Pieters Opera Software
Received on Wednesday, 13 June 2012 16:24:13 UTC