Comparison
Cache-ControlvsCache Storage
Cache-Control
you deployed a fix and the browser served the old file anyway, from its own disk cache.
The header that tells the browser and any intermediate cache how long a response may be reused and under what conditions. The directives are routinely misread: `no-cache` means revalidate before use rather than do not store, and only `no-store` actually prevents caching. Getting this wrong on an HTML entry point pins users to an old build for as long as the max-age lasts.
Full entry →Cache Storage
you stored whole request and response pairs so the service worker could answer them without the network.
A store of Request-Response pairs, separate from the HTTP cache and controlled entirely by your code. It is what makes offline-first possible, and it obeys no HTTP caching semantics on your behalf: nothing expires unless you delete it. Cache names are the versioning mechanism, so an update means writing a new one and cleaning up the old one on activation.
Full entry →