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

> @foolip mostly if these changes are compatible with eventual changes for the media API in HTML.

Probably. I think the non-obvious things that need to work for media elements are:
- Requesting the range 0- must be possible.
- If the response to that is 200, that's not an error, but it is a piece of information that's needed to avoid interrupting the fetch later, as resuming is impossible.
- If more data than requested is returned, that's probably OK, as long as it starts at the right place.
- Cache behavior is strange and probably inconsistent. At the very least, with no cache-related headers, I think implementations assume it is unchanging as long as the resource size doesn't change, or perhaps even a growing resource is OK. Needs testing.

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