Project

General

Profile

Actions

Feature #551

closed

lighttpd doesn't allow underscores in host names

Added by Anonymous over 15 years ago. Updated over 5 years ago.

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

Description

If I try to visit mister_fab.infogami.com, lighttpd returns a 400 Bad Request error. How do I get it to stop?

-- me

Actions #1

Updated by Anonymous over 15 years ago

Underscores are NOT valid in hostnames for A-Records (and MX btw.) and should not be accepted by the infogami registration. Although there actually is an rfc wich allows underscores (RFC1033), it is mostly regarded as a mistake and has Status "Unknown". Rfc1035 however is labeled "Standard" and does not allow them.

Since wildcard dns records are so popular these days, Jan might choose to allow more characters (his personal choice) but you're far better off avoiding underscores in hostnames.

-- bkw

Actions #2

Updated by Anonymous over 15 years ago

RFC 1035 makes it clear that these are conventions (the title of the section is "Conventions"). And while I would tend to agree that infogami should enforce these recommendations, lighttpd certainly shouldn't, because it prevents applications that use domain names in a non-standard way from working

http://foo_bar.fred.theinfo.org/ (you can change the foo_bar bit) is a sort of silly example but I see no good reason why it shouldn't work. (And it does with Apache.)

-- aaronsw

Actions #3

Updated by Anonymous over 15 years ago

OK, it's a convention, but then again, so is most of tcp/ip (or communication in general).

But Jon tought us to be liberal what we accept, so yes, I do agree with you.

btw http://foo_bar.fred.theinfo.org/ was an interesting read, had its lengths near the end though ;-)

-- bkw

Actions #4

Updated by moo over 15 years ago

relative enhancement: #602

to break standard or not to, it's a problem

Actions #5

Updated by gstrauss over 5 years ago

  • Description updated (diff)
  • Status changed from New to Patch Pending
  • Assignee deleted (jan)
  • Target version set to 1.4.40
Actions #6

Updated by gstrauss over 5 years ago

  • Status changed from Patch Pending to Fixed
  • % Done changed from 0 to 100
Actions

Also available in: Atom