Opened 10 years ago

Closed 10 years ago

Last modified 9 years ago

#5486 closed Bug report (rejected)

Problem with Ascii download

Reported by: odys Owned by:
Priority: high Component: FileZilla Client
Keywords: CR Cc:
Component version: Operating system type: Windows
Operating system version: 7 x64

Description

Hi,
I use "ftpes" to download files from a webserver, mostly php,css files.
I noticed a strange behavior.

In some files, when using ASCII or Auto transfer mode, extra CR(carriage return) characters are added at the end of each line, causing a [CR][CR][LF] instead of [CR][LF].

If I download the file directly from the server is fine (not using filezilla)

Haven't found replication steps yet, but has happened to me several times.

Viewer: Notepad++ 5.6.8 unicode
Log and screenshots attached

Attachments (3)

filezilla-client-bug-log.txt (5.6 KB ) - added by odys 10 years ago.
Log file, mode Debug.
filezilla-client-bug-corrupted-file.png (68.8 KB ) - added by odys 10 years ago.
Corrupted file, as viewd using notepad++. Original file is ANSI
filezilla-client-bug-normal-file.png (114.1 KB ) - added by odys 10 years ago.
Normal file, as viewd using notepad++. Original file is ANSI

Download all attachments as: .zip

Change History (6)

by odys, 10 years ago

Log file, mode Debug.

by odys, 10 years ago

Corrupted file, as viewd using notepad++. Original file is ANSI

by odys, 10 years ago

Normal file, as viewd using notepad++. Original file is ANSI

comment:1 by odys, 10 years ago

I would also like to point out that the server is unix based.
Probably filezilla does something wrong there.
Windows based ascii has a new line as: [CR][LF]
Unix based ascii has a new line as: [LF]

In this case, the result of moving a Windows based Ascii file from a Unix based environment to e Windows based, converts the [CR][LF] to [CR][CR][LF]
and according to #3830 (forgot to mention here),
if I move the [CR][LF] file up, it will become [LF] only. Thus, it'll be different and read as one-line from most windows based viewers.

I believe this is the behavior of filezilla. It should not check whether the other system is unix/windows based, and just transfer the file as is.
Correct me if I am wrong

comment:2 by Tim Kosse, 10 years ago

Resolution: rejected
Status: newclosed

comment:3 by indigo, 9 years ago

For anyone like me who experiences newline issues and finds this, I've posted a working theory as to what's going on in the another thread:

#3830

If you experience this problem, set the data type to "binary" and try again.

Note: See TracTickets for help on using tickets.