Maybe I missed the core of your question because it was so early in the morning for me :-) To extend my example: NameVirtualHost IP1:80 <VirtualHost IP1:80> ServerName domain1.com DocumentRoot /var/www/domain1/ .... </VirtualHost> <VirtualHost IP1:80> ServerName domain2.com DocumentRoot /var/www/domain2/ .... </VirtualHost> NameVirtualHost IP2:80 <VirtualHost IP2:80> ServerName domain3.com DocumentRoot /var/www/domain3/ .... </VirtualHost> Now the apache decides which website to serve only via the domain name that is given with the request. Literally speaking, if you read an NameVirtualHost statement like "I want a virtual host on that IP and on that port to exist", then a VirtualHost statement would mean "here is a configuration for ONE domain running under that virtualhost". That's why they have to have the same name and why a virtualhost needs a ServerName. I hope that was a little bit more precise. bye Florian On Mon, December 17, 2007 06:17, Bryan Richardson wrote: > Hi Florian, > > Thanks for the response. I guess my question is why have the > NameVirtualHost directive since the *same* IP address is required to be > specified as an attribute in the VirtualHost block? > > Thanks! -- BTR > > On Dec 16, 2007 10:09 PM, <florian.schmidt@xxxxxxxxxx> wrote: > >> 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 >> >> > --------------------------------------------------------------------- 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
|