HTTP Cache-Control Tester

Paste response headers and see whether a browser or shared cache such as a CDN may store the response, how long it stays fresh and when it must be revalidated, following RFC 9111.

Use the tool

Why this tool exists

Caching bugs are annoying in both directions. A page that should be cached is fetched again every time, or a private response is stored by a CDN and shown to the wrong visitor. The rules mix Cache-Control, Expires, s-maxage, status codes, request methods and heuristic freshness from Last-Modified, and few people remember them all.

This tester applies the rules to the headers you paste and explains the outcome for a private browser cache and for a shared cache. You can change the status code and method to see how the result changes. It shows the logic of the specification, not what a particular CDN does with its own overrides, so confirm with real requests. The headers are analysed in your browser.

How to use it

  1. Paste the response headers, including Cache-Control, Expires, Last-Modified and ETag if present.
  2. Choose whether to test a private browser cache or a shared cache.
  3. Set the response status code and request method.
  4. Read whether the response is storable, how long it is fresh and when it needs revalidation.

Frequently asked questions

What is the difference between max-age and s-maxage?

max-age applies to every cache, while s-maxage applies only to shared caches such as CDNs and overrides max-age there. That lets a CDN keep a copy longer than a browser does.

What is heuristic freshness?

If a response has no explicit lifetime but has Last-Modified, caches may assume a fraction of the time since that date, commonly ten percent. The tool shows this so surprising caching has an explanation.

Does it reflect my CDN's real behaviour?

Not exactly. It follows the standard, but CDNs add their own rules, such as ignoring headers or using their own overrides. Use it to understand your headers, then verify with real requests.