web / HTTP headers / cache
Review HTTP Cache-Control boundaries
Review shared caches, browser caches, storage and revalidation with fixed cases. This guide never fetches a real response or changes external settings.
Cache-Control review matrix
Do not infer where a response is stored from one directive. Separate shared cache, browser cache and revalidation.
| Case | Shared cache | Browser | Review point |
|---|---|---|---|
| public-max-age | allowed | reuse candidate during max-age | check short freshness |
| private-max-age | not allowed | private cache only | avoid sharing personal data |
| no-store | do not store | do not store | storage prohibition wins |
| no-cache-revalidate | revalidate before reuse | revalidate before reuse | do not confuse storage and freshness |
| s-maxage-max-age | review s-maxage | review max-age | separate shared and browser TTL |
Review order
- Decide whether storage is allowed: no-store or private.
- Separate shared-cache and browser-cache scope.
- Read max-age, s-maxage and no-cache separately.
- Review real headers, CDN and authentication conditions separately.
This page shows fixed cases only. It has no input, fetch, upload, storage or analytics.