[ad_1]
[ad_2]
So, we have static caching and dynamic caching we obtain through our hosting provider or a plugin .
If you use the cheapest Cloudflare plan, it also has static caching and dynamic caching.
From what I hear is that we are supposed to keep the Static caching on Cloudflare on and turn it off in our plugin or hosting provider such as SITEGROUND Optimizer plugin.
Then for Dynamic caching, we are supposed to turn it on for the hosting provider or plugin and turn it off in Cloudflare.
Is this setup correct? Because I have met many developers who actually keep everything on, but in many cases they run into issues where they have to create all sort of rules to exclude form caching.
Please let me know the official configuration ?
I don’t have a specific answer for you. But typically, something should only be cached in one place. I just had a deal with a pantheon hosted side with redis cache fighting cloud flairs cache. My reco the client was to disable cloud flair cache – problem fixed
what’s dynamic cache? i have recently stopped using cloudflare, but this is what i did when i used them:
1. persistent object caching with redis or sqlite at origin – this caches common database queries so they can be retrieved faster. this has nothing to do with cloudflare as cloudflare doesn’t interact with the database. this is important for logged in sessions and dynamic sites where user specific data needs to be retrieved and displayed to different users.
2. full page caching at origin – this saves the responses generated by wordpress/php as .html files, and serves those files to future users instead of hitting php every time. this is very useful for identical requests by logged out or cookieless users. there are a ton of caching plugins for wordpress, plus there are others beyond wordpress (like fastcgi cache for nginx and varnish for apache httpd). some wordpress plugins have the option to create private page caches for logged in users, but generally speaking it’s far more important for anonymous/cookieless/logged out users.
3. static asset caching at cloudflare – this is done automatically by cloudflare when you add your site. cloudflare saves your images, js, css, etc and serves them from its cache to users without hitting your origin server. you can pass cache-control and expires headers from your origin, or set them at cloudflare.
4. html caching at cloudflare – cloudflare doesn’t cache html by default, but you can do it with their automatic platform optimization or with a cache rule. this way the entire request can be served by cloudflare without hitting your origin server, as long as everything is in their cache. having page caching at origin means even if an html is not in cloudflare’s cache, it will get it quickly from the origin page cache instead of waiting for php to generate the page.
Nginx , redis
No idea. I added my site and I use WP fastest cache plugin that asks for a cloudflare token so it can sync I guess. Works well for 90k+ posts.