Bypassing APO with Cache Rule

I have pages on my website (everything with the url construction /show/*/) that I need to bypass the default Cloudflare APO caching. I’m attempting to do this through a combination of cache-header and Cloudflare Cache Rule. Here is a page…

…where you should see this cache header:

max-age=3600, public

Here is my cache rule in Cloudflare:

I would expect Cloudflare to throw that page out after an hour… I have run several tests, but it’s not purging. (I have also tried “Ignore cache-control header and use this TTL” with the TTL set to 1 Hour. That also wouldn’t purge.)

Is some other cache variable overriding it? Is there a better/different methodology?

Help is greatly appreciated. Thanks!

Cache Rules don’t take wildcards, so it’s never going to match /show/*/

If you’re on a Business or Enterprise plan, you can use RegEx.

Okay let me see if I can accomplish the same thing with this Page Rule…*/
Origin Cache Control: On

As far as I know, Page Rules accept wildcards across plans.

Actually, that also does NOT work. Any idea why? Page Rules do accept wildcards across plans.


Here’s a new URL to test: Rumble Fish - Movie

CURL output:

date: Sun, 18 Feb 2024 04:41:13 GMT
content-type: text/html; charset=UTF-8
cf-ray: 857398b219b40f7c-EWR
cf-cache-status: HIT
age: 2261
cache-control: public, max-age=3600
last-modified: Sun, 18 Feb 2024 03:27:20 GMT
link: <>; rel=""
vary: Accept-Encoding
cf-apo-via: tcache
cf-edge-cache: cache,platform=wordpress
x-cache: HIT: 2
x-cache-group: bot
x-cacheable: bot
x-powered-by: WP Engine
report-to: {"endpoints":[{"url":"https:\/\/\/report\/v3?s=pfgO3FhPPd1oX0%2FgF42UdyV4OX3cEsFqU2qBd9Zx8tSZbhzFYrPW0xliRj3mtuF4%2Fu3%2F9oxHwX9XtEGGNT%2Fy9boAgmGQQILpurbFwWUp9OiViQXGGES9BPvSFbG%2FihoGt4sM"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
alt-svc: h3=":443"; ma=86400

I am marking the first answer from @ sdayman as correct (because it is) and post my follow-up as a new post, since the question technically changed.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.