W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > January to April 1996

Re: Host: header and port number

From: David W. Morris <dwm@shell.portal.com>
Date: Wed, 24 Jan 1996 13:22:58 -0800 (PST)
To: Shel Kaphan <sjk@amazon.com>
Cc: Rob McCool <robm@netscape.com>, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <Pine.SUN.3.90.960123095445.195D-100000@jobe.shell.portal.com>

On Mon, 22 Jan 1996, Shel Kaphan wrote:

> It's conceivable that a gateway would want to translate requests it
> receives on various ports to other ports on the other side (the
> inside) of a firewall.  If the original port were part of this header
> Maybe that is outlandish -- I'm not so sure.  It's not that much of a
> burning issue for me, though it feels more sensible to me to leave the
> port info in if it's there, rather than exclude it.

The point of the Host: header is to provide the information lost between
the original URL and the non-proxy server request. I understand that
if port proxying isn't implemented, the request port will be known to
the server at some layer but it seems much cleaner to me to include
port with the host: header. No reason it couldn't be optional UNLESS
port mapping was occuring in which case it would be required and
in particular required for the proxy doing the port mapping to add the
port. We are now introducing the host: header in part because the
original protocol deleted information. Why repeat that mistake for
the sake of saving a few bytes of data?

Dave Morris
Received on Wednesday, 24 January 1996 13:26:56 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:16 UTC