Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:cache:litemage:troubleshooting:no-cache-hit-header [2018/08/07 17:41]
Jackson Zhang [Did you turn off CDN cache?]
+++ litespeed_wiki:cache:litemage:troubleshooting:no-cache-hit-header [2019/05/17 14:34]
Kacey Schroeder [For Your License?]
@@ Line 16: / Line 16: @@
 ===== Is LiteMage Enabled... =====
 ==== For Your License? ====
-For 1-CPU and lower licenses, you will need to purchase LiteMage as an add-on, while LiteMage starter is included in all 2-CPU and above license. If you just recently upgraded your license by adding LiteMage, you will need to register a new license key with the ''.../lsws/bin/lshttpd -r'' command and then restart LSWS.
+For 1-CPU and lower legacy licenses, you will need to purchase LiteMage as an add-on, while LiteMage Starter + LSCache is included in all of the current licenses as well as the legacy 8-CPU license. If you just recently upgraded your license by adding LiteMage, you will need to register a new license key with the ''.../lsws/bin/lshttpd -r'' command and then restart LSWS.
 ==== In Your Configuration? ====
@@ Line 45: / Line 45: @@
 Did you try flushing LiteMage Cache and Magento Cache Storage? Do so, and then reload the page a few times.
-===== Reach your license's cache object limit? =====
+===== Have You Reached Your License's Cache Object Limit? =====
-If you see the header ''x-litespeed-cache-control: esi=on'', then the page is cachable but it has encountered a problem. one of the possible reason is LiteMage may have reached your license's cache object limit. You should check Magento Admin LiteMage stats for details.
+If you see the header ''x-litespeed-cache-control: esi=on'', then the page is cachable, but it has encountered a problem. One possible reason is that LiteMage may have reached your license's cache object limit. You should check your Magento Admin LiteMage stats for details.
-===== Did you turn off CDN cache? =====
+===== Are You Using CDN Cache? =====
-CDN cache solutions may be conflicted with LiteMage, such as CloudFlare cache, Sucuri cache etc. Please make sure to turn off CDN cache when using LiteMage.
+CDN cache solutions, such as CloudFlare cache, Sucuri cache etc., may conflict with LiteMage. Please make sure to turn off CDN caches when using LiteMage.
+This example shows CloudFlare cache enabled:
 {{:litespeed_wiki:cache:litemage:troubleshooting:litemage-cloudflare-incorrectcachesetting.png?direct&300}}
-Another example when the user using sucuri and turn on cache on sucuri, you always see **"x-litespeed-cache: miss"**:
+Here's another example, where the user has turned on cache in Sucuri. In this case, you will always see ''x-litespeed-cache: miss'':
 {{ :litespeed_wiki:cache:litemage:troubleshooting:litemage-cdn-cache-problem1.png?800 |}}
-If you visit backend directly with sucuri, LiteMage is running fine with **"x-litespeed-cache: hit,litemage"**:
+If you visit the backend directly with Sucuri, you can see LiteMage running fine with ''x-litespeed-cache: hit,litemage'':
 {{ :litespeed_wiki:cache:litemage:troubleshooting:litemage-cdn-cache-problem2.png?500 |}}
 It's LiteMage's job to cache dynamic content, therefore, if you are going to use CloudFlare/Sucuri cache, it must be set up to only cache //static// content. See [[https://blog.litespeedtech.com/2017/11/20/magento-monday-litemage-cdns-and-tokens/|this blog post]] for more details.
 ===== Is There a Vary Cookie Issue? =====
@@ Line 82: / Line 81: @@
 {{:litespeed_wiki:cache:litemage:troubleshooting:litemage-right-cookie-header-with-lscache-very-miss-hit.png?direct&800}}
+===== Are There Cache-Related Rewrite Rules in .htaccess? =====
+Please don't place ''RewriteRule (.*) - [E=Cache-Control:no-cache]'' in your ''.htaccess'' file. In fact, don't place //any// rewrite-rule-based cache directives into ''.htaccess'', unless there is a wiki or KB article instructing you to do so.
+Normally if you follow our wiki, LiteMage should work out of the box after installation, with no need to manually add anything. We have seen user-added rules break LiteMage and cause the cache miss header to display all the time.