Reset all button.', 'wp-cloudflare-page-cache'); ?>

Strip response cookies on pages that should be cached.', 'wp-cloudflare-page-cache'); ?>

Purge HTML pages only option is enabled, clicking on the PURGE CACHE button only HTML pages already in cache will be deleted from Cloudflare\'s cache.', 'wp-cloudflare-page-cache'); ?>

Force purge everything', 'wp-cloudflare-page-cache'); ?>

If you chose the API Key as the authentication mode, make sure you have entered the correct email address associated with your Cloudflare account and the correct Global API key (not your Cloudflare password!).', 'wp-cloudflare-page-cache'); ?>

If you are chose the API Token as the authentication mode, make sure you have entered the correct token, with all the required permissions, and the domain name exactly as it appears in your Cloudflare account.', 'wp-cloudflare-page-cache'); ?>

Cache Everything page rule already exists for your domain. If yes, delete it. Now from the settings page of Super Page Cache for Cloudflare, disable and re-enable the cache.', 'wp-cloudflare-page-cache'); ?>

API Token, check that you entered the domain name exactly as on Cloudflare', 'wp-cloudflare-page-cache'); ?>

3. https://stackoverflow.com/a/8028987/2308992

mu-plugin is sending the header before advanced-cache.php can. That\'s causing the issue. We have thoroughly tested this.', 'wp-cloudflare-page-cache'); ?>

Prevent the following URIs to be cached, then save, purge the cache, wait 30 seconds and retry.', 'wp-cloudflare-page-cache'); ?>

Overwrite the cache-control header for Wordpress\'s pages using web server rules. You can keep this option enabled for Litespeed Server versions equal or higher then 6.0RC1', 'wp-cloudflare-page-cache'); ?>

Fallback Cache system provided by this plugin is turned OFF.', 'wp-cloudflare-page-cache'); ?>

x-kinsta-cache header is of status MISS. For the second request when Cloudflare serves the page from it\'s own CDN Edge servers without sending the request to the origin server, it keeps showing the x-kinsta-cache cache header as MISS. Because when Cloudflare cached the page the response header was MISS but Kinsta caching system has already cached it upon receiving the first request.', 'wp-cloudflare-page-cache'); ?>

x-kinsta-cache showing as HIT, because this time the request is going to your origin server and you are seeing the updated response headers that is being served by the server.', 'wp-cloudflare-page-cache'); ?>

1. Litespeed Cache > Cache', 'wp-cloudflare-page-cache'); ?>
2. OFF near Enable Cache', 'wp-cloudflare-page-cache'); ?>
3. Save Changes button', 'wp-cloudflare-page-cache'); ?>

Then:

2. Third Party tab', 'wp-cloudflare-page-cache'); ?>
3. Litespeed Cache Settings section', 'wp-cloudflare-page-cache'); ?>
4. Automatically purge the cache when LiteSpeed Cache flushs all caches', 'wp-cloudflare-page-cache'); ?>

Enable 404 fallbacks of Autoptimize.', 'wp-cloudflare-page-cache'); ?>

this GitHub Gist. This will guide you to do all the things necessary in order to use WP Rocket with this plugin. Here is a summery of what you need to do:', 'wp-cloudflare-page-cache'); ?>

2. /wp-content/mu-plugins/ folder) provided in the GitHub Gist (link given above).', 'wp-cloudflare-page-cache'); ?>
4. Fallback Cache option (If you want to use disk level fallback cache)', 'wp-cloudflare-page-cache'); ?>
5. Third Party tab', 'wp-cloudflare-page-cache'); ?>
6. WP-Rocket Cache Settings section and enable the Disable WP Rocket page cache option', 'wp-cloudflare-page-cache'); ?>

Cache-Control response header is different from that of the X-WP-CF-Super-Cache-Cache-Control response header (make sure it is the same).', 'wp-cloudflare-page-cache'); ?>

LiteSpeed Server version lower than 6.0RC1, make sure the Overwrite the cache-control header for Wordpress\'s pages using web server rules option is disabled. If not, disable it, clear your cache and try again. You can keep this option enabled for Litespeed Server versions equal or higher then 6.0RC1', 'wp-cloudflare-page-cache'); ?>

Overwrite the cache-control header for Wordpress\'s pages using web server rules option, clear the cache and try again.', 'wp-cloudflare-page-cache'); ?>

Force cache bypassing for backend with an additional Cloudflare page rule option or to change the caching mode by activating the Worker mode option.', 'wp-cloudflare-page-cache'); ?>

Fallback cache, make sure you have also enabled the option Automatically purge the fallback cache when Cloudflare cache is purged.', 'wp-cloudflare-page-cache'); ?>

Varnish cache, make sure you have also enabled the option Automatically purge Varnish cache when the Cloudflare cache is purged.', 'wp-cloudflare-page-cache'); ?>

SEO redirect inside the plugin settings page under the Others tab. This will auto redirect any URLs which has swcfpc=1 in it to it\'s normal URL when any non-logged in user clicks on that link, avoiding duplicate content problems.', 'wp-cloudflare-page-cache'); ?>

SEO redirect option inside the plugin settings page under the Others tab. This will auto redirect any URLs which has swcfpc=1 in it to it\'s normal URL when any non-logged in user clicks on that link.', 'wp-cloudflare-page-cache'); ?>

• Development Mode is NOT enabled for your domain inside Cloudflare.', 'wp-cloudflare-page-cache'); ?>
• Strip response cookies on pages that should be cached option under the Cache tab to see if this resolves your issue. If it does, that means there are plugin which is injecting cookies into your site header and when Cloudflare sees these Cookies, it think that the page has dynamic content, so it doesn\'t cache everything.', 'wp-cloudflare-page-cache'); ?>

advanced-cache.php method to generate the fallback cache. This system works well in almost all the cases, also this cache generation mechanism is very fast and don\'t eat much server resource. On the other hand the cURL mode is useful in some edge cases where the advanced-cache.php mode of fallback cache is unable to generate proper HTML for the page. This is rare, but the cURL option is given just for these edge cases.', 'wp-cloudflare-page-cache'); ?>

advanced-cache.php to generate the page cache, the cache files comes out very stable and without any issues. But then again if your enable the cURL mode, that means cURL will fetch every page of your website (which are not excluded from fallback cache) to generate the fallback cache and each cURL request is going to increase some server load. So, if you have a small to medium site with not many pages, you can definitely use the cURL mode of fallback cache. But for large high traffic website, unless you have more than enough server resource to handle so many cURL requests, we will recommend stick to using the default advanced-cache.php option which works flawlessly anyway.', 'wp-cloudflare-page-cache'); ?>

Cache Everything works perfectly in almost every cases but in some situations due to some server config or other reasons, the headers that this plugin sets for each requests, does not get respected by the server and gets stripped out. In those edge case scenarios Cloudflare Worker mode can be really helpful over the page rules mode.', 'wp-cloudflare-page-cache'); ?>

100,000 requests/day for FREE. But if your site has more requests than that per day, then you need to opt for the paid plan of $5/month which will give you 10 Million Requests/month and after that $0.50 per additional 1 Million requests.', 'wp-cloudflare-page-cache'); ?>

/assets/js/worker_template.js path.', 'wp-cloudflare-page-cache'); ?>

wp cfcache', 'wp-cloudflare-page-cache'); ?>

this implementation guide which comes all types of Cloudflare accounts before enabling this option.', 'wp-cloudflare-page-cache'); ?>

SWCFPC_CACHE_BUSTER to your wp-config.php', 'wp-cloudflare-page-cache'); ?>

• SWCFPC_CACHE_BUSTER,
• SWCFPC_CF_API_ZONE_ID,
• SWCFPC_CF_API_KEY,
• SWCFPC_CF_API_EMAIL,
• SWCFPC_CF_API_TOKEN,
• SWCFPC_PRELOADER_MAX_POST_NUMBER,
• SWCFPC_CF_WOKER_ENABLED,
• SWCFPC_CF_WOKER_ID,
• SWCFPC_CF_WOKER_ROUTE_ID,
• SWCFPC_CF_WOKER_FULL_PATH,
• SWCFPC_CURL_TIMEOUT,
• SWCFPC_PURGE_CACHE_LOCK_SECONDS,
• SWCFPC_PURGE_CACHE_CRON_INTERVAL,
• SWCFPC_HOME_PAGE_SHOWS_POSTS,

Actions:

• swcfpc_purge_all, no arguments.
• swcfpc_purge_urls, 1 argument: $urls.
• swcfpc_cf_purge_whole_cache_before,
• swcfpc_cf_purge_whole_cache_after,
• swcfpc_cf_purge_cache_by_urls_before, 1 argument: $urls.
• swcfpc_cf_purge_cache_by_urls_after, 1 argument: $urls.

Filters:

• swcfpc_bypass_cache_metabox_post_types,
• swcfpc_fc_modify_current_url,
• swcfpc_cache_bypass,
• swcfpc_post_related_url_init,
• swcfpc_normal_fallback_cache_html,
• swcfpc_curl_fallback_cache_html,

SWCFPC_CF_WOKER_FULL_PATH PHP constant to provide the full path of your own custom JavaScript file.', 'wp-cloudflare-page-cache'); ?>

/assets/js/worker_template.js path and see the Worker code we are using by default. Then you can copy that worker template file in your computer and extend it to add more features and conditionality that you might need in your project. Once you are done with your Worker code, you can simply point your custom Worker template JavaScript file inside wp-config.php using the SWCFPC_CF_WOKER_FULL_PATH PHP constant and the plugin will use your Worker file to create the worker in your website route instead of using the default Worker code. Here is an example of how to use the PHP constant inside your wp-config.php. Please make sure you provide the absolute path of your custom Worker file.', 'wp-cloudflare-page-cache'); ?>

define('SWCFPC_CF_WOKER_FULL_PATH', '/home/some-site/public/wp-content/themes/your-theme/assets/js/my-custom-cf-worker.js');

Please note only for Super Advanced Knowledgeable Users who know exactly what they are doing and which will lead to what. General users should avoid tinkering with the Worker Code as this might break your website if you don\'t know what you are doing.', 'wp-cloudflare-page-cache'); ?>

do_action("swcfpc_purge_cache");

do_action("swcfpc_purge_cache", array("https://example.com/some-page/", "https://example.com/other-page/"));