Caching ¶
Cached Requests
cf-cache-status: HIT Asset exists- and is served from CF’s cache. Only status that doesn’t make a request to origin.cf-cache-status: MISS Asset did not exist in CF’s cache and was fetched from origin (it might be cached now).cf-cache-status: EXPIRED Asset exists in CF’s cache, but because it expired, it was fetched from origin and then cached again.
Not Cached Requests
cf-cache-status: BYPASS CF does not cache this asset, usually due to no-cache headers and it was fetched from origin.cf-cache-status: DYNAMIC Asset not in CF’s cache by design and was fetched from origin (default for eg. POST requests).