This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/fetching-resources.html Multipage: http://www.whatwg.org/C#potentially-cors-enabled-fetch Complete: http://www.whatwg.org/c#potentially-cors-enabled-fetch Comment: No CORS and not-same-origin should not fetch the URL 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
When failure mode is "fail" and mode is "No CORS", we shouldn't fetch anything at all but just fail directly.
Similarly, if /default/ is "fail", and /mode/ is "No CORS", and /URL/ is a same-origin URL that redirects to a different-origin URL, the redirect shouldn't be followed but should fail at that point.
This bug was cloned to create bug 18215 as part of operation convergence.
Can you elaborate?
When /default/ is "fail", we don't want to waste network resources on fetches we know we're not going to accept. This also applies in case of redirects. This came up as part of implementing <track>.