![\"\"](\"https:\/\/lswp.store\/wp-content\/uploads\/2017\/11\/null.png\" "\\"\\"")
<\/p>\n<\/p>\n
Welcome to another installment of WordPress Wednesday<\/a>!<\/p>\n Disclaimer<\/strong>: The information contained in this post is accurate for LSCWP v5.0. If you are using a newer version of the plugin, some details may have changed. Please refer to our documentation<\/a> for the latest!<\/p>\n LiteSpeed Cache for WordPress has the ability to support your Content Delivery Network usage<\/a>. This quick guide should explain how the different settings between your CDN and LiteSpeed relate to each other.<\/p>\n Make sure you have set up your Cloudflare account on the Cloudflare website. Once that’s done, switch over to your WordPress Dashboard and navigate to LiteSpeed Cache > CDN > CDN Settings<\/strong>.<\/p>\n To manage Cloudflare through the LSCache plugin, set the following:<\/p>\n NOTE<\/strong>: You can also use Cloudflare without managing it through LSCache. If that is what you choose, just set Cloudflare API<\/strong> to The QUIC.cloud onboarding process<\/a> is documented in the QUIC.cloud Knowledge Base, and explains how to set up everything from the LSCache plugin to your QUIC.cloud Dashboard.<\/p>\n For this guide, we\u2019re going to assume you have already set up your CDN account, and added your site (let\u2019s call it Make sure that your CDN is configured to cache static files only. Dynamic content will be handled by LiteSpeed.<\/p>\n Your CDN configuration screen should have an area for adding a CNAME record. Look for it under DNS Editor<\/strong> or something along those lines.<\/p>\n The goal here is to set up a custom domain to be used only by the CDN. For example, Once that is complete, and the domain is active, we\u2019ll be ready to tell WordPress how to proceed.<\/p>\n Now that your CDN is set up and your static content is ready to be served by the CDN, you will need to let WordPress know about it. You can do this through LiteSpeed Cache.<\/p>\n In your WordPress Dashboard, navigate to LiteSpeed Cache > CDN > CDN Settings<\/strong>.<\/p>\n Make sure both QUIC Cloud CDN<\/strong> and Cloudflare API<\/strong> are set to The remaining settings can be left as-is, unless you have a specific reason to change them. If you do want to adjust them, this documentation should help<\/a>.<\/p>\n And that\u2019s it! Once you save your changes, LiteSpeed Cache for WordPress will substitute the CDN URL for the Original URL in the static copies it saves of your dynamically-generated code, wherever appropriate.<\/p>\n Want to learn more about how all of this works? We\u2019ve written about our CDN support in some depth before. You can check that out here<\/a>.<\/p>\n —<\/p>\n Have some of your own ideas for future WordPress Wednesday<\/a> topics? Leave us a comment!<\/p>\n Don\u2019t forget to meet us back here next week for the next installment. In the meantime, here are a few other things you can do:<\/p>\nCloudflare<\/h2>\n
\n
OFF<\/code><\/li>\nOFF<\/code>, and leave all settings under it alone<\/li>\nON<\/code>, and fill in your Email Address<\/strong>, Global API Key<\/strong>, and Domain<\/strong><\/li>\n<\/ul>\nOFF<\/code>, and leave all settings under it alone. Cloudflare will work either way. The advantage of setting this up in LSCache is that you may purge your Cloudflare cache or enable Cloudflare’s Development Mode from within LSCache. If that doesn’t matter to you, feel free to skip this setup.<\/p>\nQUIC Cloud<\/h2>\n
Other Reverse-Proxy CDNs<\/h2>\n
CNAME setup in the CDN<\/h3>\n
example.com<\/code>) according to the CDN\u2019s instructions.<\/p>\ncdn.example.com<\/code>. Follow the CDN\u2019s instructions for adding the CNAME record.<\/p>\nLiteSpeed Cache CDN Settings<\/h3>\n
OFF<\/code>.<\/p>\n![\"\"](\"https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/lscwp-cdn-1.png\")
<\/p>\n![\"\"](\"https:\/\/lswp.store\/wp-content\/uploads\/2017\/10\/lscwp-cdn-2.png\")
<\/p>\n\n
ON<\/code>.<\/li>\nhttp:\/\/cdn.example.com<\/code>.<\/li>\n\/\/example.com<\/code>.<\/li>\n<\/ul>\n