![]() ![]() Page Caching by using Cloudflare Worker (alternate to page rule solution, needs to be manually activated in plugin settings).Cache Buster Support to ensure logged-in users don’t see cached content.Takes full advantage of Cloudflare Cache Everything Page Rule.Developed to work flawlessly with any Cloudflare Plan (be it Cloudflare Free or Pro or Business or Enterprise account).The alternative to this plugin is to purchase and configure the Enterprise plan. You will be able to significantly improve the response times of your WordPress website by taking advantage of the very fast Cloudflare cache also for HTML pages, saving a lot of bandwidth. Moreover, you can also overwrite our default worker code to add your own custom login into it if you are an advanced user. The Cloudflare Worker based solution will help you to have a clean page caching solution without any cache buster query string (/?swcfpc=1) for logged-in users. By default the Cloudflare Worker mode is disabled as it is not 100% free like the Cache Everything page rule. This plugin enable page caching on your website by taking advantage of either the Cloudflare Cache Everything page rule or using Cloudflare Worker. ![]() Thanks to this plugin all of this becomes possible. However for dynamic websites such as WordPress, it is not possible to use this page rule without running into problems as it is not possible to exclude critical web pages from the cache, the sessions for logged in users, ajax requests and much more. The free Cloudflare plan allows you to enable a page cache by entering the Cache Everything page rule, greatly improving response times. then you have to pay for the Cloudflare Pro plan to enable those features in your Cloudflare account. But if you like to use features like Cloudflare image optimization, WAF (Web Application Firewall) etc. ![]() This plugin takes full advantage of the FREE Cloudflare Plan, so to use this plugin, you don’t need a paid Cloudflare account. Take a look at the review video below by IdeaSpot, which will give you a clear idea about the plugin before you install it. This will reduce your website loading speed drastically thanks to taking advantage of the Cloudflare CDN, not only for the static files but also for the HTML webpages. With more than 200 CDN edge locations provided by Cloudflare, your webpage will be served from the nearest CDN location of the visitor, rather than sending the request to your web server which might be sitting on the other side of the world. the cached webpages will be served from your web-server), this plugin will cache your webpages and static files to the Cloudflare CDN, one of the fastest CDN networks in the world. Unlike most caching plugin out there which only provides disk caching (i.e. But for most users, you don’t need to change any settings as this plugin will work perfectly with the default settings, out of the box. But if you are a curious/advanced user, there are detailed settings inside the plugin which you can tweak to make it work as you like. Moreover, this plugin works completely out of the box, all you need to do is provide your Cloudflare Account’s API Key or API Token details and the plugin will do the rest. CSS, JS, images etc.) but also the HTML webpages generated by WordPress both at server disk-level and to the global Cloudflare CDN. This plugin will help you to cache not only the static files (e.g. We know that WordPress has a CF module which enables CF and LiteSpeed's cache module to work simultaneously.The Super Page Cache for Cloudflare plugin helps you to make your website blazing fast by taking the website caching to the next level. Somehow there is a conflict between CF and LiteSpeed in this setup which causes the redirect error. We have tried to disable the LiteSpeed cache module again (the LiteSpeed's rewrite rules are of course still unchanged even though the cache module has been disabled in PS) - and the issue remains. We believe it's due to Litespeed's re-write logic. The page just redirects to itself again and doesn't complain about wrong user credentials or similar. Screenshot of the test-domain which is not "proxied" via CF:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |