Google Inc. the discontinuation of FTP protocol support in Chromium and Chrome. In Chrome 80, scheduled for early 2020, a gradual phasing out of FTP support for stable branch users (a DisableFTP flag will be added for corporate deployments to revert FTP). In Chrome 82, it is planned to completely remove the code and resources used to operate the FTP client.
The gradual reduction of FTP support began in Chrome 63, in which
accessing resources via FTP protocol began to be flagged as an unsafe connection. In Chrome 72, the display in the browser window of content from resources loaded via 'ftp://' protocol was disabled (for example, the display of HTML documents and README files was discontinued), and the use of FTP for loading subresources from documents was prohibited. In Chrome 74, due to a bug, access to FTP through HTTP proxies stopped working, and in Chrome 76, proxy support for FTP was removed. Currently, downloading files through direct links and displaying directory contents remains functional.
According to Google, FTP is already almost unused — the share of FTP users is about 0.1%. This protocol is also insecure due to the lack of traffic encryption. Support for FTPS (FTP over SSL) is not implemented for Chrome, and the company sees no point in enhancing the FTP client in the browser considering its lack of demand, nor does it intend to continue supporting the insecure implementation (from the perspective of lack of encryption). When data needs to be downloaded via FTP, users will be advised to use third-party FTP clients — when trying to open links via 'ftp://', the browser will invoke the handler set in the operating system.
Source: opennet.ru
