The following reply was made to PR general/1197; it has been noted by GNATS.
From: Dean Gaudet <[EMAIL PROTECTED]> To: "Erik T. Brandsberg" <[EMAIL PROTECTED]> Subject: Re: general/1197: VirtualHost directives don't respond to all the IP's that a name might resolve to. Date: Sat, 4 Oct 1997 18:46:55 -0700 (PDT) On Sat, 4 Oct 1997, Erik T. Brandsberg wrote: > > Yup this is the problem. Call it non-intuitive (I'll agree with you), but > > the global ServerName dictates what ip addresses will be considered for > > HTTP/1.1 Host: based vhosting... which is almost never what anyone wants. > > The standard workaround is this: > > This doesn't quite make sense--the global ServerName directive was > pointing to BOTH IP's that I wanted, not just one. > The virtual hosts that > I had a problem with were on the same IP's (I used the same dns .hosts > file for vhost and every other domain to insure consistancy). It seems > like it chose to respond to HTTP 1.1 requests only on one of the two IP's > that were specified in the global servername directive, which I would say > is wrong, even given the limitations described. Oh you and I are talking about completely different things. You're trying to give name-based (i.e. HTTP/1.1) vhosts multiple IP addresses right? Well, that just isn't possible. A vhost is either name-based (which works on exactly those ip addresses matching the global ServerName, i.e. 209.12.240.131) or ip-based, it can't be both. Your global ServerName has exactly one ip address, so all your name based hosts must also have exactly one ip address. Have you read htdocs/manual/vhosts-in-depth.html ? Dean
