#8601 closed Bug report (outdated)
Unable to download ± character
Reported by: | Jodah | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | FileZilla Client |
Keywords: | encoding | Cc: | |
Component version: | Operating system type: | Windows | |
Operating system version: | XP64 |
Description
I get an error every time I try to download the ± character. It is not a foreign language, just something I come across often with technical people. Can you please include support for this?
Thank you. I love this program otherwise.
Below are my details:
FileZilla Client
Version: 3.6.0.2
Build information:
Compiled for: i586-pc-mingw32msvc
Compiled on: x86_64-unknown-linux-gnu
Build date: 2012-11-29
Compiled with: i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2)
Compiler flags: -g -O2 -Wall -g -fexceptions
Linked against:
wxWidgets: 2.8.12
GnuTLS: 3.1.4
SQLite: 3.7.6.2
Operating system:
Name: Windows Server 2003 (build 3790, Service Pack 2)
Version: 5.2
Platform: 64 bit system
Status: Connecting to [deleted]...
Status: Connection established, waiting for welcome message...
Response: 220 (vsFTPd 2.3.4)
Command: USER [deleted]
Response: 331 Please specify the password.
Command: PASS
Response: 230 Login successful.
Command: SYST
Response: 215 UNIX Type: L8
Command: FEAT
Response: 211-Features:
Response: EPRT
Response: EPSV
Response: MDTM
Response: PASV
Response: REST STREAM
Response: SIZE
Response: TVFS
Response: UTF8
Response: 211 End
Command: OPTS UTF8 ON
Response: 200 Always in UTF8 mode.
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "/"
Command: TYPE I
Response: 200 Switching to Binary mode.
Command: PASV
Response: 227 Entering Passive Mode ([deleted])
Command: LIST
Response: 150 Here comes the directory listing.
Response: 226 Directory send OK.
Status: Invalid character sequence received, disabling UTF-8. Select UTF-8 option in site manager to force UTF-8.
Status: Calculating timezone offset of server...
Command: MDTM 524120092A5034A17±pg04.dwg
Response: 213 20130408195423
Status: Timezone offsets: Server: 0 seconds. Local: -25200 seconds. Difference: -25200 seconds.
Status: Directory listing successful
Status: Connecting to [deleted]...
Status: Connection established, waiting for welcome message...
Response: 220 (vsFTPd 2.3.4)
Command: USER [deleted]
Response: 331 Please specify the password.
Command: PASS
Response: 230 Login successful.
Command: OPTS UTF8 ON
Response: 200 Always in UTF8 mode.
Status: Connected
Status: Starting download of /524120092A5034A17±pg04.dwg
Command: CWD /
Response: 250 Directory successfully changed.
Command: PWD
Response: 257 "/"
Command: TYPE I
Response: 200 Switching to Binary mode.
Command: PASV
Response: 227 Entering Passive Mode ([deleted])
Command: RETR 524120092A5034A17±pg04.dwg
Response: 550 Failed to open file.
Error: Critical file transfer error
Status: Disconnected from server
Change History (2)
comment:1 by , 12 years ago
Keywords: | encoding added |
---|---|
Status: | new → moreinfo |
comment:2 by , 12 years ago
Resolution: | → outdated |
---|---|
Status: | moreinfo → closed |
No reply for more than 28 days.
The interesting parts are:
Control Connection
Command: OPTS UTF8 ON
Response: 200 Always in UTF8 mode.
Status: Invalid character sequence received, disabling UTF-8. Select UTF-8 option in site manager to force UTF-8.
Command: MDTM 524120092A5034A17±pg04.dwg
Response: 213 20130408195423
Data Connection
Command: OPTS UTF8 ON
Response: 200 Always in UTF8 mode.
Command: RETR 524120092A5034A17±pg04.dwg
Response: 550 Failed to open file.
So to put it in easy words: The FTP server supports UTF-8. The FTP server claims to always use UTF-8. Still FileZilla detected an invalid UTF-8 byte sequence when receiving the directory listing. FileZilla asks for the last modification date of file and gets a server response. FileZilla later on tries to download that file, but the server claims it cannot open the file.
1) What are the file permissions? Is the logged in user allowed to open/read that file?
2) Is the file name valid UTF-8 or was it created using a non-UTF-8 aware client? (And the FTP server erroneously accepted the given file name byte-sequence?)