[
https://issues.apache.org/jira/browse/VFS-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930158#action_12930158
]
Dmytro Polivenok edited comment on VFS-305 at 11/9/10 10:21 AM:
----------------------------------------------------------------
Faced issue related to invoking commands on files with non UTF encoding
(create, rename, move, etc..) :
Commons-net control buffer readers and writers were initialized with
DEFAULT_CONTROL_ENCODING = "ISO-8859-1" before setting encoding in
FtpClientFactory, so I moved setting control encoding before connect method
which creates _controlInput_,_controlOutput_ in FTP class
patch - VFS-305(commands).patch
was (Author: polivenok):
Faced issue related to invoking commands on files with non UTF encoding
(create, rename, move, etc..) :
Commons-net control buffer readers and writers were initialized with
DEFAULT_CONTROL_ENCODING = "ISO-8859-1" before setting encoding in
FtpClientFactory, so I moved setting control encoding before connect method
which creates _controlInput_,_controlOutput_ in FTP class
> VFS does not support FTP servers with non Latin-1 control encoding
> ------------------------------------------------------------------
>
> Key: VFS-305
> URL: https://issues.apache.org/jira/browse/VFS-305
> Project: Commons VFS
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: Java client talking to Java FTP server (Alfresco)
> Reporter: Tom
> Fix For: 2.0
>
> Attachments: VFS-305(commands).patch, VFS-305.patch
>
>
> It should be possible to set the client.setControlEncoding with a sensible
> value.
> Being able to set that value is a must, but a FTPClient (commons-net) that
> somehow can detect what control encoding is used, would automagically solve a
> lot of issues. FileZilla automatically detects that Alfresco's FTP server is
> doing UTF8.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
