Victor KachiHere is How Google Will Mark Sites with HTTP Connection come July 2018
Google recently announced an innovation that would tell users on Chrome when a site is secured or not secured. Come July 2018, websites on HTTP connection will be marked as "Not secured", this will be indicated right in the address bar of Chrome browser.
Google has been warning all site owners to move their website on HTTP unsecured connection to a secured version HTTPS. Let's see the meaning of both connections.
WHAT IS HTTP?
HTTP stands for Hypertext Transfer Protocol, which is an application protocol for distributed, collaborative, and hypermedia information systems. HTTP is the foundation and unsecured way of data communication for the World Wide Web.
WHAT IS HTTPS?
HTTPS stands for Hypertext Transfer Protocol Secure, which communication protocol is encrypted by Transport Layer Security (TLS), or formerly, its predecessor, Secure Sockets Layer (SSL).
In a nutshell, HTTPS is the secured version of HTTP protocol which is considered as a good measure to decrease the risk of users being vulnerable to malicious attacks and other data modification.
Based on observations, Google has been moving the web towards HTTPS connection type for years, but it accelerated its efforts last year 2017 by making changes to Chrome’s user interface. Chrome 56, released in January 2017, started marking HTTP web pages that uses passwords or credit cards as “Not secure.” Chrome 62, released in October 2017, started marking HTTP sites with entered data and all HTTP sites viewed in Incognito mode as “Not secure.”
As a result, over 78 percent of Chrome traffic on both Chrome OS and Mac are now HTTPS, while 68 percent of Chrome traffic on Android and Windows is also HTTPS. But Google is not stopping there.
With the release of Chrome 68 in July 2018, here is how HTTP sites will look like in the address bar:
Here's how Google explained everything;
"Chrome’s new interface will help users understand that all HTTP sites are not secure, and continue to move the web towards a secure HTTPS web by default. HTTPS is easier and cheaper than ever before, and it unlocks both performance improvements and powerful new features that are too sensitive for HTTP.”
The plan was always to mark all HTTP sites as “Not secure.” Eventually, Google will change the icon beside the “Not secure” label and make the text red to further emphasize you should not trust HTTP sites.
Google also announced that the latest version of Lighthouse, its automated tool for improving web pages, now features mixed content audits to help developers migrate their sites to HTTPS. The new audit shows developers which resources a site loads using HTTP and which ones can be upgraded to HTTPS simply by changing the subresource reference to the HTTPS version.
Google has been warning all site owners to move their website on HTTP unsecured connection to a secured version HTTPS. Let's see the meaning of both connections.
WHAT IS HTTP?
HTTP stands for Hypertext Transfer Protocol, which is an application protocol for distributed, collaborative, and hypermedia information systems. HTTP is the foundation and unsecured way of data communication for the World Wide Web.
WHAT IS HTTPS?
HTTPS stands for Hypertext Transfer Protocol Secure, which communication protocol is encrypted by Transport Layer Security (TLS), or formerly, its predecessor, Secure Sockets Layer (SSL).
In a nutshell, HTTPS is the secured version of HTTP protocol which is considered as a good measure to decrease the risk of users being vulnerable to malicious attacks and other data modification.
Based on observations, Google has been moving the web towards HTTPS connection type for years, but it accelerated its efforts last year 2017 by making changes to Chrome’s user interface. Chrome 56, released in January 2017, started marking HTTP web pages that uses passwords or credit cards as “Not secure.” Chrome 62, released in October 2017, started marking HTTP sites with entered data and all HTTP sites viewed in Incognito mode as “Not secure.”
As a result, over 78 percent of Chrome traffic on both Chrome OS and Mac are now HTTPS, while 68 percent of Chrome traffic on Android and Windows is also HTTPS. But Google is not stopping there.
With the release of Chrome 68 in July 2018, here is how HTTP sites will look like in the address bar:
Here's how Google explained everything;
"Chrome’s new interface will help users understand that all HTTP sites are not secure, and continue to move the web towards a secure HTTPS web by default. HTTPS is easier and cheaper than ever before, and it unlocks both performance improvements and powerful new features that are too sensitive for HTTP.”
The plan was always to mark all HTTP sites as “Not secure.” Eventually, Google will change the icon beside the “Not secure” label and make the text red to further emphasize you should not trust HTTP sites.
Google also announced that the latest version of Lighthouse, its automated tool for improving web pages, now features mixed content audits to help developers migrate their sites to HTTPS. The new audit shows developers which resources a site loads using HTTP and which ones can be upgraded to HTTPS simply by changing the subresource reference to the HTTPS version.
Tap to Comment
Join Our Telegram Channel
Warning ⚠
Entclass Blog and its contents are protected by COPYRIGHT LAW (DMCA) with high-priority response rate. Reproduction without permission or due credit link back will cause your article(s) to be removed from search engines and disappearance of Ads on that page if monetized with Adsense.
Copy the link below and Share with your Friends:
About Entclass Blog
Entclassblog.com Is A Top Tech Blog That Provides Free And Cheap Browsing Cheats On Mtn, 9mobile, Glo And Airtel, Tweaking Guides And Tech News.
Newer Posts
Newer Posts
Older Posts
Older Posts
Ok
ReplyDeleteThat is good idea from them
ReplyDeleteThat's a good move, I support Google on this, https needs to become the default now and this line of action will help to hasten the switch.
ReplyDeleteGoogle now have their own HTTPS for bloggers using Blogspot
ReplyDeleteNice one
ReplyDeleteAnticipating
Already in Https
Why is glo not loading my blog? labisblog.com
ReplyDeleteIs your own Glo loading this blog without VPN?
DeleteNice one
ReplyDelete