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:lscwp:configuration:excludes [2017/12/20 16:13] Lisa Clarke [Do Not Cache Cookies] Added clarification |
litespeed_wiki:cache:lscwp:configuration:excludes [2020/05/04 13:40] Shivam Saluja |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== LSCWP Configuration Settings: Excludes ====== | + | ====== LiteSpeed Cache for WordPress Settings: Excludes ====== |
| + | **Please Note**: This wiki is valid for v2.9.x and below of the LiteSpeed Cache Plugin for WordPress. If you are using v3.0 or above, please see [[https://docs.litespeedtech.com/lscache/lscwp/overview/|the new documentation]]. | ||
| - | {{:litespeed_wiki:cache:lscwp:lscwp-settings-excludes.png?direct&800|}} | + | {{:litespeed_wiki:cache:lscwp:lscwp-settings-excludes.png?nolink|}} |
| + | |||
| + | ===== Force Cache URIs ===== | ||
| + | //empty string// | ||
| + | |||
| + | Paths containing the listed strings //WILL// be cached, regardless of any "non-cacheable" settings that may appear elsewhere. One per line. Each string will be compared to the REQUEST_URI server variable. If there is a match, the URI will be cached. To indicate the beginning of a string, add ''^'' to the beginning of the string. To do an exact match, add ''$'' to the end of the string. | ||
| + | |||
| + | ==== String Matching Examples ==== | ||
| + | |||
| + | Assume you have the following URIs: | ||
| + | - ''/recipes/baking/'' | ||
| + | - ''/recipes/baking/cakes'' | ||
| + | - ''/recipes/baking/brownies'' | ||
| + | - ''/popular/recipes/baking/'' | ||
| + | |||
| + | The string ''/recipes/baking/'' will match all four URIs. | ||
| + | |||
| + | The string ''/recipes/baking/$'' will match #1 (because ''$'' indicates exact match). | ||
| + | |||
| + | The string ''^/recipes/baking'' will match #1, #2, and #3 (because ''^'' indicates the beginning of the URI). | ||
| ===== Do Not Cache URIs ===== | ===== Do Not Cache URIs ===== | ||
| //empty string// | //empty string// | ||
| - | This should be a list of WordPress URLs that should not be cached. LiteSpeed Cache understands that there are some situations that should not be cached already, such as the WooCommerce checkout page. | + | Paths containing the listed strings will not be cached. One per line. Each string will be compared to the REQUEST_URI server variable. If there is a match, the URI will not be cached. To indicate the beginning of a string, add ''^'' to the beginning of the string. To do an exact match, add ''$'' to the end of the string. (See the **Force Cache URIs** setting above for examples of how the string matching works.) |
| ===== Do Not Cache Query Strings ===== | ===== Do Not Cache Query Strings ===== | ||
| Line 16: | Line 36: | ||
| //empty string// | //empty string// | ||
| - | This is a list of category //pages// that should not be cached. | + | By default all categories are cached. If you have categories that you wish to exclude from the cache, enter a list of the category slugs (one per line) in this box. |
| + | EXAMPLE: To exclude ''<nowiki>http://www.example.com/category/category-slug/</nowiki>'', insert ''category-slug''. | ||
| + | |||
| + | NOTE: If the category slug is not found, the category will be removed from the list on save. | ||
| ===== Do Not Cache Tags ===== | ===== Do Not Cache Tags ===== | ||
| //empty string// | //empty string// | ||
| - | This is a list of tag //pages// that should not be cached. | + | Tags are treated the same way as categories: cached by default, but ignored if entered by slug (one per line) in this box. |
| - | + | ||
| ===== Do Not Cache Cookies ===== | ===== Do Not Cache Cookies ===== | ||
| //empty string// | //empty string// | ||
| Line 36: | Line 57: | ||
| //empty string// | //empty string// | ||
| - | This is a list of user agents that should not be cached. Note that this means on a partial match of the user agent. | + | Specific user agents may also be excluded from cache. This means that if a visitor requests a page from your site via one of the listed user agents, they will not be served from the cache. You can enter user agents by name in this box, one per line. |
| + | NOTE: Partial matches are allowed. | ||
| ===== Do Not Cache Roles ===== | ===== Do Not Cache Roles ===== | ||
| //unchecked// | //unchecked// | ||
| There may be user roles that you wish to exclude from caching. For example, if you are an admin, testing new functionality, you may want to exclude your ''administrator'' role from being served from cache until your testing is through. | There may be user roles that you wish to exclude from caching. For example, if you are an admin, testing new functionality, you may want to exclude your ''administrator'' role from being served from cache until your testing is through. | ||