# 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.

## Extension Installation¶

Note

Please see the Overview for the server-level requirements before attempting to install this extension.

wget https://github.com/litespeedtech/lscache_mediawiki/archive/master.zip

unzip master.zip

3. Find the .htaccess file in the MediaWiki root directory, or create one if it doesn't exist. Add the following to the file to enable LSCache at the server level:
<IfModule LiteSpeed>
CacheLookup on
</IfModule>

4. Move the LiteSpeedCache directory to /extensions in the MediaWiki directory
5. Edit LocalSettings.php in the MediaWiki root directory, and add the following near the end:
wfLoadExtension( 'LiteSpeedCache' );

6. Log into MediaWiki and from the administrator panel, navigate to Special pages > Data and Tools > LiteSpeed Cache.
7. Set LiteSpeed Public Cache Enabled to checked and click the Save Cache Setting button.

## 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, open the developer tools and navigate to your site. 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. If you see headings similar to
X-LiteSpeed-Cache: miss
X-LiteSpeed-Cache-Control:public,max-age=1800
X-LiteSpeed-Tag:B1_F,B1_

(for example), this means the page had not yet been cached, but that LiteSpeed has now stored it for future use.
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.
6. If you don't see X-LiteSpeed-Cache: hit or X-LiteSpeed-Cache: miss, then there is a problem with the LSCache configuration.

Last update: September 2, 2020