Around this time last year, Google's Chrome browser started labeling HTTP pages with text fields as "Not secure" when you enter any information. And today the company has announced the next and final step in its strategy meant to get website owners to switch to HTTPS encryption.
From July, when Chrome version 68 is set to become stable, all HTTP pages will be labeled "Not secure", as seen in the image below. For those webmasters who still haven't transitioned to HTTPS, the company offers set-up guides to help them get started and explain why encryption is important.
In the past year, progress on the HTTPS front has been quite remarkable, with 81 of the top 100 sites on the web now using it by default. Furthermore, over 68% of Chrome traffic on Android and Windows is protected, along with over 78% of Chrome traffic on Chrome OS and macOS.
Can't see the point of HTTPS when you're not handling any sensitive content like login, mail, and alike. Except that it requires more resources on client's and server's side. A strategy? More like hands twisting, which has been the internet's most e...
I never had any problems with Firefox. In fact, is faster and lighter than Chrome.