The following reply was made to PR config/4455; it has been noted by GNATS.
From: Rodent of Unusual Size <[EMAIL PROTECTED]>
To: Apache bug database <[EMAIL PROTECTED]>
Cc: Subject: Re: config/4455: apache provides no way to do a
wildcard/globalNameVirtualHost
Date: Wed, 26 May 1999 13:08:31 -0400
This is a multi-part message in MIME format.
--------------D3E17CFAA0B29E7CBFD78B87
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Not sent to the database..
--------------D3E17CFAA0B29E7CBFD78B87
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Return-Path: <[EMAIL PROTECTED]>
Received: from hyperreal.org (taz.hyperreal.org [209.133.83.16])
by Mail.MeepZor.Com (8.8.7/8.8.7) with SMTP id MAA13535
for <[EMAIL PROTECTED]>; Wed, 26 May 1999 12:54:41 -0400
Received: (qmail 22322 invoked by uid 161); 26 May 1999 16:53:37 -0000
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 22312 invoked by uid 2016); 26 May 1999 16:53:37 -0000
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 22306 invoked from network); 26 May 1999 16:53:36 -0000
Received: from www.duh.org (HELO duhnet.net) ([EMAIL PROTECTED])
by taz.hyperreal.org with SMTP; 26 May 1999 16:53:36 -0000
Received: from localhost (IDENT:[EMAIL PROTECTED] [127.0.0.1])
by duhnet.net (8.9.3/8.9.3/3.1.0) with ESMTP id MAA27261Wed, 26 May
1999 12:59:04 -0400 (EDT)
Date: Wed, 26 May 1999 12:59:04 -0400 (EDT)
From: Todd Vierling <[EMAIL PROTECTED]>
X-Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: apache-bugdb@apache.org
Subject: Re: config/4455: apache provides no way to do a wildcard/global
NameVirtualHost
In-Reply-To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
On 26 May 1999 [EMAIL PROTECTED] wrote:
: Please check out the use of the <VirtualHost _default_>
: syntax and see if that addresses your need.
No. There's two things I'm wanting here, to address two different problems:
- A replicable wildcard for VirtualHost.
This would allow a named virtual host to appear on *any* IP address, if
desired using the HTTP/1.1 (and extended HTTP/1.0) Host: header.
(Currently, an IP must be assigned to each VirtualHost, though you can
duplicate the same ServerName in multiple VirtualHosts.)
The <VirtualHost _default_> directive may be used exactly once, and does
not do "NameVirtualHost matching" on the ServerName (since you may only
have one of them).
- A wildcard for NameVirtualHost, or "default" behavior of allowing
NameVirtualHosts on all addresses.
Name-based virtual hosts are only scanned on addresses for which the
NameVirtualHost directive is given. Frankly, I believe they should be
allowed on all addresses by default (whenever a Host: header is supplied).
However, a wildcard for NameVirtualHost would suffice.
=====
The two setups I administer which require something like the above:
- One server with a dynamically changing IP address to the outside world
which has multiple named virtual hosts. (Providing an IP address to
either VirtualHost or NameVirtualHost would be meaningless.)
- A cluster of servers, referenced by multiple DNS address records for each
domain served. These machines do failover -- if one crashes, another
picks up the orphaned IP address as an alias, just to keep that address
from becoming a "black hole" in the DNS address list. (The cluster
machines need a way to allow dynamically added IP addresses to serve the
same name based virtual hosts without modifying httpd.conf.)
The <VirtualHost _default_> directive provides settings to be a "catch-all"
if a virtual host is not matched, which doesn't help either situation above.
In these networks, I do in fact have a <VirtualHost _default_> directive
that points to a page reading "Update your browser ... to one supporting
HTTP/1.1 named virtual hosts ...."
--
-- Todd Vierling (Personal [EMAIL PROTECTED]; Bus. [EMAIL PROTECTED])
--------------D3E17CFAA0B29E7CBFD78B87--
