www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <dgau...@arctic.org>
Subject Re: os-linux/788: (1) mod_dld doensn't compile. (2) Virtual hosting is broken in certain circumstances
Date Sat, 19 Jul 1997 23:40:02 GMT
The following reply was made to PR os-linux/788; it has been noted by GNATS.

From: Dean Gaudet <dgaudet@arctic.org>
To: Niels <niels@holding.pi.net>
Subject: Re: os-linux/788: (1) mod_dld doensn't compile. (2) Virtual hosting is broken in
certain circumstances
Date: Sat, 19 Jul 1997 16:39:39 -0700 (PDT)

 You can't get the old behaviour back.  It was hopelessly broken pre-1.1 by
 the addition of the name-based virtual hosts.  There's a bunch of
 documentation that describes workarounds.  I know it's hopelessly broken
 because I've spent far too much time trying to make it work, and plan on
 rewriting vhost support entirely. 
 If you've got a <VirtualHost> that matches the ip of the machine that your
 server is on then it will have this undesirable new behaviour.  To work
 around it you can use:
 <VirtualHost _default_:*>
 ServerName whatever
 in place of your previous <VirtualHost>.
 Or you could place "ServerName localhost" outside of all <VirtualHost>
 sections, which fools apache into thinking that is the address
 that it's supposed to do name-based vhost matching. 
 On Sun, 20 Jul 1997, Niels wrote:
 > On Sat, 19 Jul 1997 dgaudet@hyperreal.org wrote:
 > > There's nothing the server can do if the client passes it a
 > > hostname of just "web" rather than a fully-qualified hostname.
 > > It can't guess the information ... if you want to support unqualified
 > > names then you could use ServerAlias.
 > If the client doesn't pass any Host: header it gets the wrong index.html -
 > that's the problem.
 > (telnet to port 80, GET / HTTP/1.0 Enter twice)
 > I don't want support for unqualified hostnames; I would like the old
 > Apache behaviour back where it would look at the interface address, as I
 > thought it was meant to be.
 > Again, it may have been a broken setup at my end but I do not believe so..
 > server-status shows that Apache attaches the real virtual_host to it but
 > fails to get the real index.html somehow.

View raw message