Ticket #204 (closed enhancement: wontfix)

Opened 8 years ago

Last modified 8 years ago

ASCII vs BINARY transfer

Reported by: anonymous Owned by: alamaison
Priority: minor (e.g. uncommon, cosmetic, has workaround) Milestone: 0.9.x Bug sprint
Component: backend Version: 0.7.0
Keywords: Cc:


Files are always transfered as binary. If there are textfiles (for example scripts) they should transfered as ASCII cause of the Linefeed problems between Windows and UNIX

Change History

comment:1 Changed 8 years ago by alamaison

  • Priority changed from critical (affects core workflow) to minor (e.g. uncommon, cosmetic, has workaround)
  • Status changed from new to closed
  • Resolution set to wontfix
  • Type changed from defect to enhancement

ASCII mode is a historical feature of the FTP protocol (FTP) when back in ancient times, files being transferred might have been in wildly different formats, e.g.  fixed length records vs streams of characters.

SFTP version 3 (the version implemented by most servers) has no such concept. It makes no sense nowadays. The idea that a file transfer protocol may or may not mutate the contents of your files is downright scary! More to the point, it doesn't even work. Most OSses use Unicode nowadays which ASCII mode would cheerfully corrupt.

If you need to convert line endings, do it properly, reliably, yourself using the correct tool. In other words, either save your file with the correct line endings (an option in many text editors) or use the unix2dos/dos2unix tools to convert them afterwards.

Note: See TracTickets for help on using tickets.