enoexec
Forum Replies Created
-
Thanks for the tips and advice. I checked the CF BUI and confirmed all the defaults where ON.
A1) I have no cache rules defined
A2) I have no workers defined
A3) The ‘Browser Cache TTL’ was (is) set to ‘Respect Header’. I tried setting it to 1 day, but this didn’t change the caching behaviour
A4) I have no other Page Rules defined other than the one created by the plugin.
A5) Development mode is disabledI have a ticket open with Elementor Cloud to see if the ‘ec-source’ is coming from the web server.
Thank you. I removed the Rule in Cloudflare, then Disabled and Enabled the Cache. I see the rule was added, but the HTML pages continue to return ‘cf-cache-status: DYNAMIC’. Static resources return ‘cf-cache-status: HIT’.
Here’s the current CF Rule added by the Plugin


Do you have any other ideas or recommendations?
When I “Test the Cache” I get this message which confirms the DYNAMIC Response Header value:

I have my DNS pointing at CloudFlare and CloudFlare shows it’s proxying the A and CNAME entries, so I don’t believe it’s an issue there.

@saumya, thanks for the response. I have only one Page Rule that currently looks like this:

I started with the vanilla “Cache Level: Cache Everything”, but then added the others as I tested each one.
I also tried different URL options, including “*stevescargall.com/*” to no avail.
The ‘cache-control’ and ‘x-wp-cf-super-cache-control’ response headers are the same, so something is preventing CloudFlare from caching the HTML result. I don’t know if CloudFlare is honoring the ‘ec-source: dynamic’ value.

For images and other CF cachable objects, ‘ec-source: static’ which returns a ‘cf-cache-status: HIT’

I could be barking up the wrong tree with ‘ec-source’.
Thanks for the help.