The world’s most popular web browser will soon be taking the next step towards a more secure internet connection, by marking additional HTTP pages as “not secure”.
For those who aren’t sure about the difference between HTTP and HTTPS, it’s very simple: HTTPS means that a web page is coded in such a way that prevents outside parties from reading any information entered, keeping it safe from hackers
As things stand, Chrome only marks HTTP pages as “not secure” if they require very personal details, such as passwords or credit card information. But from October 2017, they aim to include the “not secure” warning to two additional situations:
Google Chrome aims to eventually show a “not secure” warning on every HTTP page, regardless of whether on incognito mode or not.
Google has given us some sure-fire warnings to start seriously thinking about transitioning to HTTPS in the near future. The Chrome Security Team claims that it’s easier and less expensive than ever to set up, and includes new features which aren’t able to run on HTTP.
The announcement has brought forward our date to secure our domain with HTTPS, and we’ll be looking to bring it forward with our clients as well.
You can check out Google’s HTTPS setup guide here to help you with the setup process.