commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <>
Subject [jira] [Resolved] (VFS-494) [SFTP] No support for SFTP servers with non Latin-1 file name encoding
Date Mon, 23 Sep 2013 18:17:02 GMT


Gary Gregory resolved VFS-494.

       Resolution: Fixed
    Fix Version/s: 2.1
         Assignee: Gary Gregory

commit -m "[VFS-494][SFTP] No support for SFTP servers with non Latin-1 file name encoding.
The provided patch did not apply cleanly, this version should be equivalent." C:/vcs/svn/apache/commons/trunks-proper/vfs/core/src/main/java/org/apache/commons/vfs2/provider/sftp/
C:/vcs/svn/apache/commons/trunks-proper/vfs/src/changes/changes.xml C:/vcs/svn/apache/commons/trunks-proper/vfs/core/src/main/java/org/apache/commons/vfs2/
    Sending        C:/vcs/svn/apache/commons/trunks-proper/vfs/core/src/main/java/org/apache/commons/vfs2/
    Sending        C:/vcs/svn/apache/commons/trunks-proper/vfs/core/src/main/java/org/apache/commons/vfs2/provider/sftp/
    Sending        C:/vcs/svn/apache/commons/trunks-proper/vfs/core/src/main/java/org/apache/commons/vfs2/provider/sftp/
    Sending        C:/vcs/svn/apache/commons/trunks-proper/vfs/src/changes/changes.xml
    Transmitting file data ...
    Committed revision 1525663.

> [SFTP] No support for SFTP servers with non Latin-1 file name encoding
> ----------------------------------------------------------------------
>                 Key: VFS-494
>                 URL:
>             Project: Commons VFS
>          Issue Type: Bug
>    Affects Versions: 2.0
>         Environment: Windows 7/Suse 11
>            Reporter: Allen Xudong Cheng
>            Assignee: Gary Gregory
>              Labels: encoding, patch, sftp
>             Fix For: 2.1
>         Attachments: not-setfilenameencoding-bug.patch
> Jsch provide a method to set file name encoding, but VFS have not provide this configuration.
When the SFTP server have some file with non-UTF-8 encoding, will cause access failed

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message