Feature #506
closedManual Documentation is misleading
Description
mod_expires must be defined before mod_ssi if you want mod_ssi to properly
set expire headers. This should be mentioned in the boring manual.
Currently the documentation reads:
the order of the modules is somewhat important as the modules are handled in the way they are specified. mod_rewrite should always be the first module, mod_accesslog always the last. e.g.: server.modules = ( "mod_rewrite", "mod_redirect", "mod_alias", "mod_access", "mod_auth", "mod_status", "mod_fastcgi", "mod_proxy", "mod_simple_vhost", "mod_evhost", "mod_userdir", "mod_cgi", "mod_compress", "mod_ssi", "mod_usertrack", "mod_expire", "mod_secdownload", "mod_rrdtool", "mod_accesslog" )
This is somewhat misleading in that mod_ssi is required after mod_expires, but actually needs to be defined before mod_expires. Either reordering this list or adding a note would elevate confusion.
-- buecking
Updated by stbuehler over 16 years ago
- Status changed from New to Fixed
- Resolution set to wontfix
wiki... do it yourself.
Updated by gstrauss about 1 year ago
- Description updated (diff)
- Status changed from Wontfix to Fixed
- ASK QUESTIONS IN Forums set to No
Since lighttpd 1.4.43, mod_expire is handled in the "response start" hook, and so its order in server.modules
compared to "mod_ssi" does not matter.
Separately, since lighttpd 1.4.40, ssi.conditional-requests = "enable"
will tell mod_ssi to generate an ETag and Last-Modified for an SSI page. (commit 6982b193)
Also available in: Atom