Re: [whatwg/fetch] How are reloads mapped to cache modes? (#524)

Probably, it will be difficult to define per-fetch-group cache mode correctly because fyi, in Chrome it apparently has a per-frame cache policy internally that may match to the concept of per-fetch-group cache mode. But actual cache mode for each request was determined by many conditions, e.g. if the per-frame load type is 'reload', cache mode for the main resource could be no-cache, but for others, it could be default.

Anne, what do you think about the point I asked as follows?

> One confusing point of the Fetch cache mode spec to me is that it defines HTTP-network-or-cache fetch as
> 
> no-cache appends "max-age=0" if there is no Cache-Control header
> no-store and reload append "no-cache" if there is no Cache-Control header

Why don't we have a straight-forward maps that set no-cache for no-cache, and no-store for no-store?
(and probably max-age=0 for reload?)

-- 
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/524#issuecomment-293540478