W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1999

RE: Host header issue

From: Josh Cohen (Exchange) <joshco@Exchange.Microsoft.com>
Date: Tue, 7 Sep 1999 15:42:53 -0700
Message-ID: <BFF90FB6CF66D111BF4F0000F840DB850BCBBA81@LASSIE>
To: "'John Stracke'" <francis@ecal.com>, http-wg@hplb.hpl.hp.com
> -----Original Message-----
> From: John Stracke [mailto:francis@ecal.com]
> Sent: Tuesday, September 07, 1999 11:30 AM
> To: http-wg@hplb.hpl.hp.com
> Subject: Re: Host header issue
> 
> This isn't necessarily pathological.  My home network 
> includes a proxy; it runs
> Apache with mod_proxy, and that same Apache also serves up 
> its own content.  It
> has two CNAMEs, "proxy" and "www"; my browser is configured 
> to use "proxy" as
> its proxy.  So, if I send my browser to http://www/foo.html, 
> then Apache gets a
> request whose request-URI is http://www/foo.html.  It knows 
> that www is itself,
> so it delivers its own content.
>
In which case you really dont need the Host: header...
hence my point..

> --
> /============================================================\
> |John Stracke    |http://www.ecal.com|My opinions are my own.|
> |Chief Scientist |===========================================|
> |eCal Corp.      |"Who died and made you king?" "My father." |
> |francis@ecal.com|                                           |
> \============================================================/
> 
> 
Received on Tuesday, 7 September 1999 23:44:27 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:33:33 EDT