17305 2012-06-04 13:28:28 +0000 No CORS and not-same-origin should not fetch the URL 2012-08-29 19:32:09 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#potentially-cors-enabled-fetch P3 normal Unsorted 1 contributor ian ian mike zcorpan contributor oldest_to_newest 68566 0 contributor 2012-06-04 13:28:28 +0000 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 68567 1 zcorpan 2012-06-04 13:37:25 +0000 When failure mode is "fail" and mode is "No CORS", we shouldn't fetch anything at all but just fail directly. 68620 2 zcorpan 2012-06-05 07:31:57 +0000 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. 70897 3 contributor 2012-07-18 17:42:42 +0000 This bug was cloned to create bug 18215 as part of operation convergence. 71569 4 ian 2012-07-27 03:12:50 +0000 Can you elaborate? 72194 5 zcorpan 2012-08-15 09:33:01 +0000 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>.