With well over half of all websites now encrypted, it\u2019s 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.<\/p>\n
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\u2019s time to change the way we view the web.<\/p>\n
At the moment, sites that aren\u2019t secure don\u2019t have any special labels attached. As far as Chrome is concerned they\u2019re considered the standard. On the flipside, sites which have HTTPS switched on get a green \u201cSecure\u201d label with a lock symbol attached.<\/p>\n
However, this is all set to change over the next few months. As outlined on the Chromium Blog<\/a>, with the release of Chrome 69 in September, the \u201cSecure\u201d label will disappear. And then at some point in the future, Google will remove the lock symbol as well.<\/p>\n Since HTTPS should be the default, Chrome will remove the “Secure” indicator for HTTPS sites. It’s the new default. Insecure sites (HTTP) will be called out. https:\/\/t.co\/JW6Bms0APV<\/a> pic.twitter.com\/kXq7x7FAsk<\/a><\/p>\n \u2014 \/dev\/eloper (@mattiasgeniar) May 18, 2018<\/a><\/p><\/blockquote>\n In addition to this, with the release of Chrome 70 in October, standard HTTP pages will be labelled with a \u201cNot Secure\u201d warning with a red triangle attached. In other words, Google is turning everything on its head and labelling HTTP rather than HTTPS.<\/p>\n Google\u2019s reasoning for making this change is that \u201cusers should expect that the web is safe by default\u201d. 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.<\/p>\n This actually makes a lot of sense. Thanks to companies such as Google, more of the web is now encrypted, which means that\u2019s the default. Unfortunately for sites which still haven\u2019t made the switch from HTTP to HTTPS this just piles the pressure on.<\/p>\n It\u2019s shocking it has taken this long for most of the web to switch to HTTPS. We were explaining what HTTPS means<\/a> back in 2011, and it has taken seven years to get to this point. Still that was before we understood quite how much we\u2019re all being surveilled<\/a>.<\/p>\n \u062b\u0628\u062a \u062f\u0627\u0645\u0646\u0647\u060c \u0645\u062f\u06cc\u0631\u06cc\u062a \u0633\u0631\u0648\u0631\u060c \u0644\u06cc\u0646\u0648\u06a9\u0633\u060c \u0627\u0645\u0646\u06cc\u062a\u060c \u067e\u0634\u062a\u06cc\u0628\u0627\u0646\u06cc<\/p>\n","protected":false},"excerpt":{"rendered":" With well over half of all websites now encrypted, it\u2019s 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 […]<\/p>\n","protected":false},"author":1,"featured_media":3957,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[36],"tags":[],"class_list":["post-3956","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-36"],"_links":{"self":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/3956","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/comments?post=3956"}],"version-history":[{"count":0,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/3956\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/"}],"wp:attachment":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/media?parent=3956"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/categories?post=3956"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/tags?post=3956"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
Google Ups the HTTPS Ante<\/h2>\n