Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
litespeed_wiki:cache:webadc [2017/10/30 15:22] Jackson Zhang [Enable cache on Web ADC] |
litespeed_wiki:cache:webadc [2020/11/18 15:36] (current) Lisa Clarke Redirect to new Documentation Site |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== LSCache + LiteSpeed WebADC ====== | + | ~~REDIRECT>https://docs.litespeedtech.com/products/lsadc/cache/~~ |
| - | + | ||
| - | 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 | + | |
| - | + | ||
| - | ===== Enable cache on Web ADC ===== | + | |
| - | * Navigate to **LSLB Web Admin Console→Server→Cache** | + | |
| - | - Set **Storage Path** to ''/home/lscache/'' | + | |
| - | {{:litespeed_wiki:cache:adc-server.png?|}} | + | |
| - | * Navigate to **LSLB Web Admin Console→Virtual Hosts→Cache** | + | |
| - | - Set **Storage Path** to ''/home/Litespeed443/lscache'' | + | |
| - | - Set **Check Public Cache** to ''Yes'' | + | |
| - | {{:litespeed_wiki:cache:adc-vh.png?|}} | + | |
| - | * Install and activate plugin for WordPress at backend web servers by following this [[litespeed_wiki:cache:lscwp:installation#installation|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. | + | |
| - | ===== Testing ===== | + | |
| - | + | ||
| - | You can check if a page is being cached from WebADC by: | + | |
| - | - Navigating to your site from a non-logged-in browser and using your browser's developer tools to check the response header. | + | |
| - | - Enter the URL ''<nowiki>http://[Back_end_web_server_IP]/[wordpress-path]</nowiki>'' and check that there is no cache from response header. | + | |
| - | - Enter the URL ''<nowiki>http://[Web_ADC_IP]/[wordpress-path]</nowiki>''. 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. | + | |
| - | - Modify a post with the WordPress application, then press Ctrl+F5 to refresh ''<nowiki>http://[Web_ADC_IP]/[wordpress-path]</nowiki>'', you should see the updated posts. | + | |
| - | + | ||
| - | ===== Turning On the Web ADC Debug Log ===== | + | |
| - | To turn on the Web ADC Debug Log, you would follow the exact same steps that are laid-out [[litespeed_wiki:config:toggle-debug-logging|here]] for LiteSpeed Web Server. | + | |