A new Chromium code update has revealed that Google is set to make a subtle security change to its Chrome web browser that delivers major security improvements. The code suggests that Google Chrome will soon attempt to connect to the HTTPS version of a website by default when users leave out the security protocol altogether.
Currently, if you leave out the security protocol when browsing, as most do when typing in a web address, Chrome will first try the insecure or HTTP version of the site. Then, when sites do have a secure version, a redirect will occur taking individuals to the HTTPS version. Chrome will then make a record of the HTTPS version and jump straight there next time the user navigates to the same domain.
However, it now appears that Chrome will switch its priorities, taking users to the HTTPS version first where possible.
- Here's everything you need to know about DNS-over-HTTPS
- Check out our roundup of the best endpoint protection software
- Also, keep your devices virus-free with the best malware removal software
A security switch-up
The new Chromium code indicates that Chrome will instead attempt to connect to the HTTPS version of any URL first. Where secure versions don’t exist, Chrome will wait either three or 10 seconds before connecting to the HTTP version instead.
The original HTTPS security protocol was introduced all the way back in 1995 and has slowly but surely become the default method of securing online portals. When sensitive information is sent over an HTTPS connection, it’s not possible for anyone else to snoop on the transit.
Although some would say that this simple change to Chrome's security protocols is long overdue, users will still have to wait a little while before its implemented.
The HTTPS default has only just appeared in the Chromium code, so it probably won’t appear in a stable Chrome version for a few months yet at least.
- We've also highlighted the best antivirus software