[pkg-lighttpd] Bug#445459: lighttpd: mod_alias fails on localhost

[Steve Greenland]

Olaf van der Spek wrote:
> I tried to reproduce this on a fresh install of 1.4.18-1, but failed.
> A fresh install doesn't include aliases except those for 127.0.0.1, so
> I'd like to ask you what you changed from the default configuration.

Uh, I added aliases (and enabled mod_alias, of course). For example, I
added the following for nagios support:


alias.url += ("/nagios2/cgi-bin" => "/usr/lib/cgi-bin/nagios2",
              "/nagios2/" => "/usr/share/nagios2/htdocs/",
              )

If I access 'http://localhost/nagios2/', I get a 404. If I access
'http://speedy.moregruel.net/nagios2/', it works fine. Using IPs instead
of names makes no difference: using 127.0.0.1 fails, while 192.168.1.2
works.

Okay, while trying to make the minimal lighttpd.conf that exhibits the
problem, I found that aliases work if 10-mod_cgi.conf is not enabled.
(I'd guess that this makes this bug related to #345554.) In particular,
if I comment out the remoteip section in 10-cgi.conf like this:

#$HTTP["remoteip"] == "127.0.0.1" {
#   alias.url += ( "/cgi-bin/" => "/usr/lib/cgi-bin/" )
#   $HTTP["url"] =~ "^/cgi-bin/" {
#       cgi.assign = ( "" => "" )
#   }
#}

...aliases work again. I'm not sure why that section is there, the
/cgi-bin/ -> /usr/lib/cgi-bin/ mapping should work no matter what the
remote IP.

BTW, if you expect the bug submitter to respond to a question, you
really need to CC the submitter; the BTS doesn't automatically do this
(which I think is bad design...) I just happened to check the bug and
found your question.

Regards,
Steve



-- 
Steve Greenland
    The irony is that Bill Gates claims to be making a stable operating
    system and Linus Torvalds claims to be trying to take over the
    world.       -- seen on the net