Re: [fetch] Response content-length header almost always wrong (#67)

Yeah, HTTP range requests were the other thing I was thinking about, particularly as they relate to the use of MPEG DASH (which, depending on the serving infrastructure, may either use multiple separate URLs for chunks or use Range requests with a single streaming URL). If you wanted to, say, allow offline streaming (ignoring the ever looming DRM question for 'meaningful' streaming), how would developers want to interact with the Cache, versus what are the security implications of allowing SW control over Range requests (there have been interesting security interactions with Range in the past)

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