I was hit by https://redmine.lighttpd.net/projects/lighttpd/repository/revisions/cd33554b74fd39ecd2e7c367070534da178d5147 -- I had blocked a few IPv6 addresses from our site, and that config prevented restarting lighttpd. Modifying the config to have the IPv6 address in square brackets made lighttpd start properly, but the IPv6 addresses were no longer blocked. The linked patch should fix this regression. If someone uses $HTTP["remoteip"] for some real ACL purpose with IPv6 addresses, this bug is a bit nasty.
This update has been submitted for testing by limb.
This update has been pushed to testing.
I was hit by https://redmine.lighttpd.net/projects/lighttpd/repository/revisions/cd33554b74fd39ecd2e7c367070534da178d5147 -- I had blocked a few IPv6 addresses from our site, and that config prevented restarting lighttpd. Modifying the config to have the IPv6 address in square brackets made lighttpd start properly, but the IPv6 addresses were no longer blocked. The linked patch should fix this regression. If someone uses $HTTP["remoteip"] for some real ACL purpose with IPv6 addresses, this bug is a bit nasty.
Thank you, I'll get out a patched version.
This update has been obsoleted by lighttpd-1.4.40-2.el7.