TRENDING ON ONEINDIA
- PM Modi Attends Swearing-In Ceremony Of Maldives New President, Ibrahim Mohamed Solih
- Free OnePlus 6T On Upcoming Black Friday Sale — Here's How
- Jawa Vs Royal Enfield — A Brief Comparison
- Salman Khan's Bharat Movie, Hoists Pakistani Flag In Indian Soil; Locals Upset
- The Health Wonders of Arugula: The Mediterranean Wonder Plant
- Did You Know That Cashback On Shopping Is Taxable?
- Winter Destinations In Uttarakhand
- Lakshya Sen Enters Semifinals Of World Junior Badminton Championship
Security is one of the major concerns in the digital space today. As such, Google has been moving towards a more secure web by strongly advocating that sites adopt HTTPS encryption. And within last year, the search giant also helped users understand that HTTP sites are not secure by gradually marking a larger subset of HTTP pages as "not secure".
While, the company has been encouraging developers to adopt or switch to HTTPS application, beginning in July 2018 with the release of Chrome 68, Google's own web browser Chrome will mark all HTTP sites as "not secure". Thus developers might have to now transition their sites completely to HTTPS and make the web safer for everyone.
So with the release of Google Chrome 68, the omnibox will reflect a "Not secure" label for all HTTP pages. However, this label will not only display that HTTP pages are unsecured but basically it will also give a strong push to prefer HTTPS over HTTP. The company has said that HTTPS is easier and cheaper than ever before, and it unlocks both performance improvements and powerful new features that are too sensitive for HTTP. Developers can check out the company's set-up guides to get started.
Meanwhile, Google in a blog post has also said, "Chrome is dedicated to making it as easy as possible to set up HTTPS. Mixed content audits are now available to help developers migrate their sites to HTTPS in the latest Node CLI version of Lighthouse, an automated tool for improving web pages. The new audit in Lighthouse helps developers find which resources a site loads using HTTP, and which of those are ready to be upgraded to HTTPS simply by changing the subresource reference to the HTTPS version."
Google is moving in the right direction to keep users safe on the web. With Chrome 68 and its new interface users will understand that all HTTP sites are not secure, and for developers, they will continue to move the web towards a secure HTTPS web by default. All in all, Chrome users in future may start seeing or they will see lots of "not secure" warnings to the left of the browser's address bar.