How to enable caching on Turbo servers

This article describes how to enable caching on the following Turbo hosting packages:

• Turbo Velocity and Turbo Nitro Web Hosting accounts.
• Turbo Managed VPS.
• Turbo Managed Dedicated server.

Enabling caching

By default, caching is disabled on Turbo accounts. To enable caching for your account, you use directives in an .htaccess file. These directives enable you to control precisely which types of content the Turbo server caches, and for how long. You should create the .htaccess file in the base folder for the application that you want to cache.

The following sample configuration demonstrates how to enable caching on a Turbo account:

<IfModule LiteSpeed>
    RewriteEngine On
    RewriteCond %{REQUEST_METHOD} ^GET|HEAD$
    RewriteCond %{HTTP_HOST} ^example.com [NC]
    RewriteCond %{REQUEST_URI} !login|admin|register|post|cron
    RewriteCond %{QUERY_STRING} !nocache
    RewriteRule .* - [E=Cache-Control:max-age=300]
</IfModule>

Let's go through this example configuration line by line:

• The first line checks to make sure the web server is running LiteSpeed.
  Strictly speaking, you do not have to use this line (and its corresponding line at the end of the file), but it is good practice to do so, particularly if you use the .htaccess file on a different server in the future.
• The second line turns on URL rewrite functionality. Turbo servers use rewrite conditions and rules to control caching behavior.
• The third, fourth, and fifth lines use RewriteCond directives to specify what should and should not be cached. The REQUEST_METHOD condition instructs the server to cache GET and HEAD requests, but not POST requests. The REQUEST_URI condition, because it begins with an exclamation mark (!), instructs the server to not cache any page whose URL contains login, admin, register, post, or cron.
  To add additional strings to the REQUEST_METHOD or REQUEST_URI conditions, use the pipe symbol (|) to separate them.
• The QUERY_STRING configuration line enables you to see the non-cached version of any page by adding nocache to a query string in the URL. For example, to view the non-cached version of http://example.com/mypage, you could add ?any_field=any_value&nocache to the end of the URL.
• The RewriteRule directive actually sets the cache duration. In this example, pages are cached for five minutes (300 seconds).

X-LiteSpeed-Cache: hit

Caching and static content

Turbo accounts do not cache static content, such as audio and image files, on the web server. This type of content is cached by client web browsers instead. However, you can specify how long web browsers should cache your static content by using the ExpiresByType directive in the .htaccess file. For example, the following lines instruct web browsers to cache MP3 files for one year (31557600 seconds) and GIF files for 30 days (2592000 seconds):

ExpiresByType audio/mp3 A31557600
ExpiresByType image/gif A2592000

For more information about the ExpiresByType directive, please visit https://httpd.apache.org/docs/2.4/mod/mod_expires.html#ExpiresByType.

More Information

For detailed information about caching behavior on a server running LiteSpeed, please visit http://www.litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:litespeed:cache.