Google will soon enforce HTTPS by default, this will cause issues with forwards (1 Viewing)

Google Chrome will soon enforce HTTPS by default​

Google Chrome will soon enforce HTTPS by default




I turned on that setting on desktop and android and it immediately caused issues with forwarding at WHC and throws up this error.




I have my domain at WHC set to forward from MapleRed.ca to https://mapledots.ca/forsale/maplered.ca

This throws up the error above when Google flicks the switch in my first picture which renders the forwarding feature almost useless.

Luckily there is the free dns manager at WHC so now I have to figure out how I can set this on hundreds of domains to bypass this error message on forwards.

According to the article google will throw that switch pretty soon and I want to make sure I and even WHC is prepared for it.

I know WHC uses cPanel in their underpinnings so a little research is warranted to see if WHC can throw a master switch of some sort instead of the clients having to try and manually edit all fowards.

Any feed back on this? @FM

MapleDots said:

Any feed back on this? @FM

Click to expand...

I've been thinking about this already, but for this to work correctly, we'd need an SSL certificate for the domains that are being forwarded, too. It's not directly in the works, but I'm gathering information as to what this would entail.

Right on que

Looks like Webnames has the problem solved, may have to register a couple of domains there to see how they are doing it.

There are going to be sooo many HTTPS errors when google makes this a default action.

I read it's coming down the pipe possibly as the soon as the next major chrome release.

Crap, that means I have to add domains as addon domains with the full domain and URL in the bar. That will cause hundreds of certificates needing to be generated.

So even if someone like @theinvestor forwards domain1 to dncanada.com they will get a security error and it will not display dncanada.com

Same for me forwarding domain1.ca to mapledots.ca/forsale/domain1.ca it will kick out an error.

The only way around it at the moment is to set it as an addon domain and show https://domain1.ca in the address bar. It means the end of forwards as we know them today unless they come up with a solution.

Direct link to post on X.com

@FM very soon now the url forwarding/redirect will become obsolete, it looks like companies are getting a head start on implementing this.


Looks like Webnames and Spaceship has it now, if it comes to be I will have to transfer domains I forward to spaceship. I usually renew all my domains in January but I knew this was going to become an issue so at the moment I am only renewing month by month in case I have to use another service when chrome starts to enforce https on forwards/redirects.

Maybe register a domain at webnames and spaceship to see how they are accomplishing it.

MapleDots said:

Maybe register a domain at webnames and spaceship to see how they are accomplishing it.

Click to expand...

very soon now the url forwarding/redirect will become obsolete, it looks like companies are getting a head start on implementing this.

Click to expand...

I appreciate the ping

Of course, we watch our competitors I'm pretty sure I know what we need for it, but we'll likely need to add server resources to it, as it will increase the load. We'll need to see where can fit it into our roadmap.

I've done some research before on this topic in connection with domain parking, so that should help.