Hi Bryan, one example would be a machine with two IP adresses, each of them has its own www.domain example: NameVirtualHost IP1:80 <VirtualHost IP1:80> .... </VirtualHost> NameVirtualHost IP2:80 <VirtualHost IP2:80> .... </VirtualHost> but there are even more situations where NameVirtualHost could used. Maybe with different websites on different ports, etc. bye Florian On Mon, December 17, 2007 04:44, Bryan Richardson wrote: > Hello all, > > I'm curious as to why one would ever need to use the NameVirtualHost > directive in site configuration files. I just can't seem to get my head > around why it's *sometimes* required. I say sometimes only because I've > seen instances where it isn't used at all. If all VirtualHost arguments > *must* match the IP address given with the NameVirtualHost directive, then > what's the point? > > I learn best by example... can anyone give me an example of when it is > needed? > > Thanks! -- BTR > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|