NitroPack anyway to make it work?

Hi,
NitroPack is another caching system and as I have said many times in previous thread you cannot use more than one page caching system on any website. So, if you would like to use NitroPack you have to turn off wp cloudflare super page cache or vice versa.

The testing I have done with both of these plugins, I mostly get “cf-cache-status: EXPIRED” when I try to reload a page, but sometimes I will get the occasional “cf-cache-status: HIT” but it is short lived and often might only last a reload or two before going back to “EXPIRED”

– When using this plugin I need to check your site URL to test further without which it is hard to say. Also make sure that Tiered Cache is enabled inside Cloudflare dashboard.

In the header, I sometimes see x-wp-cf-super-cache” related values but often they are not there.

– This means there is another caching system at play here. Which can be another page caching plugin you have or some server level page caching. When using this plugin you have to make sure that there are no other page caching system active in your site both at the plugin level and on the server level so that this plugin can handle your page caching properly.

NitroPack is another caching system and as I have said many times in previous thread you cannot use more than one page caching system on any website.

Thank you Saumya, I don’t mean you to sound like a broken record ?? I was having trouble with the search function to review previous threads on the matter.

When using this plugin I need to check your site URL to test further without which it is hard to say.

I don’t think there is any point sharing my URL as I have both plugins enabled and since you have said both together are not supported. wp cloudflare super page works fantastic on it’s own!! I guess I have some decisions I need to make. Ideally if I can figure out a way server-side to stop CF from caching cart/check/account without using CF page rules then it might be a happy compromise.

Thanks for the awesome support.

I was having trouble with the search function to review previous threads on the matter.

– oh man! don’t even get me started on the search function of the wp support forum, I honestly think it’s broken as it never actually works the way it is supposed to.

I have some decisions I need to make. Ideally if I can figure out a way server-side to stop CF from caching cart/check/account without using CF page rules then it might be a happy compromise.

– When using this plugin it will make sure that those pages are not cached in CF. Are you talking about when not using this plugin or when using nitropack? Sorry I got confused.

– oh man! don’t even get me started on the search function of the wp support forum, I honestly think it’s broken as it never actually works the way it is supposed to.

Glad I’m not the only one then. It’s funny because the search is actually run by google ??

– When using this plugin it will make sure that those pages are not cached in CF. Are you talking about when not using this plugin or when using nitropack? Sorry I got confused.

Unfortunately I don’t get any where near the optimization improvements of NP when I use WPSPC alone or in combination with other optimization plugins. So I find it really hard to justify not using it.

I don’t full understand the magic wizardry under the hood of WPSPC. But if there were a way to actually disable the caching component and solely take advantage of the page specific bypass component then potentially I could get WPSPC and NP to work nicely together.

Otherwise if I could understand how WPSPC is instructing CF to bypass specific pages then perhaps I can write a plugin.

Otherwise if I could understand how WPSPC is instructing CF to bypass specific pages then perhaps I can write a plugin.

– WPSPC changes the cache-control header to tell CF when to cache and when not to (super simplified explanation).

WPSPC changes the cache-control header to tell CF when to cache and when not to (super simplified explanation).

Thanks @saumya. I’ll look into this further!

I know we have gone off the scope of your teams awesome plugin. But to anyone else following this I found a work around that works consistently well with WordPress/Woocommerce + Cloudflare + NitroPack.

Here’s what you do:
No changes to NitroPack required.
Setup a cloudflare work to bypass when it detects a wordpress/woocommerce cookie. Not need to add any page rule that I can see.
And presto both CF and NP will give you HIT when there are no WP/WC cookies active for the page.

Now, the interesting finding is that I would actually get slightly better pagespeed scores when you don’t use the Cloudflare worker caching. The difference of a few points. I don’t entirely understand why but I suspect there might be a little added latency to rule to CF worker. So I have decided to turn CF caching off. But I suspect if you a decent amount of traffic then maybe having CF caching on might help. I would have to do a load test to be sure.