Mobile app version of vmapp.org
Login or Join
Smith883

: Old domain, new site on Shopify - no more SSL, but SSL URL is stuck in visitors history I have built a new Shopify site for a client, and since I cut over DNS, I learned that there was

@Smith883

Posted in: #DomainForwarding #Http #Https

I have built a new Shopify site for a client, and since I cut over DNS, I learned that there was a forwarding redirect set up for the old site to drive traffic from HTTP to HTTPS.

Now that we've migrated to Shopify, the site is no longer hosted with SSL until you get to the checkout page.

The problem is that when repeat visitors have the HTTPS URL in their auto-fill history in the address bar, they attempt navigating to the site, but they are navigating to the HTTPS URL, and since Shopify has no SSL until you reach checkout, every browser gives a warning of malicious intent by hackers.

Any ideas?

I've tried forwarding from HTTPS to HTTP, but that hasn't done anything as of yet.

10.01% popularity Vote Up Vote Down


Login to follow query

More posts by @Smith883

1 Comments

Sorted by latest first Latest Oldest Best

 

@Correia994

If Shopify allows you to change your nameservers then Cloudflare may work. I haven't tried for Shopify but CF has a free SSL as a proxy. It works on "flexible" mode even if the origin is in HTTP mode. Turn on "authenticated origin pulls" to help compensate for this HTTP origin. We do this all the time with sites that shouldn't be allowed to run HTTPS.

Now, the issue may be that Shopify doesn't understand SSL mode. If this is the case, first start by forcing HTTPS with a page rule. If you are still getting warnings in console (or things not loading), then try looking in your theme resources for insecure assets. Make them all relative. Then go through any WYSIWYG data and other areas where routes are exposed to do the same thing. If you're lucky things will work. If not, at least you can suppress the insecure warning and allow them to connect to Shopify before you swap them back to HTTP mode :)

Oh, if your client had HSTS set, you can do a 0 second cache time to disable it and "reset" any browsers with HSTS (307 redirect) in cache still.

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme