17317 2012-06-05 06:15:44 +0000 Consider mode being "No CORS" and URL is same-origin. The fetch results in a redirect whose URL is also same-origin. The spec says to apply the CORS "redirect steps". Shouldn't it do the redirect without CORS when it's same-origin? 2012-08-29 19:40:26 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#cors-enabled-fetch P3 normal Unsorted 1 contributor ian fs ian mike odinho zcorpan contributor oldest_to_newest 68617 0 contributor 2012-06-05 06:15:44 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/fetching-resources.html Multipage: http://www.whatwg.org/C#cors-enabled-fetch Complete: http://www.whatwg.org/c#cors-enabled-fetch Comment: Consider mode being "No CORS" and URL is same-origin. The fetch results in a redirect whose URL is also same-origin. The spec says to apply the CORS "redirect steps". Shouldn't it do the redirect without CORS when it's same-origin? Posted from: 85.227.152.202 by simonp@opera.com User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.7.3; U; en) Presto/2.10.229 Version/11.64 68618 1 zcorpan 2012-06-05 06:17:05 +0000 (or mode being anything actually, since same-origin takes the first branch anyway) 69588 2 zcorpan 2012-07-03 12:26:00 +0000 *** Bug 17478 has been marked as a duplicate of this bug. *** 69589 3 zcorpan 2012-07-03 12:27:07 +0000 Even without the redirect, the spec seems to say to perform the resource sharing check for same-origin No CORS fetch, which is clearly wrong. 71021 4 contributor 2012-07-18 17:56:03 +0000 This bug was cloned to create bug 18277 as part of operation convergence.