Re: [whatwg/fetch] Handling Partial Content / 206 (#144)

FWIW, I've written some basic tests to see if the HTTP (!SW) cache that Fetch uses supports partial content (i.e., range requests).

AFAICT, the only browser that does anything is Safari TP, which will store a partial response (i.e., one whose request had a `Range` header) and serve that response from cache if a request with the same `Range` header is made. 

It will not serve a subset of an already-cached response to a request containing `Range`; nor will it complete an existing stored partial response by creating its own `Range` headers when it goes forward.

Firefox and Chrome don't even handle the simple case (again, according to my test; I talked to @mcmanus about this this AM, and he was a bit surprised to hear that). Edge doesn't support the HTTP cache from Fetch, AFAICT.

-- 
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/issues/144#issuecomment-286339160