Closed Bug 1138905 Opened 11 years ago Closed 10 years ago

FTP – some servers need CLNT for UTF-8

Categories

(Core Graveyard :: Networking: FTP, defect)

x86_64
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: grawity, Unassigned)

Details

When connecting to FTP servers, Firefox should send CLNT to identify its own version (user-agent) and to deal with broken servers. (Examples from other clients: "CLNT lftp/4.6.1", "CLNT Total Commander (UTF-8)", "CLNT Filezilla".) Gene6 FTP Server v3.10 supports UTF-8 but for unknown reasons insists that CLNT must be sent before "OPTS UTF8 ON". Otherwise the OPTS command is refused. The server lists "CLNT" in FEAT reply. Example log: 220 Gene6 FTP Server v3.10.0 (Build 2) ready... -> USER mantas 331 Password required for mantas. -> PASS hunter2 230 User mantas logged in. -> SYST 215 UNIX Type: L8 -> FEAT 211-Extensions supported: AUTH TLS CCC CLNT CPSV EPRT EPSV MDTM MFCT MFMT MLST type*;size*;create;modify*; MODE Z PASV PBSZ PROT REST STREAM SIZE SSCN TVFS UTF8 XCRC "filename" SP EP XMD5 "filename" SP EP XSHA1 "filename" SP EP 211 End. -> OPTS UTF8 ON 501 Please CLNT first. -> PWD 257 "/" is current directory.
Component: Untriaged → Networking: FTP
Product: Firefox → Core
Version: 36 Branch → unspecified
This seems like something easy for a new contributor, but I want to make sure we're willing to accept changes here. Care to comment?
Flags: needinfo?(mcmanus)
it would be good if we found someone who knew about real-world-ftp to review the fact that it makes sense for everyone. maybe the maintainer of filezilla? (i'd be happy to review the code)
Flags: needinfo?(mcmanus)
Related: identical report in GNOME Gvfs [1], in which the developers are concerned with CLNT being problematic with FTP proxies... [1]: https://bugzilla.gnome.org/show_bug.cgi?id=745520 As an alternative, this ftpd also supports MLSD [2] for structured file lists, and /seems/ to always use UTF-8 with it. MLSD might be easier to parse than LIST, too, but more work to implement than CLNT. (And still has problems with proxies.) [2]: https://tools.ietf.org/html/rfc3659#section-7
We can just ignore errors about CLNT, just like we are doing about "OPTS UTF8 ON". MLSD is more problematic because the transparent proxy actually has to know that MLSD will use a data connection.
sounds like :emk is qualified to review a patch :)
We are in a period where ftp is clearly deprecated and in general, making changes to the code is riskier than letting it ride unless there is a patch and reviewer available to make a good judgment about it. So I'm going to wontfix ftp bugs related to enhancements, interop errors, etc.. We will be better off putting our energy into including a different js based ftp stack.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.