4 ms·
Insecure? Bullshit. They should remove http then. I'd respect them if they just said they're lazy and don't want to support the ftp protocol.
by throw7 7y ago
Insecure? Bullshit. They should remove http then. I'd respect them if they just said they're lazy and don't want to support the ftp protocol.
- Someone1234 7y ago> They should remove http then. They're working on it. It has and will continue to be deprecated with ever increasing security warnings. But the reason why FTP got pulled and HTTP hasn't is simply usage. The FTP client in browsers is terrible, and anyone using FTP professionally is using a better client (e.g. multiple connection modes, resume downloads, concurrent streams, etc) or has already migrated to FTPS or SFTP. FTP just adds attack surface and maintenance cost.
- wolco 7y agoYou probably don't realize many links you click are ftp links that will now be broken for you.
- Someone1234 7y agoI'd realize immediately since those links would be broken. I have had: network.ftp.enabled: false set since it was introduced in Firefox 60 (over a year ago). I've had a total of one link broken in that time.
- untog 7y agoThe great thing is we don’t need to guess about this! Firefox and Chrome have user telemetry showing that FTP is barely ever used.
- throw7 7y agoSo why aren't you arguing that firefox support migration to ftps or sftp?
- Someone1234 7y agoI did in fact state exactly why: > The FTP client in browsers is terrible, and anyone using FTP professionally is using a better client (e.g. multiple connection modes, resume downloads, concurrent streams, etc) That would be just as true for SFTP or FTPS. Those mitigate the security problems, but don't address the fact that FTP-like protocols would continue to be a second class citizen in browsers and better handled by bespoke clients.