Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Last revision Both sides next revision | ||
|
litespeed_wiki:cache:no-plugin-prestashop [2017/01/04 14:25] Michael Alegre created |
litespeed_wiki:cache:no-plugin-prestashop [2017/08/14 19:47] Lisa Clarke Added note to indicate this page has been deprecated |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== LSCache + PrestaShop Configuration ====== | ====== LSCache + PrestaShop Configuration ====== | ||
| - | LSCache, similar to Varnish cache, is a simpler and more efficient page caching solution built-in to LiteSpeed Web Server. When used in conjunction with PrestaShop, you can expect significant performance gains with a quick and easy setup. Cache management is also made significantly easier and more flexible with the ability to use rewrite rules to customize cache behavior. | + | **Note: This page describes an easy way to set up simple caching for PrestaShop installations. With the release of LiteSpeed Cache for PrestaShop, though, this solution is now deprecated. [[litespeed_wiki:cache:lscps|Click here]] for the LiteSpeed Cache for PrestaShop installation and configuration manual.** |
| + | |||
| + | LSCache, similar to Varnish cache, is a simpler and more efficient page-caching solution built in to LiteSpeed Web Server. When used in conjunction with PrestaShop, you can expect significant performance gains with a quick and easy setup. Cache management is also made significantly easier and more flexible. While the LiteSpeed cache plugin for Prestashop is still in development, rewrite rules can be used to customize LSCache's behavior. | ||
| Below are some recommended configurations to enable LSCache and get it working with your PrestaShop site(s). | Below are some recommended configurations to enable LSCache and get it working with your PrestaShop site(s). | ||
| - | ===== Server Level Settings ===== | + | ===== Configure Server/Virtual-Host-Level Cache Root And Cache Policy ===== |
| - | From the LSWS WebAdmin Console navigate to **Server >> Cache**. | + | Server/Virtual-Host-level cache storage needs to be configured properly for your environment. Select your server setup from the **Web Server Configuration** section of our [[litespeed_wiki:cache:common_installation#web_server_configuration|LiteSpeed Cache Installation Guide]] and follow the instructions to set the server/virtual-host-level cache root and cache policy. |
| - | Under **Cache Storage Settings**, set **Storage path** to the directory you want to use to store cached objects. | + | ===== Rewrite Rules ===== |
| - | For example: | + | At the top of your ''.htaccess'' file, located in the document root of your PrestaShop installation, add the following: |
| - | + | ||
| - | Storage Path: /tmp/diskcache | + | |
| - | + | ||
| - | It is recommended that this directory be on a dedicated disk or disk array in RAID 0 configuration. | + | |
| - | + | ||
| - | Under **Cache Policy**, we recommend using the following settings: | + | |
| - | + | ||
| - | Enable Cache:No | + | |
| - | Cache Request with Query String:Yes | + | |
| - | Cache Request with Cookie:Yes | + | |
| - | Cache Response with Cookie:Yes | + | |
| - | Ignore Request Cache-Control:Yes | + | |
| - | Ignore Response Cache-Control:Yes | + | |
| - | Enable Private Cache: No | + | |
| - | + | ||
| - | **Note:** **Enable Cache** has been set to “No” globally as caching will instead be enabled through the use of rewrite rules to control what pages will be cached and for how long. | + | |
| - | + | ||
| - | ===== Website Level Settings ===== | + | |
| - | + | ||
| - | At the top of your .htaccess file, located in the document root of your PrestaShop installation, add the following: | + | |
| ########## Begin - Litespeed cache | ########## Begin - Litespeed cache | ||
| <IfModule LiteSpeed> | <IfModule LiteSpeed> | ||
| - | CacheEnable public | ||
| RewriteEngine On | RewriteEngine On | ||
| + | CacheDisable public / | ||
| RewriteCond %{REQUEST_METHOD} ^GET|HEAD|PURGE$ | RewriteCond %{REQUEST_METHOD} ^GET|HEAD|PURGE$ | ||
| - | RewriteCond %{HTTP_HOST} ^your_domain_name.com [NC] | + | RewriteCond %{HTTP_HOST} ^(www.)?your_domain_name.com [NC] |
| - | RewriteCond %{REQUEST_URI} !admin_folder|404|address|authentication|best-sales|cart|contact|discount|guest-tracking|history|identity|order|password|products-comparison|search|account|friend|login|logout|addresses|contact-us|order-history|my-account|order-confirmation|order-follow|quick-order|credit-slip|password-recovery [NC] | + | RewriteCond %{REQUEST_URI} !your_admin_folder|404|address|authentication|best-sales|cart|contact|discount|guest-tracking|history|identity|order|password|products-comparison|search|account|friend|login|logout|addresses|contact-us|order-history|my-account|order-confirmation|order-follow|quick-order|credit-slip|password-recovery [NC] |
| RewriteCond %{HTTP_COOKIE} !logged|cart [NC] | RewriteCond %{HTTP_COOKIE} !logged|cart [NC] | ||
| RewriteCond %{QUERY_STRING} !nocache [NC] | RewriteCond %{QUERY_STRING} !nocache [NC] | ||
| Line 47: | Line 29: | ||
| ########## End - Litespeed cache | ########## End - Litespeed cache | ||
| | | ||
| - | Where "your_domain_name.com" is the web address of your Drupal site and "admin_folder" is the PrestaShop administration folder name specified during installation. | + | ====Notes==== |
| - | + | ||
| - | **Note:** For any friendly URLs included in the REQUEST_URI configuration line, make sure any corresponding translated (rewritten) URLs are also included. (To view friendly URLs in the PrestaShop administration interface, click Preferences >> SEO & URLs.) | + | |
| - | + | ||
| - | We recommend using a different domain for your backend so that you can add/edit/preview a website's content through the admin domain without worrying about these changes being cached and seen by visitors. | + | |
| - | To get the non-cached version of a page, add the "nocache" query string to a URL. | + | * The ''CacheDisable public /'' directive is used to help protect against globally-enabled caching and is optional. If this directive is not used, the server's global cache settings should be checked to ensure that cache is not enabled globally. **Do NOT** use ''CacheEnable public /'' here as it will enable caching for all URLs belonging to this virtual host, including admin pages. |
| + | * ''your_domain_name.com'' is the web address of your PrestaShop site and ''your_admin_folder'' is the PrestaShop administration folder name specified during installation. Replace them with your real domain name and admin folder. | ||
| + | * For any friendly URLs included in the ''REQUEST_URI'' configuration line, make sure any corresponding translated (rewritten) URLs are also included. (To view friendly URLs in the PrestaShop administration interface, navigate to **Preferences > SEO & URLs**.) | ||
| + | * We recommend using a different domain for your backend such as backend.your_domain_name.com so that you can add/edit/preview a website's content through the admin domain without worrying about these changes being cached and seen by visitors. | ||
| + | * To get the non-cached version of a page, add the ''nocache'' query string to a URL. | ||
| For example | For example | ||
| Line 60: | Line 42: | ||
| https://www.your_domain_name.com/about?some_other_query_string&nocache | https://www.your_domain_name.com/about?some_other_query_string&nocache | ||
| - | ===== Discussion ===== | + | ===== Verify Cache Setup ===== |
| - | __**Adding a cron job to delete outdated cache files**__ | + | |
| - | While optional, it is a good idea to clear out old cache files that are past the set **Time To Live (TTL)**. To do this enter the following in /etc/crontab | + | Look for ''X-LiteSpeed-Cache: hit'' in the reply headers. [[litespeed_wiki:cache:no-plugin-setup-guidline#verify_that_pages_are_served_from_the_cache|See more detailed directions here]]. |
| - | /10 * * * * root find /tmp/diskcache -type f -mmin +8 -delete 2>/dev/null | + | ===== Deleting Outdated Cache Files Using A Cron Job ===== |
| - | **Note:** This cron job deletes cached files that are more than 8 minutes old every 10 minutes. Since the cache TTL is set at 120 seconds (2 minutes), it is safe to delete these files that are way passed TTL. | + | Please refer to [[litespeed_wiki:cache:no-plugin-setup-guidline#deleting_outdated_cache_files_using_a_cron_job|this wiki]] to learn how to clean up outdated cache files. |