ORHL will be marked as "not secure" in Chrome browser soon

[gomblue]

I received an automated email from Google. It seems important. They say that the ORHL page will be marked as "not secure" in the Chrome browser very soon.

How would I make that page secure? Are there other pages I should be worried about now?

Also, in the future: "The new warning is the first stage of a long-term plan to mark all pages served over the non-encrypted HTTP protocol as “Not Secure”." Does this mean I will need to make all pages "secure"?

I have a ticket open on this, but it seems like something others may want to pay attention to.

[ILoveHostasaurus]

Typically any link on the site that goes to a checkout or customer account page, such as what Miva Merchant users often include in global headers, or on the basket page, should be https to avoid that issue. If you've hard coded any links, those would need to be altered, but if you're using tokens in your page templates, normally they should be secure already. Support can investigate, and if a stock theme is not secure towards the checkout pages, that would be a bug we will report to our developers, but can fix for you immediately.

You can also choose to run the entire site in https mode but that will require settings changes that support can help you with, and also should only be done if you are sure you haven't hard coded any content into the pages using http:// URL's, such as images, since running in secure mode but with insecure content will produce errors on the shoppers' computers.

[gomblue]

Thanks David.

I'm not much of a coder, but it appears that the footer is ok, but the Divino header is using http in two occasions:

<a href="http://&mvt:global:domain:name;/" title="&mvt:global:store:name;" class="align-center" rel="nofollow">

<a href="http://&mvt:global:domain:name;/" title="&mvt:global:store:name;" class="column x-large-three-tenths large-one-third large-align-left align-center" id="desktop-logo">

I'll wait for support to take a look.

[Bruce - PhosphorMedia]

You can just replace
http://&mvt:global:domain:name;/ with "/" or //&mvt:global:domain:name;/