- From: Zachary Amsden <zamsden@cthulhu.engr.sgi.com>
- Date: Mon, 17 Apr 2000 18:05:47 -0700
- To: "Larry Masinter" <LM@att.com>
- Cc: http-wg@hplb.hpl.hp.com
This was the solution recommended at IETF-47. Of course, you also have the problem with userland utilities that accept host:port designations as well. > Following RFC 2732 & integrating with HTTP 1.1: > > > > The problem I have is in the Host field in the HTTP 1.1 header > > > > > > It says: > > > > > > Host hostname > > > > > > or > > > > > > Host hostname:port > > > > > > If hostname is an IPv6 literal address, then there is an ambiguity due > > > the colon > > > > > > example: > > > > > > Host 3ffe::1:8080 > > > > > > Does this mean hostname is 3ffe::1 and port 8080 or hostname > > > 3ffe::1:8080 and default port 80 ? > > > > > > The only way to remove the ambiguity is to make the use of [ ] around > > > the IPv6 > > > literal address madatory. Such as: > > > > > > Host [3ffe::1]:8080 > > > > > > or > > > > > > Host [3ffe::1:8080] > > > > > > > > > We ran into this problem at Connectathon 2000. > -- Zachary Amsden zamsden@engr.sgi.com 3-6919 31-2-510 Core Protocols
Received on Tuesday, 18 April 2000 01:56:30 UTC