Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
litespeed_wiki:cache:lscjoomla:configuration:advanced [2020/02/03 14:54] Jackson Zhang [Clean Cache Secure Words] |
litespeed_wiki:cache:lscjoomla:configuration:advanced [2020/02/03 16:52] Lisa Clarke Copyediting last two sections |
||
---|---|---|---|
Line 5: | Line 5: | ||
===== ESI Feature Enabled ===== | ===== ESI Feature Enabled ===== | ||
- | LiteSpeed's implementation of ESI (Edge Side Includes) brings caching to the next level by allowing you to mix public and private content on a single page, and still serve that page from cache. ESI is a an important aspect of any ecommerce caching strategy. | + | LiteSpeed's implementation of ESI (Edge Side Includes) brings caching to the next level by allowing you to mix public and private content on a single page, and still serve that page from cache. ESI is an important aspect of any eCommerce caching strategy. |
- | ESI is enabled by default in the plugin, but you can turn it off, if you don't need it. You can not use OpenLiteSpeed for this feature since OLS doesn't support ESI at all. For LiteSpeed Enterprise, normally the ESI feature is disabled by default on server level. You will need to enable ESI on LSWS before using ESI related features. Please check this wiki on [[litespeed_wiki:cache:common_installation:shared-enable-individually|how to enable ESI on LSWS for control panel or native environment]]. | + | ESI must be enabled both in the plugin and at the server level. ESI is enabled by default in the plugin (but you can turn it off, if you don't need it). The ESI feature is //disabled// by default at the server level. You will need to [[litespeed_wiki:cache:common_installation:shared-enable-individually|enable ESI in LiteSpeed Enterprise]] before using ESI-related features in the plugin. |
+ | |||
+ | **Please Note**: OpenLiteSpeed does not support ESI, so you cannot use this feature with OpenLiteSpeed. | ||
Want to learn more about ESI? [[https://blog.litespeedtech.com/2017/09/06/wpw-esi-and-litespeed-cache/|This blog post]] explains it from a WordPress point of view, but the concepts are the same for Joomla. Anywhere you see the word "widget," just think "module." | Want to learn more about ESI? [[https://blog.litespeedtech.com/2017/09/06/wpw-esi-and-litespeed-cache/|This blog post]] explains it from a WordPress point of view, but the concepts are the same for Joomla. Anywhere you see the word "widget," just think "module." | ||
Line 40: | Line 42: | ||
===== Web interface to purge all LiteSpeed Cache ===== | ===== Web interface to purge all LiteSpeed Cache ===== | ||
- | Click ''Web interface to purge all LiteSpeed Cache'' URL and it will manually purge call LiteSpeed Cache. | + | To manually purge all LiteSpeed Cache from the web interface, click the **Web interface to purge all LiteSpeed Cache** URL. You can bookmark this URL to avoid logging into the Joomla backend in the future. |
- | ===== Web interface to rebuild all LiteSpeed Cache ===== | + | ===== Web Web interface to rebuild all LiteSpeed Cache ===== |
- | It is the crawler function to regenerate all caches. You can manually run this crawler by clicking the URL when needed or set up a cron job to do so periodically. Please check [[litespeed_wiki:cache:lscjoomla:crawler|this wiki]] for details. | + | To manually start the crawler to rebuild all LiteSpeed Cache, click the **Web interface to rebuild all LiteSpeed Cache** URL. You can also [[litespeed_wiki:cache:lscjoomla:crawler|set up a cron job]] to do this periodically. |