Chrome 56 Stable: Feeds HTTP pages unsafe

The end of HTTP: The allegedly preparing surprises for them of but also for Webmasters. Starting in January 2017 (when Chrome 56 Stable is released) all HTTP pages will be marked as “not secure.”

To date, the company uses a neutral list for sites that do not use HTTP. All web pages that contain mixed content (HTTP and HTTPS) fall into this category.https

"Chrome is currently showing HTTP connections with a neutral pointer," says Emily Schechter in a blog post.

"This does not reflect the real lack of security for HTTP connections. When you upload a website via HTTP, someone else on the network may view or modify the website before it reaches you. ”

Google will deliberately begin to implement its plan gradually. Schechter reports that according to studies, users do not pay attention to the warnings that appear very often.blog-image-1

So Google will take other measures to encourage the use of HTTPS, such as the use of HTTPS as a positive signal for the ranking of the page.

Since December 2015, it has adapted its indexing system and crawls HTTPS pages, ranking them better than HTTPS in search. The company recently announced that more than half of the pages visited with Chrome from desktops are served over HTTPS.

Last month, Google implemented HTTP Strict Transport (HSTS) on the google.com domain to prevent users from connecting to the insecure HTTP protocol on its main page.

iGuRu.gr The Best Technology Site in Greecefgns

every publication, directly to your inbox

Join the 2.087 registrants.

Written by Dimitris

Dimitris hates on Mondays .....

Leave a reply

Your email address is not published. Required fields are mentioned with *

Your message will not be published if:
1. Contains insulting, defamatory, racist, offensive or inappropriate comments.
2. Causes harm to minors.
3. It interferes with the privacy and individual and social rights of other users.
4. Advertises products or services or websites.
5. Contains personal information (address, phone, etc.).