No it’s not, it’s a regression, the same config file worked fine before.
Reduced reproducing config file:
alias.url += (
"/dump1090-fa/data/" => "/run/dump1090-fa/",
"/dump1090-fa/" => "/usr/share/dump1090-fa/html/"
)
# Listen on port 8080 and serve the map there, too.
$SERVER["socket"] == ":8080" {
alias.url += (
"/data/" => "/run/dump1090-fa/",
"/" => "/usr/share/dump1090-fa/html/"
)
}
lighttpd[3046773]: 2020-11-11 22:52:54: (mod_alias.c.70) url.alias: `/dump1090-fa/' will never match as `/' matched first
lighttpd[3046773]: 2020-11-11 22:52:54: (server.c.1484) Configuration of plugins failed. Going down.
The issue seems to be that somehow the $SERVER["socket"] == ":8080" {
block gets processed first?
Just tried to make this a bug report but your bugtracker didn’t allow me to create an account as no email was sent for activation.
As a feature request / bug report:
server.modules += ( "mod_setenv" )
server.modules += ( "mod_setenv" )
This leads to mod_setenv not working correctly.
It would be much better if a module being loaded twice would just be ignored, that way if 2 programs which enable lighttpd configurations both need that module they can safely activate it without causing it to not work properly.