Do we have to use the WP Cloudflare plugin if we don’t use your CDN settings?

Yes, that is correct.

There must be a plugin installed that can instruct WordPress to replace the appropriate native static file links with CDN links. That can be the LiteSpeed Cache plugin, the Cloudflare plugin, or some other optimization plugin with CDN integration.

A CDN will not work on WordPress without a plugin (or creating some kind of function to do it yourself).

I hope this clears it up!

Hi Lisa

But can you explain me why for this website : https://www.casasuara.com and this file https://www.casasuara.com/min/9803c.js I get a response header like this :
cf-cache-status:HIT
x-litespeed-cache:miss

This website has just you plugin installed, no Cloudlare plugin, CDN setting tab to OFF.

Thanks

I can answer half of your question ??

LiteSpeed Cache is a miss because it’s a static file and we don’t cache static files.

I don’t know enough about CloudFlare to explain the hit on their end.

Hopefully my colleagues can jump in with more information about this.

Ok Lisa I’ll wait for more informations because I really wonder if CloudFlare Cache Plugin necessary.

Reading this https://fr.www.ads-software.com/plugins/cloudflare/ I do not see anywhere that this plugin do some special stuff except:
– One-click WordPress-optimized settings
– Automatic cache purge
– Prevent redirect loop
– Change Cloudflare settings from within the plugin itself
– View analytics

Thanks

Hi Pako,

You can set CDN from either LSCache>CDN or CloudFlare plugin or other CDN plugins. If you don’t use any other functions of cloudflare plugin, you may want to Deactivate it to keep everything simple.

Generally static file is not cached by LSCache, but your 9803c.js is minified by LSCache plugin, which is generated by php and should be cached. I guess cf-cache-status:HIT and x-litespeed-cache:miss is because CloudFlare cache litespeed’s headers already.

I dont see why we should add cdn.mydomain.com in litespeed CDN settings?
Cloudflare works if you have a plugin or not.

All the cloudflare plugin does is to activate standard settings optimized for wordpress.

So what changes when we add cdn.mydomain.com under CDN settings in litespeed plugin?

Jumping in the conversation here: you don’t have to use LiteSpeedCache’s CDN settings with Cloudflare. Everything is automatic but you may have to tweak some settings in Cloudflare backend.

Hi @yoav1987

If nothing is needed what is the purpose of this: https://blog.litespeedtech.com/2017/10/25/wpw-how-to-set-up-cloudflare-with-lscache/comment-page-1/ ?

And regarding the Cloudflare plugin, and I’m not talking about other plugins like @eric780217 said but only this one : https://fr.www.ads-software.com/plugins/cloudflare/
> This plugin is NOT NEEDED for LiteSpeed Cache plugin to work with CloudFlare as @lclarke said first, except if you want to change Cloudflare settings from within the plugin itself without needing to navigate to the cloudflare.com dashboard

I have read 15 pages of the support forum of this plugin, and the author said several times that his plugin is NOT needed for Cloudflare to work.

LiteSpeed Cache is a must have but we need to have a definitive and clear answer about using LiteSpeed Cache plugin + CloudFlare without forgetting to give us what should the Cloudflare settings should be (minify or not the js,css,html – Browser Cache Expiration, and so on).

Thanks ??

Pascal, I’m so sorry. The two of us that have been “helping” you have been acting on bad information.

Your arguments were starting to make sense to me, so I did some additional research and this is what I’ve found:

Most CDNs are reverse proxies. Traffic control happens at the site level – WP handles the dynamic content and sends the visitor to the CDN for the static content. This is what our CDN settings tab is for.

Cloudflare is not like other CDNs. It is a proxy. Traffic control happens at the Cloudflare level – CF handles the static content and sends the visitor to WP for the dynamic content. For this, our CDN settings tab is not useful.

So, you do not need a plugin to use Cloudflare. You should disable it in LiteSpeed Cache Settings.

Again, my apologies for the misinformation. Thank you for your persistence. I now have a blog post to update…

Oh, and in terms of minify, browser cache, etc., my advice would be to pick one location for those functions, and stick to it.

In other words, you can enable those functions at the LiteSpeed level (and then clear your CF cache), or you can enable them at the CF level. Just don’t enable them in both places.

Hi Lisa

‘So, you do not need a plugin to use Cloudflare‘
Yes ?? That’s was I’m saying

‘Our CDN settings tab is not useful…‘
..If we use CloudFlare and this information should be imperatively, in my opinion, written in bold in LiteSpeed Cache CDN Tab because a lot of people, like me, have lost a lot of time trying to understand your post: https://blog.litespeedtech.com/2017/10/25/wpw-how-to-set-up-cloudflare-with-lscache/comment-page-1/
> This post should be named: ‘WpW: How to Set Up CDN with LSCache but CloudFlare’ ??

But don’t confuse people while saying ‘You should disable it‘, nope, it’s not true. People can enable the Official Cloudflare plugin if they want additionals features, and this plugin will never hurt your plugin.

– –

And about the others stuff minify, browser cache, etc., I have completly disabled those options on CloudFlare because LiteSpeed Cache do it very well.
For the ‘Browser Cache Expiration’ CloudFlare settings I have leave it at “Respect existing headers” which are by default 1 month at the server level: https://www.ads-software.com/support/topic/cloudflare-setup/

I hope this thread will help people to find out some usefull information about using LiteSpeed Cache plugin and CloudFlare…

Thank you for your feedback.

I’m way ahead of you:
I’ve already re-written the entire blog post so that it is clearly not about Cloudflare anymore.

Additionally, I’ve suggested some new wording for the CDN tab in the next release.

And lastly, yes. I agree that the CF plugin has a completely different set of functions than I originally thought, and the advice to use “one or the other” was misguided and will not be repeated.

Again, my apologies for the time you’ve lost on this.