No “X-LiteSpeed-Cache: hit,litemage” Header

In a Magento 1.x store, if the X-LiteSpeed-Cache: hit,litemage header is missing, it is an indication that LiteMage is not working properly. There can be various causes for this problem, but most likely a step was missed in the LiteMage 1.x Installation Guide.

Go through this list, checking each item until you find what may be causing the problem.

This header indicates 3 things:

1. It didn't find the page in the cache.
2. When it loaded the page to display this time, it also cached a copy.
3. The next time you load the page, it will be served from cache.

If you see this header, refresh the page and check again. You should then see the X-LiteSpeed-Cache: hit,litemage header.

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.

Have you added LiteMage On to your store's .htaccess file?

Has Enable LiteMage Cache been set to Yes under LiteMage Configuration in the Magento admin?

If you host your Magento store on a shared hosting service account, please contact your hosting company to ensure that they have enabled LiteMage for your account.

If some pages are cached but others are not, you may have reached your license's cache object limit. In that case, you will need to upgrade LiteMage to a higher tier.

Have you or your host set the server-level & virtual-host-level cache root and cache policy?

Have other full page caches been disabled? You can only use one full page cache at a time, or there will be conflicts.

If you have set Enable LiteMage Cache Only for Listed IPs, is your IP listed?

For LiteMage to work correctly, you must have both Configuration and Layouts enabled under System → Cache Management. If you are using Magento Enterprise, you must also disable Page Cache.

Did you try flushing LiteMage Cache and Magento Cache Storage? Do so, and then reload the page a few times.

If you see the header x-litespeed-cache-control: esi=on, then the page is cachable but it has encountered a problem. You may have reached your license's cache object limit. Another possible cause is a conflict with another cache solutions, such as CloudFlare.

It's LiteMage's job to cache dynamic content, therefore, if you are going to use CloudFlare cache, it must be set up to only cache static content. See this blog post for more details.

If the cache vary cookie _lscache_vary_toolbar is set, then the page won't be cached for the first hit. This is expected bahavior. You should see X-Litespeed-Cache: miss on the second hit, and X-LiteSpeed-Cache: hit,litemage on the third hit.

First hit: See Magento frontend and frontend_cid cookie with LSCache vary header

Second hit: See Magento frontend and frontend_cid cookie with cache miss header

Third hit: See cache hit header