See https://issues.apache.org/bugzilla/show_bug.cgi?id=43218#c5
It will work if you use a different ServerName (even varying the port
would fix it) in the vhost with a different cert.
Regards, Joe
ahh, a bug.
changing port to non-standard would solve this problem but cause others...
i did
On Mon, Feb 21, 2011 at 10:09:14AM +0100, Hajo Locke wrote:
> >>
> >>Servername example.com
> >>SSLCertificateFile crt1
> >>
>
> >>
> >>Servername example.com
> >>SSLCertificateFile crt2
> >>
See https://issues.apache.org/bugzilla/show_bug.cgi?id=43218#c5
It will work if you use
> i dont find any fault in my conf. logging separatly did show separatly
> requests by same cert-content.
> either this is a tricky conf-thing or a bug.
what does apachectl -S say?
-
The official User-To-User support forum of the
Hello,
Krist wrote:
You don't have a NameVirtualHost directive?
What happens if you enter https://ip2.ip2.ip2.ip2 in your browser?
we use
NameVirtualHost *:80
in httpd.conf
I did some tests with setting NameVirtualHost to base-ip of the server
ip0.ip0.ip0.ip0, but nothing changed.
ip1 an
> Nobody has an opinion about this issue? I think this is critical. Either a
> bug in apache or a bug in my conf. my conf seems clean, i cannot solve this.
> it should be impossible that apache is mixing vhost-special directives. i
> can reproduce this on demand.
It's hard to tell which IP-based v
On Mon, Feb 21, 2011 at 10:09 AM, Hajo Locke wrote:
>
> Nobody has an opinion about this issue? I think this is critical. Either a
> bug in apache or a bug in my conf. my conf seems clean, i cannot solve this.
> it should be impossible that apache is mixing vhost-special directives. i
> can repro
Hello,
Apache 2.2.14
Hello List,
have a question to ssl and two vhosts.
i have 2 ip-based vhosts for enabling ssl for one domain in httpd.conf
Servername example.com
SSLCertificateFile crt1
Servername example.com
SSLCertificateFile crt2
document-root and Serv
