[BlueOnyx:20083] Re: SSL redirection

[Darren Wolfe]

> -----Original Message-----
> From: Blueonyx [mailto:blueonyx-bounces at mail.blueonyx.it] On Behalf Of
> Michael Stauber
> Sent: 08 September 2016 18:41
> To: BlueOnyx General Mailing List <blueonyx at mail.blueonyx.it>
> Subject: [BlueOnyx:20082] Re: SSL redirection
> 
> Hi Darren,
> 
> > But if I try to go to a site that does not have
> > an SSL certificate using https -
> > https://www.othersite.com
> > I would expect it to fail, but instead I first
> > get a "ERR_CRT_COMMON_NAME_INVALID" warning from
> > Chrome, and then if I proceed it redirects me
> > to https://www.site.com
> >
> > It has been this way in BX for as long as I
> > can remember, but is it something that is
> > actually solvable?
> 
> Generally: This is a fundamental protocol issue. You will have this with
> any browser and any web server.
> 
> So your scenario is this:
> 
> Vsite named www.site.com with these aliases:
> 
> site.com
> www.othersite.com
> othersite.com


No, that's the thing - they are two entirely different vsites!
Each does have web alias redirects enabled, but only to catch their non-www prefixed domain and send it to www. No others. They are completely separate, only sharing the same server and same public IP address.

So: vsite1 is www.site.com, which has https enabled
Vsite2 is www.othersite.com, which does not have https enabled
If I go to https://www.othersite.com, it tries to, at first, connect me to https://www.othersite.com which throws the certificate error, then immediately redirects me to https://www.site.com after I click through the certificate warning.