Lighttpd

As the anonymous commenter already said: tlds in your format are invalid, change your hostnames :)

While it's technically true that there are no TLDs starting with numbers today, it is somewhat annoying. A fair number of companies use .companyname as a TLD for their intranets; and this makes lighttpd a poor fit for those that start with numbers.

If I were to submit a patch supporting TLDs that start with any alpha-numeric number for intranets like these, might this feature be reconsidered?

Conversely, lighttpd does support TLDs that end in numbers - though no such TLDs exist either. Should I submit a patch that rejects those?

If lighty behaves like this, the next one screams lighty is not compliant. So where should this lead too? Just because sth. might be possible does not proof its the right thing to do. The "fix" is there -> use proper hostnames.

I think we could discuss whether we should check the hostname at all for such characteristics - perhaps we could simplify the checks.

• Which characters should be allowed? The rfc even allows escaped characters (rfc 2396) - should we unescape it before checking?
  I think the basic regex looks like ([a-zA-Z0-9_~.!$&'()*+,;=\-]|%[0-9a-fA-Z][0-9a-fA-Z])+
  I guess [a-zA-Z0-9_.\-]+ should be enough, but perhaps there are good arguments for other characters.
• Which substrings should be forbidden? ".." is a pretty obvious example imho, but are there more?

Applied in changeset b47494d4cda6dc1a152f9033e4617897842c2f50.