# Installation¶

Before installing and activating the LSCache plugin, deactivate all other full-page cache plugins.

Tip

You can still use other types of cache (like object cache), but only one page cache can be used at a time, so you’ll need to disable any other page caches, if you want to use LSCache.

## Server Configuration¶

Note

Please see the Overview for the server-level requirements before attempting to use LSCache.

## Extension Installation¶

1. Clone the Github repo
git clone https://github.com/litespeedtech/full-page-cache-addon

2. Copy the contents of cscart/* to your CSCart installation
rsync -a full-page-cache-addon/cscart/ /your/cscart/installation/

3. Append the contents of htaccess_lscache to your .htaccess
cat full-page-cache-addon/htaccess_lscache >> /your/cscart/installation/.htaccess

5. Scroll down to Full-page cache add-on and click the Install button.
6. Scroll down to Full-page cache add-on again, click the Disabled drop down, and change it to Active.

## Verify Your Site is Being Cached¶

You can verify a page is being served from LSCache through the following steps:

1. From a non-logged-in browser, navigate to your site, and open the developer tools (usually, right-click > Inspect). Open the Network tab.
2. Refresh the page.
3. Click the first resource. This should be an HTML file. For example, if your page is http://example.com/webapp/, your first resource should either be something like example.com/webapp/ or webapp/.
4. You should see headings similar to these:
X-LiteSpeed-Cache: miss
X-LiteSpeed-Cache-Control:public,max-age=1800
X-LiteSpeed-Tag:B1_F,B1_

These headings mean the page had not yet been cached, but that LiteSpeed has now stored it, and it will be served from cache with the next request.
5. Reload the page and you should see X-LiteSpeed-Cache: hit in the response header. This means the page is being served by LSCache and is configured correctly.

The X-LiteSpeed-Cache header is most common, but you may see X-LSADC-Cache if your site is served by LiteSpeed Web ADC. You may also see X-QC-Cache if your site was served via QUIC.cloud CDN. These alternate headers are also an indication that LSCache is working properly on your site.
If you don't see X-LiteSpeed-Cache: hit or X-LiteSpeed-Cache: miss (or any of the alternative headers), then there is a problem with the LSCache configuration.