Are You Ready For Google Chrome’s HTTPS Change In January?
The New Year is just around the corner and along with changing our calendar we also need to be aware of the change Google Chrome is making in regards to sites not on HTTPS. As a top web development company this is one of those issues that we feel everyone should be aware of to understand how it may or may not impact them in the coming year.
What is the change to Chrome?
Starting in January 2017, with the version 56 update, HTTP pages that collect passwords or credit cards will be marked as non-secure, as part of a plan to mark all HTTP sites as non-secure. The way the display will be changed will be in the address bar with the addition of “Not secure |” before the normal web address.
This is an interesting change that Google is making as other browsers have yet to put a line in the sand in this regard. Currently Google Chrome indicates all HTTP connections with a neutral indicator, as in they don’t let you know one way or the other how secure the HTTP connection is.
One reason behind the change is that Google wants their users to be aware of security and a lack there of when it occurs. The feeling is that people ignore warnings that occur too often and also do not interpret a lack of a secure icon as any type of warning. This is the first step in a multi-layered plan to label HTTP sites more clearly and accurately.
What does it mean for you?
What it means will vary depending on your current site and setup. More than half of Chrome desktop page loads are served over HTTPS per Google. If your site is already using HTTPS then there is nothing to worry about. Also if your site does not collect passwords or credit cards, then nothing will change for you.
The primary point of this change is to ensure that Google’s primary customers are aware if a site might not be secure before they type in passwords or credit card information. The concern being that a hacker could intercept information on an unsecure connection and currently there are plenty of unsecure connections that users might think are secure.
If you do need to switch to using secure SSL certificates, the change can only be viewed as positive in the long run. While there is a time and cost component for a change, you are also increasing your site’s security which is something you can then report to users to help increase the trust in your business and brand. On top of that, using HTTPS can take advantage of a different protocol which can increase your site’s speed.
The bottom line
The bottom line is that this is another instance of Google making a change to the industry whether we like it or not. They are focused on their customers’ wants and needs of which security is a big part of. As with all Google changes, there really isn’t much you can do about it so making sure that you are ready for Google Chrome’s HTTPS change in January by reviewing how it may impact you is a good idea.
Be sure to check back every Monday, Wednesday and Friday for great new Lounge Lizard blog articles.