Opened 14 years ago

Closed 8 years ago

Last modified 6 years ago

#5641 closed Feature request (wontfix)

windows explorer cannot upload some files with special name — at Version 6

Reported by: Lu Wei Owned by:
Priority: high Component: FileZilla Server
Keywords: explorer Cc:
Component version: Operating system type: Windows
Operating system version: XPSP3

Description (last modified by Tim Kosse)

Uploading file "306待产包.jpg" to filezilla server fails with windows explorer, but successes with filezilla client. Not all chinese named files fails, but occurs rather frequently. Seems a character handling related bug.

the full error log:

(000019)2010-10-19 12:54:08 - (not logged in) (127.0.0.1)> Connected, sending welcome message...
(000019)2010-10-19 12:54:08 - (not logged in) (127.0.0.1)> 220 FileZilla Server version 0.9.37 beta written by Tim Kosse (Tim.Kosse@…) Please visit http://sourceforge.
(000019)2010-10-19 12:54:08 - (not logged in) (127.0.0.1)> USER me
(000019)2010-10-19 12:54:08 - (not logged in) (127.0.0.1)> 331 Password required for me
(000019)2010-10-19 12:54:08 - (not logged in) (127.0.0.1)> PASS
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> 230 Logged on
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> opts utf8 on
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> 200 UTF8 mode enabled
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> PWD
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> 257 "/" is current directory.
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> CWD /incoming/
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> 250 CWD successful. "/incoming" is current directory.
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> noop
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> 200 OK
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> CWD /incoming/
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> 250 CWD successful. "/incoming" is current directory.
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> TYPE A
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> 200 Type set to A
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> PASV
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> 227 Entering Passive Mode (127,0,0,1,6,66)
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> LIST
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> 150 Connection accepted
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> 226 Transfer OK
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> noop
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> 200 OK
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> CWD /incoming/
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> 250 CWD successful. "/incoming" is current directory.
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> TYPE I
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> 200 Type set to I
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> PASV
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> 227 Entering Passive Mode (127,0,0,1,6,68)
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> STOR 306待产?jpg
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> 150 Connection accepted
(000019)2010-10-19 12:54:08 - me (127.0.0.1)> 550 can't access file.

Change History (4)

comment:3 by Lu Wei, 10 years ago

I have no virus scanner installed.
I suggest that it relates to character set handling. Maybe file explorer or filezilla is not good at UTF8 transforming and send filezilla server something that can not be understood. The bug starts at "STOR 306待产?jpg" command. Specifically, at the character 包,which displays as a question mark in the log.

comment:4 by Tim Kosse, 9 years ago

Status: newmoreinfo

Do you also experience this issue if using a dedicated FTP client? Explorer has a notoriously bad FTP implementation.

in reply to:  4 comment:5 by Lu Wei, 9 years ago

Status: moreinfonew

I do not have other dedicated FTP client; There are so many Windows machine that have not any dedicated FTP client at all, and I have to use Explorer to access the FTP server.

comment:6 by Tim Kosse, 8 years ago

Description: modified (diff)
Resolution: worksforme
Status: newclosed

包 is a character outside the basic multilingual plane. Older Windows versions cannot handle characters in the supplementary planes correctly. Solution is to update to a more recent Windows version, e.g. Windows 7

Note: See TracTickets for help on using tickets.