Lighttpd

(repeating the issue, with proper brackets for accuracy)

I think `$SERVER["socket"] == ":1234"` without explicitly specifying the host to bind to, should bind to IPv6 '::' instead of 0.0.0.0 when `server.use-ipv6 = "enable"` is specified.

I'm well aware that one can use "[::]:1234", but the behavior described above makes much more sense to me.

-- intgr

This should already work if you specify server.use-ipv6 = "enable" within the $SERVER["socket"] condition.

The actual issue is not inheriting the setting from the global scope. The following patch fixes that, but might surprise people with existing configs who have server.use-ipv6 = "enable" in the global scope, and then do not set server.use-ipv6 = "disable" in $SERVER["socket"] conditionals where IPv4 is desired instead of IPv6-mapped IPv4.

diff --git a/src/configfile.c b/src/configfile.c
index 690713c..094ad83 100644
--- a/src/configfile.c
+++ b/src/configfile.c
@@ -207,8 +207,8 @@ static int config_insert(server *srv) {
                s->ssl_empty_fragments = 0;
                s->ssl_use_sslv2 = 0;
                s->ssl_use_sslv3 = 0;
-               s->use_ipv6      = 0;
-               s->set_v6only    = 1;
+               s->use_ipv6      = (0 != i) srv->config_storage[0]->use_ipv6 : 0;
+               s->set_v6only    = (0 != i) srv->config_storage[0]->set_v6only : 1;
                s->defer_accept  = 0;
 #ifdef HAVE_LSTAT
                s->follow_symlink = 1;

While I do not think that this change would affect a large number of users, and I think that those who have such specific configs with mixed IPv6 and IPv4 addresses will have the knowledge to recognize if this change affects them, backward compatibility with existing configs might mean that this patch will not be accepted into a release.

Applied in changeset 2cdc017fb9d5296cfd7cd2a103fb948caa791a2b.