Auto HTTPS: MySite.com vs. www.MySite.com

Website, Application, Performance Security
1

I set a page rule for http://www.MySite.com. It appears to be working correcting so that if I go to www.MySite.com or http://www.MySite.com I get directed to https://MySite.com.

However, if I go to MySite.com I get directed to http://MySite/cgi-sys/defaultwebpage.cgi and I am told that I may have reached the page due to IP address change, server misconfiguration, or site may have moved to a different server.

In response, I set a second page rule for MySite.com and auto https. But, I am getting same result.

How to fix? People usually just type in MySite.com, I imagine.

2

Post your actual domain.

3
4

Opening your naked domain on HTTP redirects me to its HTTPS version. That is what you want, right?

5

Yes. I checked on a different browser (phone) and it appears to be working right. Still not working in FireFox. Weird. Thanks for checking.

6

Probably a caching issue.

7

So, do I actually need both of those rules then? Or will just one suffice?

8

Can you post a screenshot of these rules?

9

ScreenShot
ScreenShot.png1585×1205 109 KB

10

You can delete both rules and simply set it domain-wide under the Crypto section.

11

Great thanks.

12

This is very frustrating.I deleted the rules + enabled the feature in the Crypto section. Now, whenever I go to naked version, www, http, or https, I get redirected to just "http//: But, site is working fine on my phone. Seems to be a browser issue, but I have zero clue why it’s now doing this.

13

I still get an HTTPS redirect, so it likely still is a caching issue. Clear your browser cache again.

14

Ack. That worked…thank you. New to this stuff.

15

This topic was automatically closed after 30 days. New replies are no longer allowed.