Cloudflare Cache Responses
HIT
The resource was in Cloudflare cache
MISS
The resource was not available in Cloudflare cache and was served from the origin server
NONE/UNKNOWN
This can happen if
- there were any Redirect Rules in place or was redirected due to Always On HTTPS
- the request was blocked by the WAF filter as the request is handled by the global network before it hits the cache
EXPIRED
the requested resource was found on the cache but was expired and served from the origin server.
STALE
the requested resource was EXPIRED on the Cloudflare cache and the cache couldn’t contact the origin server.
BYPASS
The origin server instructed Cloudflare to bypass cache via a Cache-Control header set to no-cache, private, or max-age=0, Cloudflare also sets BYPASS when there is a Authorization header in the request.
Check CDN Cache Control
REVALIDATED
The resource served from Cloudflare cache but was stale, it was revalidated with If-Modified-Since and If-None-Match headers
UPDATING
The resource was served from Cloudflare cache but expired and the origin server is updating the resource. UPDATING is only seen for very popular resources
DYNAMIC
Cloudflare doesn’t consider the resource to be cached, edit the cloudflare settings to enable custom cache rules to enable caching, this means that the resource was requested from the origin web server