App for Cloudflare® Pro 1.9.2

[mcdeth]

Hi, does the plugin allow serving the same cache to logged-in users as to logged-out users? The cart icon is updated with cart fragments.

My second question is about compatibility: is the plugin fully compatible with WPML and WP All Import (R2 bucket support, if it was tested)? I often import products with disabled actions — will the plugin automatically detect missing R2 images via cron (or any other mechanism)?

 

[mcdeth]

and one more question, does the plugin allow dropping specific parameters in order to serve same cache (for example fbclicd, utm, but preserving other if needed for example orderby or custom)

 

[Shawn]

Hi, does the plugin allow serving the same cache to logged-in users as to logged-out users? The cart icon is updated with cart fragments.

It does not. It wouldn't make a lot of sense to serve cached content to logged in users since parts of the page is going to be unique to them (for example showing them they are logged in). If you *are* seeing cached content being delivered to logged in users, maybe your site is using non-standard cookies for logged in users? Part of what determines if someone is logged in, is the cookies that the user has set.

My second question is about compatibility: is the plugin fully compatible with WPML and WP All Import (R2 bucket support, if it was tested)? I often import products with disabled actions — will the plugin automatically detect missing R2 images via cron (or any other mechanism)?

Sorry, I don't know anything about either of those plugins. The R2 system works with WordPress Media, if they use WordPress Media it should work as long as they aren't trying to do anything non-standard as far as WordPress Media goes, if they aren't using WordPress Media, they definitely will not work with R2.

and one more question, does the plugin allow dropping specific parameters in order to serve same cache (for example fbclicd, utm, but preserving other if needed for example orderby or custom)

What you are talking about isn't anything specific to this plugin, rather it's a feature of Cloudflare itself. The ability to pick and choose certain things to use for the Cache Key is dependent on your Cloudflare plan. Specifically, the ability to drop certain query string parameters from being used in the cache key is only available if you have a Cloudflare Enterprise plan:

Cache keys

A Cache Key is an identifier that Cloudflare uses for a file in our cache, and the Cache Key Template defines the identifier for a given HTTP request.

developers.cloudflare.com

 

[mcdeth]

In my opinion, serving the same cache for both logged-in and logged-out (woocommerce) users is the optimal choice. Most of the time the only real difference is something small like the top header button saying “Log in” vs “My Account”. Modern UX patterns already rely more on icons/emojis anyway, so making the whole page dynamically uncached just to swap that tiny element doesn’t make much sense.


If you think about traffic scale — say you have 10k visits with 2k logged-in users and 8k logged-out — forcing two separate caches (or no cache at all for logged-in) means you’re adding thousands of extra unnecessary requests to your server, just for that one minor variation. That’s a lot of wasted resources with almost no benefit to the end user.

Woocommerce has introduced cart fragmentation long time ago to update cart icon with ajax very quickly, yet most people on internet will disable it to save 1 ajax request... but instead they dont use cache.

Of course, we are excluding some pages such as myaccount (just as excluding cart/checkout pages)

 

[Shawn]

Right, but you are talking about something different. You are talking about a partial cache that relies on your origin server to piece the page together. This is a network edge cache system where the request is served in full from Cloudflare data centers, without needing to go back to the origin server. If it was a cache that existed on the origin server, it could be done, but it's not that.

If your pages can be cached in full without touching the origin server for the page (like just if AJAX request is made to the origin to "fill in the blanks", then you certainly could do it without issue.