Re: [whatwg/fetch] Allow range header to be set by APIs (#560)

@jakearchibald You are probably correct. Have minimal experience with `ServiceWorker`. The naive expectation here was that a request for a media resource using `fetch()` - whether media fragment URI, or setting range header - would result in a `Blob` or `ArrayBuffer` comprising the only bytes, or time ranges as bytes specified. That is, `fetch("/media#t=30,60")` should have same result as `new Audio("/media#t=30,60")`. Not sure what the security risks associated with range requests are?

-- 
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/pull/560#issuecomment-312436435