Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 5585 invoked by uid 6000); 25 Oct 1997 23:00:35 -0000 Received: (qmail 5573 invoked from network); 25 Oct 1997 23:00:33 -0000 Received: from valis.worldgate.com (marcs@198.161.84.2) by taz.hyperreal.org with SMTP; 25 Oct 1997 23:00:33 -0000 Received: from localhost (marcs@localhost) by valis.worldgate.com (8.8.7/8.8.7) with SMTP id RAA15046 for ; Sat, 25 Oct 1997 17:00:27 -0600 (MDT) Date: Sat, 25 Oct 1997 17:00:27 -0600 (MDT) From: Marc Slemko To: new-httpd@apache.org Subject: RE: NameVirtualHost In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org But, as I understand it, simply adding a single NameVirtualHost directive is _not_ sufficient for current setups where people have one IP address for their main server and all name virtual hosts. On Sat, 25 Oct 1997, Lars Eilebrecht wrote: > According to Dean Gaudet: > > > In the absence of NameVirtualHost, Apache will do what everyone seems > > to want it to do (but me). That is it will guess that any overlapping > > IP addresses are supposed to be name virtual hosts. > > > > If any NameVirtualHost directives are present, then they must list > > all addresses (any unlisted addresses result in an error). > > Hmmm... how about making NameVirtualHost a required directive. Let Apache > issue an error message on startup if there is a VirtualHost without a > NameVirtualHost directive (or "NameVirtualHost None" is used). > > This will prevent people from using their old VirtualHost configs when > upgrading to Apache 1.3. > > > ciao... > -- > Lars Eilebrecht - Beat me, whip me, make me use Windows! > sfx@unix-ag.org > http://www.si.unix-ag.org/~sfx/ >