Re: [whatwg/fetch] Use of response's cache state (#376)

So basically, step 4 and step 6 of step 2.20 of https://fetch.spec.whatwg.org/#concept-http-network-or-cache-fetch:

> If httpRequest’s cache mode is "force-cache" or "only-if-cached", then set response to storedResponse and abort these substeps. 

> Otherwise, if the revalidatingFlag is unset, then set response to storedResponse.

Would need to be updated to set a flag on response.

I suppose we could add back "cache state" and make the default the empty string (set it to "local" per above). And add a note that if you plan on using this for something other than service workers you let Fetch know.

-- 
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/376#issuecomment-381994849

Received on Tuesday, 17 April 2018 13:37:14 UTC