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

I haven't given this any though in the spec, no. What I do know is that media elements integrate with the network layer in a rather unique way, that seems to be true of all implementations, and certainly was in Presto.

The problem of knowing that the resource is the same when requesting a second range isn't unique to redirects, even when the same server responds you in principle need some sanity checks. I doubt that these are interoperable today, and I doubt even more that doing the strict checks that would actually make sense (ETag) would actually be web compatible.

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