Re: [whatwg/fetch] Redirected range requests and preflights. (#145)

https://jewel-chair.glitch.me/same-origin.html

* Contains an `<audio>` that points to `/audio-redirect-second-part`.
* If the request has a `Range` that starts at an offset other than 0, the server redirects to `/audio-normal`.

**Chrome**: Observes the redirect. Subsequent requests go to `/audio-normal`.
**Firefox**: Observes the redirect. Subsequent requests go to `/audio-redirect-second-part`.

https://jewel-chair.glitch.me/same-origin-immediate-redirect.html

* Contains an `<audio>` that points to `/audio-redirect-first-part`.
* Always redirects to `/audio-normal`.

**Chrome**: Observes the redirect. Subsequent requests go to `/audio-normal`.
**Firefox**: Observes the redirect. Subsequent requests go to `/audio-normal`.

I'm looking to spec the correct behaviour here, and I'd like to do the same for other range requests like downloads.

Initially, the Firefox behaviour seems inconsistent. But, if a browser were to request multiple ranges in parallel, Chrome's behaviour could be racey.

I'm not familiar with the CDN pattern @tyoshino mentioned. Are there any further details? Do these CDNs tend to redirect for the initial range, or do they perform multiple redirects for different parts of the media resource?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/145#issuecomment-370757789