Google Is Making HTTPS the Chrome Default
Whatsapp Pinterest
Advertisement

With well over half of all websites now encrypted, it’s time to think of HTTPS as the default option rather than the exception. That is, at least, according to Google, which is changing the way Chrome handles secure vs. non-secure web pages. And about time too.

Over the last year there has been a push to switch all websites to use HTTPS (Hyper Text Transfer Protocol Secure). Google has been especially keen for sites to make the switch, and with more sites complying, it’s time to change the way we view the web.

Switching From HTTP to HTTPS

At the moment, sites that aren’t secure don’t have any special labels attached. As far as Chrome is concerned they’re considered the standard. On the flipside, sites which have HTTPS switched on get a green “Secure” label with a lock symbol attached.

However, this is all set to change over the next few months. As outlined on the Chromium Blog, with the release of Chrome 69 in September, the “Secure” label will disappear. And then at some point in the future, Google will remove the lock symbol as well.

In addition to this, with the release of Chrome 70 in October, standard HTTP pages will be labelled with a “Not Secure” warning with a red triangle attached. In other words, Google is turning everything on its head and labelling HTTP rather than HTTPS.

Google’s reasoning for making this change is that “users should expect that the web is safe by default”. So, rather than having HTTP as the standard to be expected and HTTPS as a rare beast to be celebrated, HTTPS becomes the standard and HTTP is vilified.

Google Ups the HTTPS Ante

This actually makes a lot of sense. Thanks to companies such as Google, more of the web is now encrypted, which means that’s the default. Unfortunately for sites which still haven’t made the switch from HTTP to HTTPS this just piles the pressure on.

It’s shocking it has taken this long for most of the web to switch to HTTPS. We were explaining what HTTPS means What Is HTTPS & How To Enable Secure Connections Per Default What Is HTTPS & How To Enable Secure Connections Per Default Security concerns are spreading far and wide and have reached the forefront of most everybody's mind. Terms like antivirus or firewall are no longer strange vocabulary and are not only understood, but also used by... Read More back in 2011, and it has taken seven years to get to this point. Still that was before we understood quite how much we’re all being surveilled Your Interest in Privacy Will Ensure You're Targeted by the NSA Your Interest in Privacy Will Ensure You're Targeted by the NSA Yes, that's right. If you care about privacy, you may be added to a list. Read More .

Image Credit: Stephen Shankland/Flickr

Explore more about: Google, Google Chrome, Online Security.

Enjoyed this article? Stay informed by joining our newsletter!

Enter your Email

Leave a Reply

Your email address will not be published. Required fields are marked *

  1. Nicholas N Finkelstein
    June 10, 2018 at 12:57 am

    There is no such word as "surveilled." The correct word is "surveyed."

    English does not have a noun form for the verb "to survey," so it borrows from the French: "surveillance."

    That's fine. But if you then make a back-formation from the French "surveillance" to create nonsense verbs such as "to surveil" or "surveilled," you're making up words.

  2. dragonmouth
    May 22, 2018 at 11:59 pm

    Big, Fat, Hairy Deal!
    They enforce secure access to sites in the name of "security and privacy" but then hoover up any and all user data.

  3. Gabriel
    May 21, 2018 at 1:48 am

    Am selling All kind of latest mobile phone, computers,cameras and accessories
    contact me on whatsapp number +1(334)8012192

  4. Marco Sarli
    May 20, 2018 at 5:35 am

    Google is nothing but a lot of talk and a badge. I am the owner of a Google site and, together with a lot of other problems, it is http and not https and there is nothing to do about it. I pay every month and the promised migration tool to the new Google sites (these should be https compliant) is over one year late on the announced release date. Trying to do the migration by myself, by copying and pasting and adjusting the code proved to be impossible as the new Google sites are just a rough framework and have too many limitations and unsolved problems.So Google, before looking at what others do and before acting as a net police force, should make sure that everything is in order with their products and keep the promises with their own paying customers.

  5. k1DBLITZ
    May 20, 2018 at 3:04 am

    The irony of these quotes is astounding.

    “users should expect that the web is safe by default”
    "Insecure sites (HTTP) will be called out."

    Is Google going to call themselves out when Chrome contains security vulnerabilities?

    "Still that was before we understood quite how much we’re all being surveilled."

    Google is the biggest offender when it comes to surveilling people!

  6. James Clark
    May 19, 2018 at 2:31 pm

    It's finally about time!