On Fri, May 10, 2024 at 5:53 PM Tatsuki Makino
wrote:
> Hello.
>
> By the way, do you have the setting enabled to use the Host header used to
> switch NameVirtualHost during TLS negotiation?
> I don't know how to do that since the Japanese documentation is rarely
> updated :)
> Were those things
Hello.
By the way, do you have the setting enabled to use the Host header used to
switch NameVirtualHost during TLS negotiation?
I don't know how to do that since the Japanese documentation is rarely updated
:)
Were those things implemented?
Regards.
--
On Fri, May 10, 2024 at 4:10 PM John wrote:
> On Fri, 2024-05-10 at 15:48 -0400, Sean Conner wrote:
> > It was thus said that the Great Chris me once stated:
> > > I set up each entry with but when I do that, the
> > > second site will complain that the cert is for site1. So if I go to
> > > sit
On Fri, 2024-05-10 at 15:48 -0400, Sean Conner wrote:
> It was thus said that the Great Chris me once stated:
> > I set up each entry with but when I do that, the
> > second site will complain that the cert is for site1. So if I go to
> > site2.com, I get a browser error that the cert is for site1
It was thus said that the Great Chris me once stated:
> I set up each entry with but when I do that, the
> second site will complain that the cert is for site1. So if I go to
> site2.com, I get a browser error that the cert is for site1. It will show
> me the content for site1.
On my developmen
I found NameVirtualHost *:443 was commented out in ports.conf, I changed that.
Now I am back to the ssl protocol error for the second site.
From: Chris me
Sent: Friday, May 10, 2024 8:40 AM
To: users@httpd.apache.org
Subject: RE: [users@httpd] Multi site SSL problems
I set up each entry with b
I set up each entry with but when I do that, the second
site will complain that the cert is for site1. So if I go to site2.com, I get a
browser error that the cert is for site1. It will show me the content for site1.
I am not sure why the difference, my non ssl hosts, ie all
work fine, each s
