HTTP caching
HTTP caching uses response headers and validators to control reuse by browsers and intermediaries. It is separate from service-worker Cache Storage.
What it is
HTTP caching uses response headers and validators to control reuse by browsers and intermediaries. It is separate from service-worker Cache Storage.
Why it matters
A service-worker cache miss may still receive an old response from the browser HTTP cache if freshness rules allow it.
Example
Cache-Control: no-cache allows storage but requires revalidation; no-store asks caches not to store the response.
Technical detail
ETag and If-None-Match can produce 304 Not Modified responses when the stored representation is still current.
When to use it
Give content-hashed files long lifetimes; revalidate mutable policy weights, manifests, and HTML.
Go deeper
Sources
More in Web platform
Assembled from the ReLU.chat curated knowledge base. These explanations are concise on purpose; check the sources for anything important.