tarantoga
unread,Jan 24, 2011, 8:10:00 AM1/24/11Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to AndreasLiebig
Hello Andreas,
on my Windows Vista Laptop I use Windows Explorer for FTP, which works
fine - most of the time. But there seems to be a problem when
connected to FTPServer: non-ASCII chars are not displayed correctly,
e.g. "Björk" shows up as "Björk". I tried connecting to my Linux-FTP-
server and Windows Explorer displays the non-ASCII chars correctly.
I did some packet sniffing with Wireshark to find out, what's wrong. I
could see, that Explorer sends:
opts utf8 on
FTPserver answers:
501 OPTS command utf8 on not supported
I think this is the reason, why Explorer thinks that FTPServer uses
ASCII only.
Next I did some tests using netcat:
$ nc galaxy 2121
220 aFTPServer ready (cwd is /)
USER andi
331 - Login as andi OK. Send password
PASS *****
230 - Password accepted
opts utf8 on
501 OPTS command utf8 on not supported
OPTS UTF8 ON
200 OPTS command UTF8 ON understood
I think this is part of a more general problem (more netcat tests):
pwd
500 pwd not understood
PWD
257 "/"
list
500 list not understood
LIST
150 Directory listing for /mnt/sdcard
226 Directory send OK
According to RFC 959 this is not the expected behaviour:
[RFC 959, page 45, chapter 5.3 "COMMANDS]
...
The commands begin with a command code followed by an argument
field. The command codes are four or fewer alphabetic characters.
Upper and lower case alphabetic characters are to be treated
identically. Thus, any of the following may represent the
retrieve command:
RETR Retr retr ReTr rETr
This also applies to any symbols representing parameter values,
such as A or a for ASCII TYPE.
...
tarantoga