This is an old revision of the document!

LSCache + LiteSpeed WebADC

This guide explains how to set up LiteSpeed WebADC to communicate with WordPress (or other web apps that use an LSCache plugin) via the following structure:

LiteSpeed WebADC (With Cache) > Back end web server > WordPress Application

  • Navigate to LSLB Web Admin Console→Server→Cache
    1. Set Storage Path to /home/lscache/

  • Navigate to LSLB Web Admin Console→Virtual Hosts→Cache
    1. Set Storage Path to /home/Litespeed443/lscache
    2. Set Check Public Cache to Yes

  • Install and activate plugin for WordPress at backend web servers by following this Installation article

'Note 1': The above steps are for most applications other than Magento. You will need to install Litespeed cache plugin for that application at back end server, which is recommended way. If there is no plugin available at this time, you can setup cache on ADC through rewrite rules on each virtual host. 'Note 2': For Magento, you will need to set “Enable LiteMage” to “yes” on ADC and install LiteMage plugin at the backend of web servers.

You can check if a page is being cached from WebADC by:

  1. Navigating to your site from a non-logged-in browser and using your browser's developer tools to check the response header.
  2. Enter the URL http://[Back_end_web_server_IP]/[wordpress-path] and check that there is no cache from response header.
  3. Enter the URL http://[Web_ADC_IP]/[wordpress-path]. Reload the page and look for X-LiteSpeed-Cache: hit in the response headers. If it's there, then the page is being served by the cache.
  4. Modify a post with the WordPress application, then press Ctrl+F5 to refresh http://[Web_ADC_IP]/[wordpress-path], you should see the updated posts.

To turn on the Web ADC Debug Log, you would follow the exact same steps that are laid-out here for LiteSpeed Web Server.

  • Admin
  • Last modified: 2017/10/30 15:22
  • by Jackson Zhang