Cloudflare Developers•3w ago

Cloudflare keep to Revalidated my static files even my origin tell to keep a half-year

I found that many path got Revalidated very frequently and lead to high load on my origin server. I want Cloudflare to cache this files as most as possible but this keep revalidate all day. I'm on enterprise plan and support center tell me to try purge that path then that work fine, after that every request for this path got HIT. That's mean I need to purge all of path which faced this problems. I want solid solution to fix this problem, Could you please suggest the correct way rather than purge all of path? (Because this very expensive for large domain.)

11 Replies

NonOP•3w ago

Here's my response header from Cloudflare

< content-type: image/jpeg
< content-length: 18371
< cache-control: public, max-age=16070400
< cf-bgj: imgq:85,h2pri
< cf-polished: degrade=85, origSize=25526, status=webp_bigger
< etag: "0812e4c25661939fd5d5d4b32ee3c43fd0b53ee6"
< expires: Sat, 18 Oct 2025 10:24:19 GMT
< x-cache-status: MISS
< cf-cache-status: REVALIDATED
< accept-ranges: bytes
< strict-transport-security: max-age=2592000
< x-content-type-options: nosniff
< server: cloudflare

< content-type: image/jpeg
< content-length: 18371
< cache-control: public, max-age=16070400
< cf-bgj: imgq:85,h2pri
< cf-polished: degrade=85, origSize=25526, status=webp_bigger
< etag: "0812e4c25661939fd5d5d4b32ee3c43fd0b53ee6"
< expires: Sat, 18 Oct 2025 10:24:19 GMT
< x-cache-status: MISS
< cf-cache-status: REVALIDATED
< accept-ranges: bytes
< strict-transport-security: max-age=2592000
< x-content-type-options: nosniff
< server: cloudflare

and some request got HIT, I don't know why this happen.

NonOP•3w ago

Here's page rule for this domain.

NonOP•3w ago

fyi; For this domain I want Cloudflare to cache everything forever.

Zack0322•2w ago

see https://developers.cloudflare.com/cache/how-to/configure-cache-status-code/#ttl-handling-for-304-and-200-status-codes

Cloudflare Docs

Cache by status code · Cloudflare Cache (CDN) docs

Customers can set cache time-to-live (TTL) based on the response status from the origin web server. Cache TTL refers to the duration of a resource in the Cloudflare network before being marked as STALE or discarded from cache. Status codes are returned by a resource's origin.

Zack0322•2w ago

basically you need to update the TTL for your 300-599 range to exclude 304 otherwise once the asset is revalidated the first time, the ttl of the asset will become no-cache (i.e always revalidate) instead of whatever ttl you set for hte 200

NonOP•2w ago

So, that mean If I remove response header etag out. Client will not try to revalidate it and Cloudflare will never revalidate asset with my origin server right?

Zack0322•2w ago

you don't want to do that. you should update the rule that sets 300-599: no cache to: 300-303: no cache and 305-599: no-cache this way the 304 status code will inherit the ttl of the 200 which you have as "forever"

NonOP•2w ago

Wow, I think we found the root cause. Here's my current config

NonOP•2w ago

I need to change my setting to like this?

NonOP•2w ago

Thank you so much, I will try to confirm this on production by next week.

Zack0322•2w ago

that's correct

Gaming

Programming

Cloudflare keep to Revalidated my static files even my origin tell to keep a half-year

Did you find this page helpful?