The HTTP protocol has been riddled with loopholes for 29 years: Firefox can be directly disabled

Time: 2020-03-26Source: Huajun InformationAuthor: Internet

We can open a variety of websites to obtain information, and the HTTP (Hypertext Transfer) protocol is indispensable. Born in 1991, it forms a channel connecting the Internet and netizens. Most of the various URLs we enter in our browsers every day use this protocol.

However, the biggest problem with the 29-year-old HTTP protocol is that it is insecure. There is no encrypted transmission, which can easily lead to vulnerability attacks, Internet fraud, etc. Therefore, HTTPS came into being, using TLS (early SSL) for encryption protection, which is now supported by most websites.

If your website is still stuck in the HTTP era, you need to act quickly, browsers are already preparing to abandon you.

The latest internal version of Firefox 76 Nightly has added an experimental new option. When turned on, it will only support the HTTPS protocol and directly block all HTTP protocol websites.

This feature is currently hidden. To access it, you need to first enter in the Firefox browser address bar:

about:config

Then search to find the following options:

dom.security.https_only_mode

It is turned off (false) by default and can be turned on manually. Then your Firefox 76 browser can only open HTTPS protocol URLs. When trying to access HTTP protocol websites, it will give an error message of "Secure Connection Failed" (Secure Connection Failed).

Mozilla did not disclose when this option will be publicly available in the future or when it will be turned on by default. I believe it is only a matter of time. Chrome 68 has already marked HTTP websites as unsafe.

In addition, both Chrome and Firefox are promoting the disabling of the FTP transfer protocol, and Firefox will turn it off by default starting from 77.

Related articles更多>>