🚀 go-pugleaf

In <6f6jvo$a78$1@nntp6.u.washington.edu> gah@u.washington.edu (G. Herrmannsfeldt) writes:

>kitchin@intersurf.com writes:

>>For virtual domain web hosting my ISP just switched over to shared IP's
>>via HTTP_HOST (see below if you don't know what this is).   I complained,

No, they are via the Host: header.  HTTP_HOST is simply a CGI 
environment variable that is set.  

>>since I have only seen this used on very low cost providers, like icom.com and
>>webcom.com.  But my ISP claims the following:

>>> In accordance with InterNIC, ARIN, MCI and UUnet policies, we have
>>> eliminated the use of IP's for virtual web sites permanently.
>>>
>>> Browsers supporting only HTTPD v1.0 will indeed see the wrong web

Erm... someone doesn't know what they are talking about.  "HTTPD" would
be a HTTP daemon or something, eg. "NCSA httpd".  It is HTTP/1.0.
And most clients, with the exception of IE4, make HTTP/1.0 requests.
Most still send the Host: header, since just because it is defined
in HTTP/1.1 and not in 1.0 doesn't mean that 1.0 clients can't send it.

>>> site, for the reason you cited above.  Updated browsers have been
>>> available for far more than one year supporting HTTP_HOST.
>>>

>Most sites now use features that make them incompatible with HTTP v1.0,
>anyway, so it would seem to me that this is the right way to go.

Erm... don't think so.  If you have anything to support this wild
claim, please post it.

As I said earlier, the only common client that makes HTTP/1.1 requests
is IE4.