seems to add an dedicated IP for the SSL stuff :-/
Take care see you soon
-Message d'origine-
De : Matus UHLAR - fantomas [mailto:[EMAIL PROTECTED]
Envoyé : dimanche 23 septembre 2007 17:58
À : users@httpd.apache.org
Objet : Re: [EMAIL PROTECTED] SSL server IP/port conflict
Objet : Re: [EMAIL PROTECTED] SSL server IP/port conflict
On 21.09.07 16:33, Axel-Stéphane SMORGRAV wrote: HTTPS and
NameVirtualHost
do not go well together. NVH is based on the Host header.
However Apache
cannot read the Host header before the SSL session has been
established
: Re: [EMAIL PROTECTED] SSL server IP/port conflict
On 21.09.07 16:33, Axel-Stéphane SMORGRAV wrote: HTTPS and
NameVirtualHost
do not go well together. NVH is based on the Host header.
However Apache
cannot read the Host header before the SSL session has been
established.
But in order
On 21.09.07 16:33, Axel-Stéphane SMORGRAV wrote: HTTPS and NameVirtualHost
do not go well together. NVH is based on the Host header. However Apache
cannot read the Host header before the SSL session has been established.
But in order to establish the SSL session, Apache needs to know what
Perhaps this can help you:
http://httpd.apache.org/docs/2.0/ssl/ssl_faq.html#vhosts
There are some limitations about SSL and name-based virtualhosts.
It was a shok for me when I read that...
[EMAIL PROTECTED] escribió:
Hello,
I have this error after setup 2 virtualhost based on the same
HTTPS and NameVirtualHost do not go well together. NVH is based on the Host
header. However Apache cannot read the Host header before the SSL session has
been established. But in order to establish the SSL session, Apache needs to
know what virtual host it is for to determine what certificate
