What is the difference between no-store and no-cache?
no-store means do not keep the response at all; no-cache allows storage but requires revalidation before reuse.
Cache-Control Parser
Parse Cache-Control directives and inspect TTL and conflicts
API & HTTP
π 100% client-side β your data never leaves this pagePage mode
Cache-Control Input
Quick CTA
Paste one Cache-Control header per line and inspect TTL, public/private visibility, and warnings first; conflict cases and fixes stay in Deep.
Output
Parsed result appears here
100% client-side
Page reading mode
Quick keeps the summary, direct answers, and next steps so you can validate fit and get a result faster.
About this tool
Cache-Control Parser decodes HTTP Cache-Control headers into structured directives so you can reason about browser and CDN behavior faster. Paste one or multiple lines and instantly see normalized directives, cacheability, visibility (public/private), TTL signals (max-age or s-maxage), and warning hints for contradictory combinations. This is useful for API responses, static asset caching, and reverse-proxy tuning where a tiny header mistake can cause stale content or cache misses. The parser also helps teams review policy changes before release and keep cache behavior predictable across environments. All processing is local in your browser.
Direct Answers
Why does s-maxage behave differently from max-age?
Shared caches such as CDNs prioritize s-maxage, while browsers typically follow max-age and private/public semantics.