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])
