Just like Google Chrome, which is currently the number one Chromium browser, Microsoft Edge is advocating for a more secure web, and encouraging everyone to use HTTPS is one way to do this.
So starting this week, Microsoft Edge 92 (currently in the Dev channel) comes with a preview of a feature that allows users to force an HTTPS connection when loading websites.
In other words, when this feature is enabled, Microsoft Edge will first attempt to load the HTTPS version of a website, therefore trying to make sure the connection is secure.
“Automatic HTTPS switches your connections to websites from HTTP to HTTPS on sites that are highly likely to support the more secure protocol. The list of HTTPS-capable websites is based on Microsoft’s analysis of the web, and helps enable a more secure connection on hundreds of thousands of top domains. Automatic HTTPS upgrades your connection only on HTTPS-capable domains by default in order to prevent connection errors and potential performance issues,” Microsoft explains.
If you’re running at least Microsoft Edge version 92 as part of the Dev or Canary channels, you can easily enable the new feature from the privacy screen in the settings menu. The toggle is called:
Automatically switch to more secure connections with Automatic HTTPS
Coming in Edge 92 to everyone
Worth knowing, however, is that you may encounter some page loading errors if you force Edge to use HTTPS exclusively without allowing a fallback to HTTP. This is because some sites don’t use HTTPS just yet, but Microsoft says some users might actually prefer to stick with this approach for better security.
“In addition to security, we know that productivity and performance are top of mind for our users. When enabled, Automatic HTTPS defaults to upgrading navigations only on domains that are likely to support HTTPS. Scoping to HTTPS-capable domains reduces the likelihood of connection failures, as well as potential performance or reliability issues with “try HTTPS first and fall back to HTTP” approaches,” it says.
Microsoft is still in the testing phase for this feature, but it should be part of the Edge 92 update when it reaches the production channel.