PROTECTED]
Envoyé : lundi 17 décembre 2007 04:44
À : users@httpd.apache.org
Objet : [EMAIL PROTECTED] NameVirtualHost Directive
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 aroun
On Dec 17, 2007 12:17 AM, Bryan Richardson <[EMAIL PROTECTED]> 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?
It makes request pro
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
ServerName domain1.com
DocumentRoot /var/www/domain1/
ServerName domain2.com
DocumentRoot /var/www/domain2/
NameVirtualHost IP2:80
The meaning of NameVirtualHost is used for other reasons as well.
Sent from my iPhone
On Dec 17, 2007, at 0:17, "Bryan Richardson" <[EMAIL PROTECTED]> wrote:
Hi Florian,
Thanks for the response. I guess my question is why have the
NameVirtualHost directive since the *same* IP address is re
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, <[EMAIL PROTECTED]> wrote:
> Hi Bryan,
>
> one example w
Hi Bryan,
one example would be a machine with two IP adresses, each of them has its own
www.domain
example:
NameVirtualHost IP1:80
NameVirtualHost IP2:80
but there are even more situations where NameVirtualHost could used. Maybe
with different websites on different ports, etc
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
