Project

General

Profile

Actions
Copy link

Bug #1742

closed

Hostnames which resolve to an IPv6 address do not work in SSL socket specification

Added by rm over 16 years ago. Updated about 16 years ago.

Status:
Invalid
Priority:
Normal
Category:
core
Target version:
1.5.0
ASK QUESTIONS IN Forums:

Description

A hostname which resolves to an IPv6 address cannot currently be used to specify a socket for SSL.

E.g., a config file (10-ssl.conf) with

$SERVER\socket == "ipv6.example.net:443" {
ssl.engine = "enable" 

ssl.pemfile                 = "/etc/lighttpd/server.pem" 
}

...where example.net resolves to an IPv6 address only, upon restart of Lighttpd will produce an error:

Starting web server: lighttpd2008-08-03 03:15:32: (network.c.224) gethostbyname failed: 1 ipv6.example.net
failed!

I should note, that specifying an IPv6 address (in square brackets) instead of hostname, or a hostname which resolves to IPv4, does work OK there.

Actions
Copy link
 #1

Updated by rm over 16 years ago

That should read "...where ipv6.example.net resolves...".

Actions
Copy link
 #2

Updated by stbuehler over 16 years ago

  • Status changed from New to Fixed
  • Resolution set to invalid

Use {{{
$SERVERsocket == "ipv6.example.net:443"
}}}

But i don't recommend using names - if the name resolves to more than one address, only the first one is taken.

Actions
Copy link
 #3

Updated by stbuehler about 16 years ago

  • Status changed from Fixed to Invalid
Actions
Copy link

Also available in: Atom