Chrome browser wants to see HTTPS on all pages

Modified on Mon, 27 Aug 2018 at 09:12 AM

The most popular browser, Google Chrome, would love to see your site operating under HTTPS on all pages, starting with the latest version 68 this July, 2018.


If you are on the latest version of AspDotNetStorefront (version 10.0+), then making the change is simple in your site admin console: Configuration > Settings > AlwaysUseHTTPS - TRUE - you'll also need to make sure your LiveServer setting matches the domain name used for your store exactly in this format: domain.com


If you are still running the previous versions (v9.x or even v8.x), then you will need a URL rewrite rule to get the job done. Here's how:


In order to setup "Always Use HTTPS" for v8 and v9 sites you need to create a rewrite rule, which requires the host server to have the IIS URL Rewrite Module installed (Vortx hosted sites will have this installed already, please check with your server host otherwise). Once that is in place, the steps are as follows:

1) Make sure that the UseSSL AppConfig is set to FALSE or you will run into an infinite redirect loop with the site. The UseSSL AppConfig ensures HTTPS links will be used for shoppingcart pages, account pages, receipt pages, etc, where sensitive data can be entered, but not throughout the entire site.


2) Add the following rewrite rule to your site Web.Config file in your site {root} (if hosted with Vortx, the Help Desk can assist you with this if needed):


<rule name="Redirect to HTTPS" stopProcessing="true">
    <match url=".*" />
    <conditions>
        <add input="{HTTPS}" pattern="off" ignoreCase="true" />
    </conditions>
    <action type="Redirect" url="https://{HTTP_HOST}{REQUEST_URI}" redirectType="Permanent" appendQueryString="false" />
</rule>

Make sure to put this rule under the system.webServer > Rewrite > Rules node.  Your Web.Config may not have a Rewrite node yet, so it might need to be created. 

When you are done it should look something like this:



NOTE: If you are not familiar with editing the Web.Config file, please engage a knowledgeable developer to assist. They will only require FTP access to your site files.

If hosted with Vortx, the Help Desk can assist you with this.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article