Google Chrome will stop supporting all FTP addresses from the fixed release of Chrome 80, and the company plans to completely remove the FTP-related code from Chrome 82.
The file transfer protocol (FTP from File Transfer Protocol *) used by websites to download and download files is quite old and does not have encryption. However, some computer manufacturers have drivers or even firmware updates from FTP sites, which is not safe.
- We mention the whole name to confuse it with the well-known anarchist slogan that uses the same initials. Keep your clothes…
In Chrome 76, if you try to access images or PDF files on FTP sites, downloads can be made, but files cannot be displayed by the browser (you can not read online before downloading). However, Chrome still displays the directory listings of the contents of an FTP server.
But today, Google he said its intention to stop generally supporting FTP URLs in Google Chrome.
Company employee Justin Tervay says that the current implementation of FTP code in Chrome does not support encrypted connections. With minimal use of FTP addresses in Chrome and the various FTP client applications available on all platforms, Tervay says "it makes no sense to invest in FTP support."
So the Chromium development team has completely removed support for access to FTP addresses, investing more in secure HTTPS addresses.
The company plans to remove directory listing and downloading via Google Chrome from unencrypted links in accordance with the timetable displayed here (Google doc).
__________________________
- File Explorer: Convert to FTP Client
- CTF unknown protocol from Windows XP risk for all Windows
- MSIX: started to be supported by Windows
- PCLinuxOS 2019.08 friendly for Windows friends
eeee let us cut off access… and the solution is uninstall and back to firefox or anyone else….
If it is to open another browser to download drivers or things I want from pages that have them with ftp link… I would prefer to use a solution to do everything… and not to change from here and there…