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

So from those:

1. Already happens.
2. Is something for the Cache API to decide.
3. Already happens in step 8 of https://fetch.spec.whatwg.org/#concept-http-network-fetch as far as I can tell.
4. This does not currently happen.

Here are some things I'm wondering about:

1. Should we change https://fetch.spec.whatwg.org/#concept-http-network-or-cache-fetch step 15 to talk about one or more partial responses?
2. Should step 17.1 explicitly talk about a complete response?
3. Is there any freshening of headers when you get a 206 response? https://tools.ietf.org/html/rfc7234#section-4.3.4 seems to suggest there isn't. HTTP Range Requests also does not talk about this as far as I can tell.
4. Is therefore the only thing we need to introduce a 206 clause (similar to step 17 for 304) when cache mode is either "default" or "no-cache" that does recombining?

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

Received on Wednesday, 11 November 2015 09:22:33 UTC