Private versus shared
A browser cache serves one user; a shared cache can serve many. Personal responses must not accidentally become shared.
A cache reuses saved responses, reducing origin-server work.
A browser cache serves one user; a shared cache can serve many. Personal responses must not accidentally become shared.
Caching rules determine freshness. no-cache requires validation before reuse; no-store forbids storing the response.
Test both normal reloads and a new session. Design publication-time invalidation, not just manual clearing.
The explainer is checked against these institutional and industry sources. Links open the original material.