Re: [ServiceWorker] Receivers of ranged responses must ensure all ranges come from the same underlying resource (#703)

@annevk I think the audio/video element (or other consumer) will be generating the Range headers in this situation. 

There's another use case where they're generated in cache/network, but that's when the HTTP cache has a partial response already there and it wants to "fill it in." When that happens, it really is opaque to SW and the API, because the response is a 200 (unless the API asked for a partial response to begin with, see above).

I think this needs to be updated with the outcome of discussion at TPAC...

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/703#issuecomment-155997563