Cache rule setup in dashboard has unexpected outcome - Cache bypass not TTL change
What steps have you taken to resolve the issue?
We have had a problem on our website with pages being cached in edge cache with a TTL that is too long so stale content is being served.
I thought that a cache rule would be a solution. So I set up a new cache rule
It has URI matching criteria which is working correctly with wildcard but instead of the overriding of cache-control headers with a set TTL instead it performs a cache bypass for the matched urls.
I tried both Browser TTL and Edge cache TTL being set to 30 minutes and instead the Edge cache was bypassed for all requests matched by the rule which I could see in both Instant Logs and at the origin server.
What are the steps to reproduce the issue?
You can see the setting the cache rules section of the dashboard in the attached screenshot.
This issue is still happening. Sorry I have been away. an example url is
As I said the behaviour is that the must re-validate header for instance sent when the browser cache empty is sent seems to display an updated version of the page, but otherwise the TTL is not respected and cache is not refreshed. BTW this is a high traffic site so a URL like the one listed would be hit at least 10 - 50 times an hour.
BTW other cache rules, for instance we have one to not cache admin seem to work fine.
It seems you are using the Cloudflare Wordpress plugin. The plugin should automatically purge the cache when you release new content, so Edge TTL shouldn’t matter.
I can’t see a BYPASS on the URL you linked here. I see cf-cache-status: HIT.
