Redirect to https using https non www

[bwnbwn]

I posted my issue here in the IIS forum but after researching this all day I am pretty sure I have found my solution.
[webmasterworld.com...]
I purchased a UCC SSL Certificate and have 10 domains under it.

I am on a cloud dedicated server and have my SSL domains mapped to different ports on internal cloud IP's. All the mapped domains are the www version.
If I add the non www to the SSL this is a domain so I will need to upgrade to 30 domains under the UCC certificate. If I had know this before I would have but I am at this point right now.

The issue is when a user types in example.com they are redirected to the https fine, when the user types in www my domain .com user redirected fine. http:// mydomain.com redirected fine. All the test I did were fine then I got the bright idea to check https: // mydomain.com

The problem and my question concerning SEO (I already know what 99% of you are going to say but am putting this issue here because I have never seen it before).

If I type in https: // mydomain. com the user gets a certificate warning and is redirected to the domain I purchased the UCC under.

The reason is the call hits the 80 port 1st and redirects there is nothing I know to do to stop it. Maybe somebody will but I don't right now.

What would you do? Let it go and hope a competitor never decides to link to https :// mydomain .com or have the non www mapped in the cloud, upgrade the SSL, and fix the issue.

If you would let it go do you think it will cause issue down the road?

[aakk9999]

Interesting - your post made me check one of sites I look after (also .NET on IIS) and there is exactly the same issue there too. And yet the site has been running like this for at least 8 years with no problems reported.

I would (will) ignore the problem for now and monitor logs periodically. Once you start to get certain number of hits to https//example.com then perhaps it is the time to buy a certificate that covers more domains, install it and let the your site do the redirect to www version.

Or maybe logs will show that you will never have to do it as there are no enough hits to the https without www.

[bwnbwn]

aakk999 what I am concerned about is others finding the problem and linking to the https :// domain. com version. Then I have a problem. I now have a different domain showing for a 301. I will assume GB will follow the 301 and spider the site, now I got a problem.

All this https is pretty new for the most part and with more and more going to https it will become a standard check IMO.
aakk999 pretty sure the certificate for the domain covers both the non and www version you just need to open a new port same IP or add it to a new IP and 443 port.

I am correcting it now. It is just difficult to get a security tech that needs to map the ip through a firewall why I need this done. being on a cloud server has it advantages, but I miss the days when all I needed to do was add an IP and do it myself.

[bwnbwn]

aakk999 I posted the solution on the Microsoft thread linked above Man it was a go around to get a solution. But I learned something today that is a good thing.