Lighttpd

{{{
#!rst ===============================================
Controlling the Expiration of Content in Caches ===============================================

------------------
Module: mod_expire
------------------

.. meta::
:keywords: lighttpd, expire

.. contents:: Table of Contents

Description ===========

mod_expire controls the Expire header in the Response Header of HTTP/1.0
messages. It is useful to set it for static files which should be cached
aggressively like images, stylesheets or similar.

Options =======

expire.url
assigns a expiration to all files below the specified path. The
specification of the time is made up of: ::

<access|modification> <number> <years|months|days|hours|minutes|seconds>

where access means time of user access and modification means time of file modification.

Follows the syntax used by mod_expire in Apache 1.3.x and later. (See: http://httpd.apache.org/docs/1.3/mod/mod_expires.html)

Example: ::

expire.url = ( "/images/" => "access 1 hours" )

Example to include all sub-directories: ::

$HTTP["url"] =~ "^/images/" {
         expire.url = ( "" => "access 1 hours" )
    }

Troubleshoot ============

It is known that mod_expire may not work due to an incorrect order of loading of modules. One instance is that mod_expire is loaded after mod_fastcgi. The solution is simple, it is to move mod_expire within the modules array in front of mod_fastcgi. Note: The order of the modules is loaded from top to bottom.

Symptoms of the above scenario is the server starts up fine but fails to serve content.

}}}