Re: [whatwg/fetch] Refreshing of stale response assumed to always be successful (#950)

One thing we can definitely do is flesh out 7.4 a bit more to align it with the https://httpwg.org/http-core/draft-ietf-httpbis-cache-latest.html#rfc.section.4.3.3, to handle the following case:

1. `revalidating` flag is set, but we get a "full response" => "the cache MUST use the full response to satisfy the request and MAY replace the stored response"
2. `revalidating` flag is set, but we get an 5xx back => "either forward this response to the requesting client, or act as if the server failed to respond. In the latter case, the cache MAY send a previously stored response"

And I think the "full response" seems to answer my previous question: a server should not send a 304 back if it would not match the validators found on the request. Although that is perhaps something the cache spec should address, essentially what to do with a 304 response that doesn't seem to match any of the stored responses. 

-- 
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/950#issuecomment-649378996