#5060 closed defect (thirdparty)
connection read timeout while using utf-8 encoding
Reported by: | josephyen | Owned by: | dkocher |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ftp | Version: | 3.5.1 |
Severity: | normal | Keywords: | |
Cc: | Architecture: | Intel | |
Platform: | Mac OS X 10.6 |
Description
connection failed when my connection text encoding is UTF-8. but all other encodings works fine.
maybe caused by rfc2640 ??
transcript
220 ProFTPD 1.3.3a Server (OVID) [::ffff:61.62.238.36] USER ftpadmin 331 �ݭn�� ftpadmin ���ѱK�X PASS ******** 230 �ϥΪ� ftpadmin �n�J FEAT 211-Features: MDTM MFMT TVFS MFF modify;UNIX.group;UNIX.mode; MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.mode*;UNIX.owner*; REST STREAM LANG en-US;zh-TW* SIZE
Change History (3)
comment:1 follow-up: ↓ 2 Changed on Jul 20, 2010 at 7:52:46 PM by dkocher
comment:2 in reply to: ↑ 1 Changed on Jul 20, 2010 at 7:53:41 PM by dkocher
Replying to dkocher:
We do send OPTS UTF8 ON if the server lists UTF8 in the FEAT response.
If negogiation fails, you should see Failed to negogiate UTF-8 charset: in the system log (open Console.app).
comment:3 Changed on Jul 22, 2010 at 4:40:28 PM by dkocher
- Resolution set to thirdparty
- Status changed from new to closed
I suppose this is a server issue.
Note: See
TracTickets for help on using
tickets.
We do send OPTS UTF8 ON if the server lists UTF8 in the FEAT response.