[tahoe-dev] [tahoe-lafs] #680: Fix for mutable files with FTP

tahoe-lafs trac at allmydata.org
Sat Oct 31 23:08:46 PDT 2009


#680: Fix for mutable files with FTP
---------------------------+------------------------------------------------
 Reporter:  frozenfire     |           Owner:  warner  
     Type:  defect         |          Status:  assigned
 Priority:  major          |       Milestone:  1.6.0   
Component:  code-frontend  |         Version:  1.3.0   
 Keywords:                 |   Launchpad_bug:          
---------------------------+------------------------------------------------

Comment(by davidsarah):

 FTP is a horrible protocol, and grokking its specification (RFC 959) is
 not helped by the fact that it has never been streamlined and updated for
 a world where bytes are always 8 bits and files are flat.

 In any case, the relevant part of RFC 959 seems to be section 3.4, which
 says

 > The following transmission modes are defined in FTP:

 > 3.4.1.  STREAM MODE

 > If the structure is a file structure, the EOF is indicated by the
 sending host closing the data connection and all bytes are data bytes.

 It is very unlikely that the FTP server library is using anything other
 than STREAM transmission mode with a file structure (
 http://cr.yp.to/ftp/type.html says the other options are all obsolete). If
 so, then the tested clients are nonconformant in treating anything other
 than a close of the data connection as end-of-file.
 http://cr.yp.to/ftp/browsing.html seems to suggest that browser ftp
 clients do actually look for connection close to signal EOF -- so I'm
 stumped.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/680#comment:7>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid


More information about the tahoe-dev mailing list