A CORS-preflight can be followed by a redirect these days. See also: * https://bugzilla.mozilla.org/show_bug.cgi?id=918767 * https://bugs.chromium.org/p/chromium/issues/detail?id=580796 * https://github.com/w3c/web-platform-tests/issues/2520
Created attachment 286571 [details] Patch
Should this be r?
Comment on attachment 286571 [details] Patch There is no test checking valid XHR preflighting after cross-origin redirections. But the fetch API tests cover successful (and failing) preflighting after cross-origin redirections. Since the code between fetch and XHR is common, this is probably sufficient. Marking patch as r?.
Made a PR to W3C WPT tests at https://github.com/w3c/web-platform-tests/pull/3523 Same tests as in the patch with some minor style tweaks.
Comment on attachment 286571 [details] Patch Clearing flags on attachment: 286571 Committed r204795: <http://trac.webkit.org/changeset/204795>
All reviewed patches have been landed. Closing bug.