commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benoit Maisonny (JIRA)" <>
Subject [jira] Commented: (VFS-302) FTP Filename Encoding
Date Wed, 13 Oct 2010 15:50:34 GMT


Benoit Maisonny commented on VFS-302:

I like Nikos' solution: it's simple and to the point. In case people want more control, however,
a more involved solution would be to allow configuration of the client via org.apache.commons.vfs.provider.ftp.FtpFileSystemConfigBuilder.
This is how VFS users can externally configure other properties such as timeout. FtpFileSystemConfigBuilder
would then need new getter/setter for "controlEncoding".

Please consider either solution in a future release. The current situation makes VFS unusable
outside US-ASCII-encoded file names, even though the underlying FTP library supports it.

> FTP Filename Encoding
> ---------------------
>                 Key: VFS-302
>                 URL:
>             Project: Commons VFS
>          Issue Type: Bug
>    Affects Versions: 1.1
>         Environment: Linux, vsftpd
>            Reporter: Oliver Tupran
>         Attachments:
> I tried to copy a file like "m√ľnchen.jpeg" using VFS to a remote ftp server, which resulted
in a wrong encoded filename on the server.
> See also a similar issue from the commons-fileupload project:
> Forgive my newbieness on VFS, but I would really appreciate a solution.
> I tried something that worked, but it really seems like a dirty trick:
> String encodedFilename = new String(filename.getBytes(), "ISO-8859-1");

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message