Bug #1234
closedConfiguration Error with mod_dirlisting
Description
index-file.names = ( "index.xhtml", "index.html", "/cgi-bin/dir-generator" ) server.dir-listing = "enable" scgi.server = ( "/cgi-bin" => ( ( "socket" => "/path/.scgi-sock" "check-local" => "disable" [removed for brevity] ) ) )
It seems that whenever lighttpd gets a request for a directory without
an index file (index.xhtml or index.html), then it should call the scgi
server to get the directory listing. It does not.
I suppose I could accomplish this with rewrite-rules, but i'm concerned
that this may be an unintended bug.
Updated by gstrauss almost 8 years ago
- Description updated (diff)
- Status changed from New to Wontfix
- Assignee deleted (
jan) - Target version deleted (
1.5.0)
mod_indexfile does not have a way to know that the target URL path will be handled by a module that uses virtual paths (e.g. mod_scgi configured with "check-local" => "disable")
A workaround is to simply touch the target, in the example above ".../cgi-bin/dir-generator" so that mod_indexfile existence check succeeds.
If an full URL-path is provided as a target for index-file.names, should lighttpd unconditionally follow the path rather than checking that it exists? For a single vhost config, that seems reasonable to me. However, what if there are multiple vhosts and have a shared config for index-file.names, where one vhost might provide the cgi-bin target, but another might not and for that second vhost I want it to fall through to use mod_dirlisting?
Marking this WontFix since changing the behavior of mod_indexfile might break some existing configs, and in most cases it would be possible to use the workaround to make sure that the target dir-generator exists. I'll add a note to the wiki doc, too.
Also available in: Atom