How does caching work in the plugin?

It’s more than just a Cache Rule on the Cloudflare side. The Cache Rule is combined with the plugin on the web server side to allow it to make granular decisions based on various factors. For example the URL doesn’t need to change for logged in/vs. logged out users, instead we can decide to serve a cached versions based on if the user is logged in or not.

?to make granular decisions based on various factors.

yeas, I understand.

For now I use – Super Page Cache for Cloudflare. And when my site down – its not shown, its down. But when I setup full Cache Rule on the Cloudflare side – page always shown from CF cache….. Do you see the difference? That’s why I’m asking how your plugin works.

the same goes for the site speed…. when I setup full Cache Rule on the Cloudflare side – pages very very fast open

Ya, the same would be true with this plugin. If a page is eligible to be cached, it’s able to be served without contacting the origin server, so for an end user, they would still be able to view the cached version of the site even if the origin server was down.

It’s not a particularly great way to hedge against server issues (better to solve the server issues), but it would allow for cached pages to be served even if the server is down (as long as it’s not longer than the cache time you set).

That being said, yes… a page would potentially be fast and available to end users if the site was down because it’s being served from Cloudflare’s edge without the need to make a request to the site’s server (so the server only needs to be up if the cached version is expired).

(better to solve the server issues)

of course this is not to solve the server problem, this is as an example of exactly how the cache works…

thanks for fast / detailed answer, I test y plugin and will wtite result / check “resolved”.

Good luck.