I am referring to Caching > Cache Rules > custom rule called “cacheable query strings” where I have set:
(http.request.uri.query contains “exampleparam=”) to “Eligible for cache”
If I visit /examplepage on my website, I get the expected values in the chrome network console:
Cache-Control: no-cache, no-store
Cf-Apo-Via: tcache
Cf-Cache-Status: HIT
Cf-Edge-Cache: cache,platform=wordpress
However, if I vist /examplepage?exampleparam=examplevalue then I get:
Cache-Control: no-cache, no-store
Cf-Apo-Via: origin,miss
Cf-Cache-Status: BYPASS
Cf-Edge-Cache: cache,platform=wordpress
I suspect this may be because a few days ago I MISTAKENLY added a sub-rule within Caching > Cache Rules > “cacheable query strings” where I have set:
(http.request.uri.query contains “exampleparam=”) to “Eligible for cache”
THIS PART CHANGED----> and then had set the Browser TTL (optional) within that rule to “Bypass cache”
I purged Cloudflare and browser caches to be safe
IMPORTANT: Before I had made this change a few days ago on the Browser TTL (optional) within that custom rule to “Bypass cache”, I was seeing
Cf-Cache-Status: HIT on pages that had query string
So, to correct it I tried deleting the Browser TTL (optional) within that “cacheable query strings” rule I had set. Then purged cache again.
Waited several hours and saw no change…still seeing Cf-Cache-Status: BYPASS on pages with those query strings
So, then several hours ago I tried changing the Browser TTL(optional) within that “cacheable query strings” I had set to “Respect origin TTL”. Then purged cache again.
I’m still seeing Cf-Cache-Status: BYPASS on pages with query strings
My overall cache configuration settings are:
Cahing Level: Standard
Browser Cache TTL: Respect Existing Headers
Any idea how to get the pages with query strings to once again start showing Cf-Cache-Status: HIT?
APPARENT FIX: I had another cache rule listed second in the stack that set (http.request.uri contains “*”) and set Eligible for Cache and set its Edge TTL Ignore cache-control header and use this TTL to 1 month.
BUT, in my cacheable query strings rule listed first in the stack I had set Eligible for Cache, but I HAD NOT SET Edge TTL. So I set Edge TTL Ignore cache-control header and use this TTL to 1 month and am now seeing Cf-Cache-Status: MISS and then HIT (no more bypass!!)
I had expected that rule 2 that set Edge TTL to 1 month would apply to the cacheable query strings rule list first, but apparently not!