Custom Query (8042 matches)
Results (325 - 327 of 8042)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #566 | ASCII file transfers do not work | |||
| Description |
OS of client: windows XP OS of server: HP-UX 11 Filezilla version: 2.2.3 I tried to transfer a file with a txt extension from windows PC to HP-UX server, using transfer type Auto- detect and transfer type ASCII. In both occasions, the file was transferred in binary mode leaving DOS line terminators in the file on the server. |
|||
| #2283 | ASCII file types | |||
| Description |
Add .ini .py (python source code) to the list of files to be transfered in ASCII |
|||
| #1028 | ASCII mode transfer corrupts files nix=>win | |||
| Description |
I have had multiple problems transferring to and from various linux servers from XP with filezilla my current version is 2.2.18. this problem was noted on previous versions as well. I have noted may other seemingly unresolved but closed complaints about this bug. It appears the problem relates to the file being first saved to the server in binary mode, in other words the crlf pair is retained. if you then transfer the file to a windows machine in ascii mode the file becomes corrupted. Filezilla does not account for the crlf pair and adds an extra cr making it crcrlf so in hex 0D 0A Becomes 0D 0D 0A This has been verified. to repeat it upload an ascii win/dos file to a nix server in binary mode then download it in ascii mode open the file in a hex editor not the hex values as above I beleive this is the main source of various complaints about ascii mode transfers resolution:... filezilla should check for crlf not just cr when doing the ascii nix=>win conversion. if there is a crlf pair then leave as is if there is only a lf then add the cr |
|||
