That error isn't from an http/https conflict. It's what happens when you hit a page using a hostname that isn't in the SSL cert. For example, I could set up www.nelson.net to point to the same IP as www.marketo.com. But if I went to https://www.nelson.net, my browser would barf because Marketo's cert doesn't cover www.nelson.net. The same can go for subtle differences within the same domain, i.e. you can't hit home.nelson.net unless the cert either contains home.nelson.net or is a wildcard for *.nelson.net.
Sounds promising! Thanks. I'll look into it to confirm.
On Thursday, July 9, 2015, Sanford Whiteman <firstname.lastname@example.org>