no-store
The Cache-Control directive that tells every cache not to keep any copy of the response.
In more detail
Use it for answers that must never be replayed to anyone, such as authentication failures, session details and responses containing personal data. It is stronger than no-cache, which allows storing but requires revalidation before each reuse.
Example
In the APIs course: The course service sends it on every problem response.Related terms
- Cache-Control — The HTTP header that states the caching policy for a response, such as private, max-age=0 or no-store.
- HTTP cache — A store that keeps HTTP responses and reuses them for later requests, following the rules the server sends in Cache-Control.
Taught in
- What An API Is, And The Alternatives — Modern API Architecture: REST, GraphQL & gRPC
- Cookies And CORS — Modern API Architecture: REST, GraphQL & gRPC
- The Fetch API: Streaming Responses, HTTP Caching And Keepalive — Frontend Architecture & Web Platform