Bug #592

400 - Bad Request to Safari with literal IPv6 addresses

Added by Anonymous 989 days ago. Updated 55 days ago.

Status:Invalid Start:
Priority:Normal Due date:
Assigned to:- % Done:

0%

Category:core
Target version:-
Pending:

No

Resolution:

invalid

Patch available:


Description

Using Safari to access a literal IPv6 address (e.g. 2001:4830:151a:d610::2/">http://2001:4830:151a:d610::2/), Safari sends the Host field in the request header as 2001:4830:151a:d610::2, instead of 2001:4830:151a:d610::2, as Mozilla does, and which generates a correct response. As a result, lighttpd responds with a 400 - Bad Request error. I'm assuming that the problem arises from the ambiguity of whether the terminal : is followed by the last octet of the address or by a port number, and the bad request message is generated by the multiplicity of colons.

A reasonable thing to do is probably just to drop the error checking for this particular case (or at least in the case where the Host field could reasonably be parsed as an IPv6 address). It might conceivably, possibly, mess up virtual hosting in the extremely rare event that someone has a vhost set up that appears only when people access it from a literal IPv6 address.

-- nathanw

History

10/23/2007 03:12 PM - mario_zdravkovski@hotmail.com

Bravo

04/24/2008 08:44 PM - stbuehler

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

I think the standards are pretty clear, and safari violated them (don't know if it still does).

10/10/2008 06:53 PM - stbuehler

  • Status changed from Fixed to Invalid

Also available in: Atom PDF