cacheEverything: true vs Cf-Cache-Status: DYNAMIC

Hi all, I have 2 zones on 1 account. Both have very similar Cache Rules, where effectively Cache eligibility evaluates to "Eligible for cache". Then I have a Cloudflare worker deployed to both zones, which contains piece of code:
const response = await fetch(requestUrl, {
headers: requestHeaders,
method: request.method,
redirect: "manual",
cf: {
cacheTtlByStatus: {
"200-399": 86400,
"400-499": 60,
"500-599": 10,
},
cacheEverything: true,
cacheTags: cacheTags,
}
});
const response = await fetch(requestUrl, {
headers: requestHeaders,
method: request.method,
redirect: "manual",
cf: {
cacheTtlByStatus: {
"200-399": 86400,
"400-499": 60,
"500-599": 10,
},
cacheEverything: true,
cacheTags: cacheTags,
}
});
The problem is that requests on one zone evaluate to response with header Cf-Cache-Status: HIT, while on second zone to response with header Cf-Cache-Status: DYNAMIC. What's more interesting - even if I configure my worker to fetch the data from the same origin in both zones, the result is the same. Could you tell me - what else can I check / how can I debug why do I receive Cf-Cache-Status: DYNAMIC on one of the zones?
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?