mrlb

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.

Thanks for your reply @silvenatodorova

NitroPack is working great there is no doubt about that.

The issue is getting cloudflare to cache and bypass appropriately – and with the limitation of three rules it is simply not possible to achieve a desirable result.

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.

• This reply was modified 2 years, 12 months ago by mrlb.

– 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.

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’m not using a CDN. The images are coming from a secure CDN though. TH issue is caused by a certificate issue. If you visit the site for the first time (in any browser) it tell you the certificate is invalid.

cdn.printfriendly.com uses an invalid security certificate.

The certificate is only valid for the following names:
*.cloudfront.net , cloudfront.net

** I am reporting a bug for the printfriendly plugin. I just realized it’s not very obvious (from title) so I might report it.

Well it should work from any domain as some as you submit the right POST parameters to wp-login.php e.g

wp-login.php?log=username&pwd=password&wp-submit=Log+In&testcookie=1

If you use ajax you can submit this POST string e.g

var dataString = log=username&pwd=password&wp-submit=Log+In&testcookie=1;
$.ajax({
type: “POST”,
url: “/wp-login.php”,
data: dataString,
success: function() {
//jquery example to update the form on success.
$(‘#login_form’).html(“<div id=’message’></div>”);
$(‘#message’).html(“<h2>Logged In!</h2>”);
});
}
});
return false;

After your Ajax POST query has run, if you’re wordpress login was successful you should have a wordpress authentication cookie on your system which will let you use wp-admin.

Mmm I don’t think curl or any other sort of php library will work for remote login. I tried doing a similar thing like you but the problem is wp-login needs to return a cookie to the client requesting machine. In this case since curl is making the reuqest (from the server) the client never gets the cookie and as such when you try visit wp-admin you get directed back to wp-login.

I was able to do what you are trying to do using jquery and ajax. The down side is that the users browser must support javascript or it must be enabled.