Server modulesDetails » History » Revision 5
Revision 4 (Anonymous, 2007-07-03 08:36) → Revision 5/9 (stbuehler, 2009-02-17 12:29)
h1. <pre> #!rst server.modules option ===================== h2. Description h3. server.modules modules to load The the order of the modules is important: important. The modules are executed in the order as they are specified. Loading mod_auth AFTER mod_fastcgi might disable authentication for fastcgi backends (if check-local is disabled). As auth should be done first, move it before all executing modules (like proxy, fastcgi, scgi and cgi). rewrites, redirects and access should be first, followed by auth and the docroot plugins. Afterwards the external handlers like fastcgi, cgi, scgi and proxy and at the bottom the post-processing plugins like mod_accesslog. Example: <pre> :: server.modules = ( "mod_rewrite", "mod_redirect", "mod_alias", "mod_access", "mod_auth", "mod_status", "mod_simple_vhost", "mod_evhost", "mod_userdir", "mod_secdownload", "mod_fastcgi", "mod_proxy", "mod_cgi", "mod_ssi", "mod_compress", "mod_usertrack", "mod_expire", "mod_rrdtool", "mod_accesslog" ) </pre> These Starting with lighttpd 1.4.0 three default modules are loaded automatically, don't load them yourself: automatically: * mod_indexfile * mod_dirlisting * mod_staticfile Do not add a module twice, only add modules in the global context. </pre>