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

@horo-t @mikewest it seems Chrome has the strictest handling of media element range requests thanks to your efforts:

* For the initial request, redirects are followed, resulting in an opaque response at a "final URL".
* Subsequent requests are made directly to the "final URL". If this "final URL" redirects:
   * If the redirect crosses the origin boundary, error. (Firefox has this too, though it does not make subsequent requests directly to the "final URL".)
   * If the redirect does not end up at the "final URL" (e.g., directly or via another redirect), error. (Firefox does not have this.)

Given that rather weird behavior it seems we might be able to outlaw redirects for subsequent requests completely. This would also help https://github.com/annevk/orb, though it does not matter much. Is there a reason they are allowed? And if not, are you interested in simplifying that logic?

cc @padenot @anforowicz 

-- 
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-763703497