`Cache-Control: no-cache` header on request not respected? about http-cache HOT 3 CLOSED

Very cool to hear, thanks for sharing!

So this one confused me as well at first. This really comes from the cache header directive, which in my opinion was poorly named because I would expect 'no-cache' to literally mean do not cache this. But it actually is more of a, cache this but force a validation before responding with it.

Here's the relevant portion from the docs:
The no-cache response directive indicates that the response can be stored in caches, but the response must be validated with the origin server before each reuse, even when the cache is disconnected from the origin server. link

The directive that tells the client not to cache at all is named 'no-store'. Not confusing at all right! 😀

I considered having the cache modes differ from the spec in this regard, but decided that it could ultimately be more confusing to not have it match the directives seen in the headers. That said, I'm still open to reconsidering that decision.

from http-cache.

Thanks very much for the quick and detailed response, appreciated. I'll try no-store then :)

from http-cache.

Confirming that no-store gives expected behaviour. Will close this issue. Thanks again for your help.

from http-cache.