Re: [whatwg/fetch] Why `max-age=0` for `no-cache` mode ? (#1121)

I agree that *if* the intent is to prevent downstream caches from using a stored response, `no-cache` would be a better choice -- in particular because it includes the semantics of `must-revalidate`. 

But, as I argue in  #722, that's not the right thing to do -- Fetch setting *any* request cache-control headers is layering in a higher-level, API-specific semantic, not allowing developers to manipulate lower-layer HTTP semantics. Developers already have direct control of the headers, and setting them automatically deprives developers from the ability to control the local cache separately from remote ones.



-- 
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/1121#issuecomment-739122811