Google Enhances Chrome Security: Insecure HTTP Requests Automatically Upgraded to HTTPS
Google Enhances Chrome Security: Insecure HTTP Requests Automatically Upgraded to HTTPS
- Linux Kernel Removes strncpy After Six Years and 362 Patches
- Linux Kernel Drops 40-Year-Old AppleTalk Protocol — AI-Generated Patch Flood Was the Last Straw
- Apple’s Native Linux Container Tool Has Arrived — But Can It Really Replace Docker?
- 60% of MD5 Password Hashes Can Be Cracked in Under an Hour with a Single GPU
- Dirty Frag: Root Access on Every Major Linux Distribution — No Patch, No Warning
Google Enhances Chrome Security: Insecure HTTP Requests Automatically Upgraded to HTTPS
News on October 31, Google has taken a significant step in improving the security of the Chrome browser: users accessing insecure HTTP links will now be automatically upgraded to HTTPS requests 100% of the time.
This feature, known as HTTPS-Upgrades, automatically attempts to redirect users to the encrypted https:// protocol after they visit old links that begin with http://.
Google began rolling out this feature in Chrome back in July of this year, and on October 16, it became available to all users in the stable channel.
Chris Thompson, the Project Manager at Google, stated, “We enabled HTTPS-Upgrades by default in the main branch version last week, and it has now been pushed to all stable versions.”
For more information about HTTPS-Upgrades, you can visit this link. Note that once enabled, Chrome will automatically upgrade all addresses starting with http:// to https://, which is a more secure protocol that encrypts user’s web traffic. Even if a user clicks on links explicitly labeled as http://, Chrome will attempt the upgrade. If the upgrade fails, Chrome will fall back to http://.
