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

Doing it generically would indeed be very broken.

To do this for a specific application (e.g., HTMLMediaElement), you need a *really* explicit assertion that not only are the two resources equivalent, but also that the two specific representations are exactly the same -- e.g., ETag sharing. Even then, this is not something happening in HTTP -- it has to be built on top.

See:
  http://httpwg.github.io/specs/rfc7233.html#combining.byte.ranges
  http://httpwg.github.io/specs/rfc7234.html#combining.responses

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/145#issuecomment-152111909