httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <>
Subject Re: virtual hosts in 1.3
Date Sat, 23 Aug 1997 02:36:10 GMT
There was one other suggestion I had that would be about 10 lines of code
for 1.3.  That is a NameVHostAddr directive which defines the addresses in
the single global name-vhost pool (rather than using the main server
address).  This doesn't give the multi-pool support that Alexei (and I) 
would like, but it does eliminate one of the hidden semantics of the
configuration ...  By default no NameVHostAddr means no name-vhost

Combine this with a config diagnostic that complains about overlapping ip
addresses.  The diagnostic should say "perhaps you need to add
NameVHostAddr, see the documentation". 


On Fri, 22 Aug 1997, Marc Slemko wrote:

> You konw, some configs would be helped a lot by having a "VirtualHostType
> xx" directive that can go in a VirtualHost.  If none is there, we don't
> care and try to figure it out.  If one is there, then it either warns or
> croaks if it doesn't agree with Apache.
> Not sure it is worthwhile though.
> On Fri, 22 Aug 1997, Dean Gaudet wrote:
> > Here is what 1.3 should be doing according to what I intended.
> > 
> > Multiple-port support:  You should be able to take a set of multiport config
> > files and split them into multiple single port config files just by changing
> > the Listen statements, and nothing else.  From outside the box you shouldn't
> > be able to tell if there's a single multi-port server, or multiple single-port
> > servers.  I think that succinctly describes the intention with ports, the
> > rest of this message assumes we're dealing with a single port server.
> > 
> > The main server is, well you know what it is.
> > 
> > A name-based vhost is a <VirtualHost> section which had at least one ip
> > address overlap the main server.  The other non-overlapping addresses are
> > treated as if they're separate ip-vhosts with the exact same config.  A
> > name-based vhost is matched only if the request is on a main server address,
> > and ServerName, ServerAlias, or ServerPath match the name-vhost.  Matching
> > occurs in the reverse order the hosts appear in the configuration files.
> > Both ServerName and ServerAliases are considered at the same time, if
> > there's no Host: header then ServerPath is considered.  For all intents
> > and purposes any address strings appearing in the <VirtualHost> line
> > are considered ServerAliases.
> > 
> > An ip-based vhost is a <VirtualHost> section which does not overlap the
> > main server's addresses.  An ip-based vhost is matched only by ip address,
> > nothing else is considered.  A corollary is that no two ip-vhosts can
> > (successfully) share the same ip address, the server does not presently
> > diagnose this.
> > 
> > A _default_ vhost matches anything which is not otherwise matched.  There
> > can only be one _default_ vhost, but Apache produces no warnings if there
> > are multiple.  A * address is the same as a
> > _default_ address.
> > 
> > I think that completely describes the vhost code in 1.3a2.  I challenge
> > anyone to come up with anything more concise to describe the behaviour
> > of 1.1 or 1.2.  Have fun with it.  Remember that hashing ip vhosts will
> > help performance on many sites, so think twice about removing it in
> > favour of restoring broken old code.
> > 
> > Dean
> > 

View raw message