18215 2012-07-18 17:42:38 +0000 No CORS and not-same-origin should not fetch the URL 2013-09-16 22:43:38 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#potentially-cors-enabled-fetch CR P3 normal --- 1 contributor silviapfeiffer1 mike public-html-admin public-html-wg-issue-tracking robin travil zcorpan public-html-bugzilla oldest_to_newest 70896 0 contributor 2012-07-18 17:42:38 +0000 This was was cloned from bug 17305 as part of operation convergence. Originally filed: 2012-06-04 13:28:00 +0000 ================================================================================ #0 contributor@whatwg.org 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 ================================================================================ #1 Simon Pieters 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. ================================================================================ #2 Simon Pieters 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. ================================================================================ 93461 1 travil 2013-09-16 22:43:38 +0000 Was resolved fixed (a year ago) by Ian. The relevant checkin was: https://github.com/w3c/html/commit/ebcd9542f528d983ebe9bbcaa3823001b6448f4f which has subsequently been integrated over in Robin's mega-merge early this year.