Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

connection read timeout while using utf-8 encoding #5060

Closed
cyberduck opened this issue Jul 20, 2010 · 3 comments
Closed

connection read timeout while using utf-8 encoding #5060

cyberduck opened this issue Jul 20, 2010 · 3 comments
Assignees
@dkocher
Labels
bug ftp FTP Protocol Implementation thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

c60b213 created the issue

connection failed when my connection text encoding is UTF-8. but all other encodings works fine.

maybe caused by rfc2640 ??

external image

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
@cyberduck
Copy link
Collaborator Author

@dkocher commented

We do send OPTS UTF8 ON if the server lists UTF8 in the FEAT response.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:1 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).

@cyberduck
Copy link
Collaborator Author

@dkocher commented

I suppose this is a server issue.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
bug ftp FTP Protocol Implementation thirdparty Issue caused by third party
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dkocher @cyberduck