Introduction
Internal websites that use HTTP instead of HTTPS have been facing an issue with the latest versions of Google Chrome and Microsoft Edge. Specifically, Chrome 126.0.6478.61 and Edge 126.0.2592.56 have started redirecting HTTP sites to HTTPS. This article will cover the details of this issue and provide some potential solutions.
HTTP vs HTTPS
HTTP (Hypertext Transfer Protocol) and HTTPS (HTTP Secure) are both protocols used for transmitting data over the web. The main difference between the two is that HTTPS encrypts the data being transmitted, making it more secure than HTTP.
The Issue
In the past, both Chrome and Edge would allow users to access internal websites using HTTP. However, in the latest versions of these browsers, HTTP sites are being automatically redirected to HTTPS. This can cause issues for internal websites that have not been configured to use HTTPS.
Why is Chrome Redirecting HTTP to HTTPS?
Google has been pushing for a more secure web for several years now. As part of this effort, they have been encouraging website owners to switch from HTTP to HTTPS. By automatically redirecting HTTP sites to HTTPS, Chrome is hoping to encourage more website owners to make the switch.
Impact on Internal Websites
The automatic redirect from HTTP to HTTPS can cause issues for internal websites that have not been configured to use HTTPS. For example, if an internal website is using hard-coded HTTP links, these links will break when the site is accessed via Chrome or Edge.
Potential Solutions
There are a few potential solutions to this issue:
-
Configure the Internal Website to Use HTTPS
The most straightforward solution is to configure the internal website to use HTTPS. This will ensure that the site can be accessed via Chrome and Edge without any issues.
-
Use a Different Browser
Another solution is to use a different browser that does not automatically redirect HTTP sites to HTTPS. However, this is not a long-term solution as other browsers may follow suit and start redirecting HTTP sites to HTTPS as well.
-
Modify the Internal Website to Use Relative Links
If modifying the internal website to use HTTPS is not an option, another solution is to modify the site to use relative links. This will ensure that the links on the site do not break when the site is accessed via Chrome or Edge.
The automatic redirect from HTTP to HTTPS in the latest versions of Chrome and Edge can cause issues for internal websites that have not been configured to use HTTPS. However, there are several potential solutions to this issue, including configuring the internal website to use HTTPS, using a different browser, or modifying the internal website to use relative links.
References
-
Type: Article
Title: Chrome is now redirecting all HTTP sites to HTTPS
Author: Mark Wilson
Publication: BetaNews
Date: February 11, 2023
-
Type: Online Resource
Title: HTTP vs HTTPS
Publication: SSL.com
Date: N/A