CDN Settings Tab¶
If you currently use a content delivery network, you can configure LSCWP so that they work together.
Turn this option
ON to use LiteSpeed's QUIC.cloud CDN.
Use CDN Mapping¶
If you set up multiple CDN paths with the same settings, the last one will overwrite the others.
This setup is not necessary for Cloudflare or other distributed proxy networks. Only use CDN mapping for reverse proxy content delivery networks! If you wish to manage your Cloudflare cache from within LSCache, skip most of this page and jump to the Cloudflare API setting.
Cloudflare may also be set up as a static content CDNS (as opposed to its default use as a distributed proxy network). Setup is different in that case. See a video demonstration of How to Use CloudFlare as a Static Content CDN with LSCWP here.
This is the base URL for content that is served from this CDN. It should be a full URL beginning with
Turn this on to serve all images through this CDN. This includes image attachments, HTML
<img> tags, and CSS
Turn this on to serve all CSS files through this CDN.
Include File Types¶
default file types
Use this spot to list, one per line, the file types that are to be served from this CDN. These should be static files. This setting affects all of the following HTML tags:
href. The default file types included in this setting are:
.aac .css .eot .gif .jpeg .js .jpg .less .mp3 .mp4 .ogg .otf .pdf .png .svg .ttf .woff
If you have turned off any of the previous three settings, you will need to remove the corresponding file extensions from this Include File Types box.
For example, if Include CSS is set to
OFF, then remove
.less from the list.
your site URL(s)
This setting defaults to your site's base URL. It shouldn't be necessary to change this. If you do change it, be sure that the URL begins with
// as in
//yoursite.com. You may use a wildcard (
*) here to specify 0 or more characters.
If your site spans multiple base URLs, you may enter them all here, separated by commas. For example:
//a.yoursite.com, //b.yoursite.com, //c.yoursite.com
These are the directories that will be served by CDN. You shouldn't need to change this unless you have a non-standard configuration.
list of paths to exclude from CDN
Use this spot to list file paths that you explicitly do not want to have served from the CDN. List them one per line. You can list a path in its entirety, or use a partial path that will be matched. Do not use wildcards.
Load JQuery Remotely¶
This setting has been deprecated.
Cloudflare isn't like other CDNs. You should not set Use CDN Mapping to
ON for Cloudflare. However, you can manage your Cloudflare cache through this plugin, if you wish. Simply set Cloudflare API to
ON and then fill in the three fields below. Once the settings are saved, you will be able to manage your Cloudflare cache through the LiteSpeed Cache > CDN > Manage area.
Enter the email address you use with your Cloudflare account.
Global API Key¶
Enter the API key you were given by Cloudflare. You can find it on your Cloudflare profile.
Enter the domain name served by Cloudflare. You needn't enter the entire domain here. If you enter only part of it, the remainder of the domain will be filled-in automatically after save.
CDN Manage Tab¶
LSCache for WordPress provides a mechanism for managing certain external CDN accounts, eliminating the need for an extra plugin.
If you wish to use QUIC.cloud CDN, you can find all of the management tools on your QUIC.cloud dashboard.
Before you can use the functions in this section, you will need to set up the Cloudflare API in the settings. Navigate to LiteSpeed Cache > Settings > CDN and set Cloudflare API to
Once the API settings are saved, the elements of this area will be populated.
This is the domain that you have configured to be served by Cloudflare. It is informational only and cannot be changed here. If it is in error, you will need to fix it in your Cloudflare account.
This is the unique id that was assigned to your domain by Cloudflare. It is informational only and cannot be changed here. You can see it on your Cloudflare profile.
These buttons allow you to turn on Development Mode, turn it off, and check to see whether it is running. If you are making updates to your site, and want to verify that they are working as planned, Development Mode allows you to temporarily disable Cloudflare so that you may see your updates in realtime.
After three hours, Development Mode will turn itself off, or you can turn it off manually via the button provided.
Press the Purge Everything button to purge your Cloudflare cache on demand. This is helpful if you have made changes that result in an LSCache purge, and you want to make sure Cloudflare is up-to-date.