Firefox Developers Firefox's move to mark all pages opened over HTTP with an insecure connection indicator. The change is scheduled to be implemented in the Firefox 70 release scheduled for October 22nd. In Chrome, an insecure connection warning indicator for pages opened over HTTP is displayed since release
proposed in July last year.
Also in Firefox 70 remove the "(i)" button from the address bar, limiting itself to the permanent placement of the connection security level indicator, which also allows you to evaluate the state of code blocking modes for tracking movements. For HTTP, the security issues icon will be explicitly shown, which will also be displayed for FTP and in cases of certificate issues:
It is expected that displaying an insecure connection indicator will encourage site owners to switch to HTTPS by default. By Firefox Telemetry service, the global share of page requests over HTTPS is 78.6%
(a year ago 70.3%, two years ago 59.7%), and in the USA - 87.6%. Let's Encrypt, a non-profit, community-controlled CA that provides free certificates to anyone, has issued 106 million certificates covering about 174 million domains (up from 80 million domains a year ago).
The move to mark HTTP as insecure is a continuation of earlier attempts to force the move to HTTPS in Firefox. For example, since the release A security issue indicator has been added to the browser, which is displayed when accessing pages containing authentication forms without using HTTPS. Also access to new Web APIs - in for pages opened outside a protected context, displaying system notifications through the Notifications API is prohibited, and in insecure accesses block requests to call getUserMedia() to gain access to media sources (for example, camera and microphone). The "security.insecure_connection_icon.enabled" flag was also previously added to the about:config settings, which allows you to optionally enable the insecure connection flag for HTTP.
Source: opennet.ru