https://redmine.lighttpd.net/https://redmine.lighttpd.net/favicon.ico?13667327412006-02-28T12:18:19Zlighty labsLighttpd - Feature #551: lighttpd doesn't allow underscores in host nameshttps://redmine.lighttpd.net/issues/551?journal_id=13852006-02-28T12:18:19ZAnonymous
<ul></ul><p>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 <em>not</em> allow them.</p>
<p>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.</p>
<p>-- bkw</p> Lighttpd - Feature #551: lighttpd doesn't allow underscores in host nameshttps://redmine.lighttpd.net/issues/551?journal_id=13862006-02-28T16:28:18ZAnonymous
<ul></ul><p>RFC 1035 makes it clear that these are <em>conventions</em> (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</p>
<p><a class="external" href="http://foo_bar.fred.theinfo.org/">http://foo_bar.fred.theinfo.org/</a> (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.)</p>
<p>-- aaronsw</p> Lighttpd - Feature #551: lighttpd doesn't allow underscores in host nameshttps://redmine.lighttpd.net/issues/551?journal_id=13872006-02-28T21:37:04ZAnonymous
<ul></ul><p>OK, it's a convention, but then again, so is most of tcp/ip (or communication in general).</p>
<p>But Jon tought us to be liberal what we accept, so yes, I do agree with you.</p>
<p>btw <a class="external" href="http://foo_bar.fred.theinfo.org/">http://foo_bar.fred.theinfo.org/</a> was an interesting read, had its lengths near the end though ;-)</p>
<p>-- bkw</p> Lighttpd - Feature #551: lighttpd doesn't allow underscores in host nameshttps://redmine.lighttpd.net/issues/551?journal_id=13882006-03-28T02:55:22Zmoo
<ul></ul><p>relative enhancement: <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Russian letters not alowed? (Fixed)" href="https://redmine.lighttpd.net/issues/602">#602</a></p>
<p>to break standard or not to, it's a problem</p> Lighttpd - Feature #551: lighttpd doesn't allow underscores in host nameshttps://redmine.lighttpd.net/issues/551?journal_id=96462016-05-18T10:57:51Zgstrauss
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/9646/diff?detail_id=7720">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>Patch Pending</i></li><li><strong>Assignee</strong> deleted (<del><i>jan</i></del>)</li><li><strong>Target version</strong> set to <i>1.4.40</i></li></ul> Lighttpd - Feature #551: lighttpd doesn't allow underscores in host nameshttps://redmine.lighttpd.net/issues/551?journal_id=96602016-05-23T05:40:04Zgstrauss
<ul><li><strong>Status</strong> changed from <i>Patch Pending</i> to <i>Fixed</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="[config] opts for http header parsing strictness (fixes #551, fixes #1086, fixes #1184, fixes #21..." href="https://redmine.lighttpd.net/projects/lighttpd/repository/14/revisions/b47494d4cda6dc1a152f9033e4617897842c2f50">b47494d4cda6dc1a152f9033e4617897842c2f50</a>.</p>