• Resolved The cPanel Guy

    (@thecpanelguy)


    I am trying to determine the “proper” configuration for Cloudflare while using Litespeed-cache. Specifically, whether the official Cloudflare plugin is compatible with the Cloudflare functionality built-in to the Litespeed-cache plugin.

    I do understand that running both in unison can cause problems with minify, js and various other features. However, I’ve read that there is still benefit to using both, despite the warning in the UX that indicates potential compatibility concerns.

    1. Should we setup both for our customer’s caching needs?
    2. Should we disable the Cloudflare API & QUIC features of LSCWP if Cloudflare plugin is installed?
    3. Should we disable conflicting features in one over the other? Is there a preference for which one should be the authority for these features? (i.e. minify and other conflicting features)

    Essentially just trying to understand the “Best Practice” for co-mingling these two plugins or is the built-in CF API/QUIC features sufficient as-is or should we let the CF plugin handle these tasks.

    Thanks in advance for any advice.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • In principle, you can also use the CF plugin, but you will then have to deactivate the settings for webp replacement, guest mode and cache mobile, as CloudFlare neither recognizes nor supports these functions. Otherwise you will get significant glitches and malfunctions, which is also the reason why the LiteSpeed Cache Plugin indicates that the CF is not compatible with the LiteSpeed Cahe Plugin. The simple explanation for this is that both plugins do almost, but only almost, the same thing, but the CloudFlare plugin is not compatible with the special optimization functions. That’s why I recommend you use quic.cloud instead of CouldFlare, because this is the only way you can use the advantages of a CDN while using a page cache.

    Plugin Support qtwrk

    (@qtwrk)

    1. it is generally , NOT recommended to use multiple page cache plugin simultaneously
    2. it doesn’t affect a thing , the CF API is to create a shortcut button for CF’s purge everything , and QC CDN , if you did not map the CNAME , it won’t have any effect at all.
    3. if you are going to use CF page cache , then yes, you need to disable the conflicting features , otherwise the page may result in broken status.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Litespeed Cache vs Cloudflare Plugins’ is closed to new replies.