Bug 167521 – Cross-origin redirects with preflight should be allowed

• Component: Page Loading
• Status: RESOLVED FIXED

[Joey Parrish]

In August 2016, the Fetch spec was updated [1] to allow cross-origin HTTP redirects, even w/ preflight requests.  All major browsers except Safari and Firefox have implemented the change.  This is preventing users of Shaka Player from using HTTP redirects for load balancing [2].  Media applications that do this kind of load balancing currently cannot be run in Safari.

To reproduce, simply load the repro page [3] in Safari and wait a few seconds for the request to fire.  You should see "OK, status = 200", indicating that the cross-origin redirect was followed.  In Safari, you see "FAILED", indicating that the redirect was not allowed by the browser.

[1] https://github.com/whatwg/fetch/commit/0d9a4db8bc02251cc9e391543bb3c1322fb882f2
[2] https://github.com/google/shaka-player/issues/666
[3] http://storage.googleapis.com/shaka-demo-assets/_bugs/cors_redirect/index.html

[youenn fablet]

Thanks for the feedback.
Have you tried in latest Safari/latest STP?

[Joey Parrish]

Sorry, no, I have not tried in anything but Safari Version 10.0.2 (12602.3.12.0.1).  I will grab a WebKit nightly and see if it's fixed there.

[youenn fablet]

Safari tech preview should be good enough

[Joey Parrish]

Tested again in WebKit nightly r211339.  It is working there.  I should have tested that before I filed the original report.

Is this a feature that could be released in an update to Safari 10?  Or will it have to wait for Safari 11?

Thanks!

[youenn fablet]

> Is this a feature that could be released in an update to Safari 10?  Or will
> it have to wait for Safari 11?

Not exactly sure when this change was introduced.
I would think this would be aligned with fetch API implementation.

I'll close the bug. Do not hesitate to reopen it if needed.