Lighttpd Client Side Optimization With mod_expire To Control / Set The Expire HTTP Headers

by on April 17, 2007 · 2 comments· LAST UPDATED December 23, 2013

in , ,

The last time I wrote about Lighttpd optimization tips here and here.

You must optimize server side as well as client side. Client side optimization includes CSS code, javascript and images as they would hardly change.

You can force client web browser not to download files for particular day / hour.

Lighttpd comes with mod_expire module. It 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, java scripts, pdf files or similar.

Step # 1: Make sure mod_expire is active

Open lighttpd config file /etc/lighttpd/lighttpd.conf, using a text editor such as vi:
# vi /etc/lighttpd/lighttpd.conf
You must load mod_expire before all other module to avoid ill side effects.

server.modules              = (
                               "mod_expire",
                               "mod_redirect",
                               "mod_alias",
                               "mod_rewrite",
                               "mod_access",
                               "mod_auth",
                               "mod_status",
                               "mod_fastcgi",
                               "mod_compress",
                               "mod_accesslog" )

Step # 2: Set expiration for /js/ and other dirs

Assigns a expiration to all files below the specified path:

## js - java script, css, figs directory in days ###
  expire.url = (
                  "/js/"     => "access 1 days",
                  "/css/"    => "access 3 days",
                  "/figs/" => "access 7 days"
               )

You can also add conditional tags as follows:

$HTTP["url"] =~ "^/assets/figs/" {
     expire.url = ( "" => "access 12 hours" )
}

Save and close the file. Restart the lighttpd server using the following command:
# /etc/init.d/lighttpd restart

Step #3: Test your settings

Use the curl command as follows to test http headers:
$ curl -I your-url-here
$ curl -I http://s0.cyberciti.org/images/misc/warning-40px.png

TwitterFacebookGoogle+PDF versionFound an error/typo on this page? Help us!

{ 2 comments… read them below or add one }

1 Guy Patterson January 6, 2010 at 11:22 pm

What are some methods to test whether or not mod_expire is working correctly?

Reply

2 Jerimaih December 23, 2013 at 6:19 pm
curl -I http://example.com/test.html

Check for the Cache-Control and Expires.

Reply

Leave a Comment

Previous post:

Next post: