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

I'm a little concerned that this may not match the gecko implementation at all.  Currently we add Range headers at the http cache level.  We do this because we use the http cache to known whether we are resuming a previously seen resource or if the resource has changed.  If the resource has changed we don't use a range request.

@mcmanus Is my reading of range requests in gecko correct here?  Are there other ways that we generate range requests?  For example, do media channels do something different here compared to resuming a download?

-- 
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-333130184