Re: [fetch] Cache state: partial content (#38)

> it's not entirely clear to me how to deal with partial content. Does us handling that mean we also pay special attention to a 206 response? What's the logic here, if we notice we have a partial cache entry, we set If-Range, then if there's a 206 response, we combine some stuff and hand out the combined response as a 200 to content? 

Exactly.  We always hand out a 200 (on a new 200 server response -> cache state "none", or a 206 response from the server that we, as you say, combine -> cache state "partial" or could well be "validated" since 206 is mostly the same as 304.  But depends.  I kinda don't see a use case right now for the "partial" state, tho)

> Does this only happen for media elements basically?

No, this can happen for anything, large HTML, CSS whatever.  The response just needs to fulfill some conditions to be "resumable".  I don't think you need to be concerned about it tho.

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