Project

General

Profile

Bug #2281

closed

400 Bad Request when using Numeric TLDs

Added by khemael almost 10 years ago. Updated over 4 years ago.

Status:
Duplicate
Priority:
Normal
Category:
-
Target version:
ASK QUESTIONS IN Forums:

Description

When using full numeric TLDs, lighttpd (any version) always respond with a bad request.

Reproductible : Anytime
Version : Any


Related issues

Related to Bug #2258: Bad RequestInvalid2010-09-15Actions
Is duplicate of Bug #2143: Numeric tld'sFixed2009-12-31Actions
#1

Updated by icy almost 10 years ago

  • Status changed from New to Duplicate
#2

Updated by nitrox almost 10 years ago

RFC2616

14.23 Host
   Host = "Host" ":" host [ ":" port ] ;

3.2.1 General Syntax
   RFC 2396 [42] (which replaces RFCs
   1738 [4] and RFC 1808 [11]). This specification adopts the
   definitions of "URI-reference", "absoluteURI", "relativeURI", "port",
   "host","abs_path", "rel_path", and "authority" from that
   specification.

RFC2396

3.2.2. Server-based Naming Authority

      host          = hostname | IPv4address
      hostname      = *( domainlabel "." ) toplabel [ "." ]
      domainlabel   = alphanum | alphanum *( alphanum | "-" ) alphanum
      toplabel      = alpha | alpha *( alphanum | "-" ) alphanum

So toplabel is alpha.
ICANNĀ“s mentioned "ideas" from #2143 are just a "Draft".

#3

Updated by khemael almost 10 years ago

Hi,

First : Our company uses Numeric only TLD's internal. Lighttpd is the only soft to fail with that.
Also, ICANN does not say TLD 'MUST' be alpha, but "MAY NOT" be full numerical.

also : http://www.ietf.org/mail-archive/web/dnsop/current/msg08941.html

ietf is using pseudo-TLD's to test numericals tld.

#4

Updated by gstrauss over 4 years ago

  • Target version set to 1.4.40

Also available in: Atom