Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
litespeed_wiki:cache:litemage2:troubleshooting [2018/08/17 13:43] Lisa Clarke [Diagnose the Issue] |
litespeed_wiki:cache:litemage2:troubleshooting [2019/11/12 16:50] Jackson Zhang [Page Cache should be enabled under Cache Management] |
||
|---|---|---|---|
| Line 41: | Line 41: | ||
| {{ :litespeed_wiki:cache:litemage2:litemage-pagecache-enable.png?800 |}} | {{ :litespeed_wiki:cache:litemage2:litemage-pagecache-enable.png?800 |}} | ||
| + | |||
| + | ==== Enable debug "Yes and set X-LiteMage-Debug response headers" ==== | ||
| + | Staring from LiteMage 2.1.0, LiteMage introduces the "X-LiteMage-Debug response headers" feature and it will make your troubleshooting easier. When you tried everything in the wiki but you still could not see ""X-LiteSpeed-Cache: hit,litemage" header, you might consider to enable this debug feature to find out more information. | ||
| + | |||
| + | To enable this, you will need to go to Magento Admin -> Stores -> Advanced -> LiteMage Cache -> Developer Settings -> Enable Debug -> ''Yes and set X-LiteMage-Debug response headers''. You can also add your IP to "Log Debug Messages Only for Listed IPs" field to show such debug header to your IP only. | ||
| + | {{ :litespeed_wiki:cache:litemage2:litemage2-enable-debug-response-headers1.png?800 |}} | ||
| + | |||
| + | Then when you browse your site and use the browser developer tool to check the header: | ||
| + | |||
| + | {{ :litespeed_wiki:cache:litemage2:litemage2-enable-debug-response-headers2.png?800 |}} | ||
| + | |||
| + | Headers show: | ||
| + | x-litemage-debug-cc: | ||
| + | x-litemage-debug-info: Layout has uncacheable blocks mgs_gdpr_login_header, wishlist-link-header, wishlist_header, wishlist_header, | ||
| + | captcha-header | ||
| + | x-litemage-debug-tag: | ||
| + | x-litemage-debug-vary: | ||
| + | | ||
| + | which tells you ''Layout has uncacheable blocks mgs_gdpr_login_header, wishlist-link-header, wishlist_header, wishlist_header, | ||
| + | captcha-header'' and these blocks cause the page uncacheable. You may need to consider to disable such blocks or modify the template to make them ''cacheable''. | ||
| ==== Page is not cachable because of "cacheable" is set to "false"==== | ==== Page is not cachable because of "cacheable" is set to "false"==== | ||
| If you followed every step in the installation wiki and still do not see the ''X-LiteSpeed-Cache: hit,litemage'' header for that page/for all pages, it is likely that the page is non-cacheable due to a setting from another plugin. | If you followed every step in the installation wiki and still do not see the ''X-LiteSpeed-Cache: hit,litemage'' header for that page/for all pages, it is likely that the page is non-cacheable due to a setting from another plugin. | ||
| Line 129: | Line 149: | ||
| First visit: | First visit: | ||
| - | {{ :litespeed_wiki:cache:litemage2:litemage2-cache-very0.png?800 |}} | + | {{ :litespeed_wiki:cache:litemage2:litemage2-cache-vary0.png?800 |}} |
| Second Visit: | Second Visit: | ||
| - | {{ :litespeed_wiki:cache:litemage2:litemage2-cache-very1.png?800 |}} | + | {{ :litespeed_wiki:cache:litemage2:litemage2-cache-vary1.png?800 |}} |
| Third Visit: | Third Visit: | ||
| - | {{ :litespeed_wiki:cache:litemage2:litemage2-cache-very3.png?400 |}} | + | {{ :litespeed_wiki:cache:litemage2:litemage2-cache-vary3.png?400 |}} |
| Next, you can use another browser such as Firefox to simulate a different user and check the same page. On the first visit, you will see the cache vary cookie being set. The second visit, since the page has already been cached, you will see a cache hit. (If the page has not yet been cached, you will see cache miss on the second visit and cache hit on the third.) | Next, you can use another browser such as Firefox to simulate a different user and check the same page. On the first visit, you will see the cache vary cookie being set. The second visit, since the page has already been cached, you will see a cache hit. (If the page has not yet been cached, you will see cache miss on the second visit and cache hit on the third.) | ||