httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@ai.mit.edu (Robert S. Thau)
Subject Re: No HOST header solutions?
Date Wed, 29 May 1996 20:54:26 GMT
  Anybody have a better solution?

Pre-draft 04a of the HTTP/1.1 spec suggests that you "MAY attempt to
use heuristics (e.g. examination of the URI path for something unique
to a particular host) in order to determine what exact resource is
being requested".

I guess we could implement this by trying to translate the request
with each virtual host, and picking the first one that translates into
an existing file or directory which *doesn't* leave the entire
request-URI as PATH_INFO.  This would, of course, require some
uglification of the server core --- it really can't be done as a
module, for all the same reasons that Host: header support itself
can't be done that way.  (It also leaves the question of what to do
with a plain request for http://virtualhost.com/ --- but in that case,
giving the client a menu is the best you can possibly do anyway).

It's a ghod-awful kludge, of course, but I can't think of anything
better at the moment.  (I have thought of a couple of *different* ideas,
but as far as I can tell, they're all a hell of a lot worse, in terms
of their effects on both the users and the net).

rst


Mime
View raw message