By default, Cloudflare will cache static files, but not HTML. In order to make Cloudflare cache static-content HTML, you’d need to create a Cache Rule (beta), or a Page Rule (soon to be deprecated).
Thanks for the reply,
Actually I had created cache rules but that doesn’t changed my cf-cache-status: DYNAMIC I’m trying to connect with (superpage cache with Cloudflare) plugin which created page cache rules for all websites but then my response headers still shows different status for each websites which is > cf-cache-status: EXPIRED for main website and the page cache worked in the plugin which increased my website speed successfully
For one subdomain - opanai ,the > cf-cache-status: MISS but the plugin page cached successfully but doesn’t improved my subdomain website speed and
the other subdomain - conzigne has the same > cf-cache-status: DYNAMIC as before even though the plugin created a page rule,shows the same error as before which the plugin couldn’t page cache successfully.
So what I do to make it work and to make the cache status → cf-cache-status: HIT
What websites are you talking about? Are you using Cloudflare for SaaS? Or is this a multisite WordPress installation? I’m afraid you are conflating too many separate questions into one topic, and that complicates matters.
Why don’t you pick one domain and describe its caching configuration in detail so that we can start with that?
Its a wordpress multisite website
Can you post a screenshot of your Cache Rule?
Sorry for the delay.
As it was showing the same >>cf-cache-status: DYNAMIC, I have deleted cache rules and created byepass cache for my admin files n cache rules for content files .
The plugin which I have connected,created page rules by itself which has the above issues I have mentioned in my previous reply
Thanks again While taking the screen shot i just realized that the plugin created pages rules with http for one of the subdomain So changed back to https not ts working fine but then Why does the response headers shows different
which is > cf-cache-status: EXPIRED for main website and one subdomain - opanai and the page cache worked in the plugin which increased my website speed successfully
For one subdomain - conzigne ,the > cf-cache-status: MISS but the plugin page cached successfully .
It all depends on the Cache-Control header your origin is sending back with responses, as well as your Cache Rule and Page Rule configurations.
With a Page Rule, you can override the origin Cache-Control by adding Edge Cache TTL to the same page rule that has Cache Everything.
With Cache Rules (beta), you can do this as part of the rule itself, where for both Browser TTL and Edge TTL you can decide whether to respect the origin or override it.
In any case, MISS is the appropriate response for the first visit(s) handled by a single colocation. It means the rule to cache the page is ON, but since this was the first or second visit, it wasn’t cached yet. Fetch the same page a couple more times and you should see HIT.
EXPIRED indicates there’s a time component. You should dig into the first link I posted in my first reply, and navigate through the left column links, and you’ll become more familiar with the many ways cache can be set (and unset).
yeah I wrote some other cache rules and some setting in the plugins response header were fixed.issues were fixed.thanks very much for the support
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.