Issues with HTTPS non-www to HTTPS www (or whatever subdomain used for HubSpot) Forwarding
We recently enabled the SSL functionality on our COS. Our domain is storyblock.media and our HubSpot COS URI is https://www.storyblock.media. We use GoDaddy as a domain registrar and we have forwarding setup to forward (http://storyblock.media and http://www.storyblock.media) to https://www.storyblock.media. However, the issue is found when going to https://storyblock.media. It does not forward to https://www.storyblock.media. Instead, the browser loads a blank screen with an error message.
Why? When you setup domain forwarding, visitors technically visit an IP address on GoDaddy's server first that 301 redirects them to the desired destination that's setup in domain/dns settings. This does not work for HTTPS traffic since this GoDaddy server does not have a valid SSL cert for the domain. Therefore, when you attempt to redirect HTTPS traffic via this method, it bellyflops and doesn't go anywhere...
Why is this an issue? Everyone is used to chopping off the www. Chances are they will also chop off the https too, but when they do not, they are not going to end up where they want to go. Who knows. This might result in a few lost backlinks too. Haven't thought out any other SEO issues/implications yet.
That's the problem. Open to others' solutions. Here are two ideas I've had:
1) I can relatively easily setup an SSL cert on my own server with it's only purpose to forward HTTPS non-www to HTTPS www, but that would cost $$ and not solve everyone's issue.
2) HubSpot could setup an IP address to point naked domains to and direct the traffic accordingly (I'm not 100% on how things are setup on their end -- I know there are reasons they utilize the cname setup, but forget why exactly.).