HTTP Caching HTTP responses Stop use of cached resources without checking with the server first


Example

Cache-Control: no-cache

The client will behave as if the response was not cached. This is appropriate for resources that can unpredictably change at any time, and which users must always see in the latest version.

Responses with no-cache will be slower (high latency) due to need to contact the server every time they're used.

However, to save bandwidth, the clients may still store such responses. Responses with no-cache won't be used to satisfy requests without contacting the server each time to check whether the cached response can be reused.