While this seems to make sense, there are always problems with directories
that exist in both (such as /cgi-bin or /image) that complicate simple
solutions :(
Brian
-------- REPLY, Original message follows --------
Date: Wednesday, 06-Nov-96 10:29 PM
From: Klaus Johannes Rusch \ Internet: (e8726057@student.tuwien.ac.at
) To: robots@webcrawler.com \ Internet: (robots@webcrawler.com)
Subject: Re: Domains and HTTP_HOST
In <199611061329.GAA27547@smtp.radzone.org>, Brian Clark <bclark@radzone.
org> writes:
> You see this effect through
> the search engine databanks ... most typically, they do encounter the
> correct pages at some point during their crawl, turning a URL like:
>
> http://www.mydomain.com/
>
> to something like:
>
> http://www.mydomain.com/mydomain/
>
> Which isn't always a valid link for every browser (since a browser that
the
> HTTP_HOST variable is now likely to get a 404.)
Wouldn't it be reasonable for the server to redirect requests for http://www
.mydomain.com/mydomain/* to http://www.mydomain.com/* if the browser sends a
Host: header?
Klaus Johannes Rusch
-- e8726057@student.tuwien.ac.at, KlausRusch@atmedia.net http://www.atmedia. net/KlausRusch/
-------- REPLY, End of original message --------