The following reply was made to PR general/1247; it has been noted by GNATS.
From: Dean Gaudet <[EMAIL PROTECTED]>
To: JDC <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: general/1247: Main server configuration & VirtualHosts are botched
Date: Tue, 21 Oct 1997 17:31:42 -0700 (PDT)
On 20 Oct 1997, JDC wrote:
> All of our <VirtualHost> entries look like this now; the
> result is that all <VirtualHost>'s work, but our main
> server "www.parodius.com" (also "parodius.com") goes to
> the <VirtualHost> defined above. This <VirtualHost> is
> the first in the list.
This is expected (undocumented) behaviour. When you declare a
NameVirtualHost then only <VirtualHost>s are expected on that address. To
fix it put a <VirtualHost> section first which is a copy of your main
server config.
> > Erm, there's only *one* server defined outside the
> > <VirtualHost> containers - the default or "main" server.
> > Try listing the main server's details inside its own <VirtualHost>
> > container, and changing the global ServerName to "localhost". That
> > way, *all* of your working servers should be defined by
> > <VirtualHost> blocks, including the main one.
>
> This seems more like an "excuse" to get around the bug; I don't
> mean to seem like an asshole, but I am not willing to try this.
> I'd prefer the bug be fixed rather than have some "configuration
> hack". Sorry if that's rude :-(.
Sorry, this is how it is. It's not an excuse, it's not a bug. It's just
how the configuration language now works. In future versions we will be
removing the "main" server entirely.
FWIW, if your name-vhosts are on 10.1.1.1, you can do this (before any
other vhosts):
NameVirtualHost 10.1.1.1
<VirtualHost 10.1.1.1 _default_>
ServerName www.parodius.com
yadda yadda
</VirtualHost>
and it will handle all the default requests on that name-vhost address, and
for any other address you might not specify.
Dean
