Storage and reuse have different controls
The unqualified no-cache response directive permits storage but requires successful validation before reuse. No-store directs a cache not to store the request or response. Private restricts storage by shared caches, while a private client cache can still be allowed to store the response under the applicable rules.
These are not interchangeable privacy promises. They govern compliant HTTP caching behaviour. They do not erase screenshots, browser history, logs or files saved by other mechanisms. Sensitive URLs still require careful handling even when the response has restrictive cache directives.
A freshness calculation
Consider a response with max-age=60 and a current age of 45 seconds. Ignoring additional restrictions for this illustration, it has 15 seconds of freshness remaining. A newly received response is not necessarily age zero because it may already have spent time in an upstream cache.
Media resources need different policies according to whether their representation changes. A rolling live playlist and an immutable named segment do not have the same update needs. Copying one long cache lifetime onto both can delay playlist progression even if the cached segments remain perfectly valid.
Interpret the complete policy
Directives can interact with response status, authorisation and other metadata. Shared-cache controls such as s-maxage have a different scope from ordinary max-age. A single header value should therefore be read in its context rather than turned into a universal recommendation for every streaming server.
For a stale-content report, keep Date, Age, Cache-Control, validators and the observed body change together. Viewers generally cannot repair an upstream cache by deleting local app data. A local clear can change one stored copy, but the next request may receive the same permitted response from another cache.
Questions about this guide
Does no-cache forbid storing the response?
No. Its unqualified response form requires validation before reuse. No-store addresses storage.
Is the HTTP cache the playback buffer?
No. A cache stores HTTP responses; a media buffer holds data for playback and can have different limits.