![]() You can learn more about the differences between Cloudflare and QUIC.cloud caching on the QUIC.cloud blog.Īnd if you have any other questions, please feel free to drop by our Slack workspace and talk to other people who have used a variety of CDN setups with LSCache.WordPress is the most popular content management systems on the internet today, powering some 25% of all websites. You can continue to use Jetpack for static content, if you switch to QUIC.cloud for everything else. Our recommendation is to try QUIC.cloud CDN, because QUIC.cloud is integrated with the LSCache plugin so that the content cached at the CDN level always is the same as that cached at your local server level. If you put Cloudflare in front of it, CF’s own cache is not as precise as LiteSpeed’s, and you risk serving outdated content. LiteSpeed Cache takes care of keeping the HTML cache up to date and accurate. The problem with this is that it introduces a bit of a conflict. You are using Jetpack for your static content, so I am guessing that what you are using Cloudflare for is the dynamic content (in other words, the HTML that is generate by WordPress). If you find an inaccuracy, please let us know! In the meantime, see our documentation site for the most up-to-date information.Īs I understand it, you don’t need to do anything special with LiteSpeed in order to use the Jetpack CDN.Ĭloudflare, though is another story. This content was last verified and updated in July of 2022.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |