commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Neidhart (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FILEUPLOAD-199) Uploads have unexpected results for files with non-ASCII names - support RFC2047
Date Sun, 10 Mar 2013 11:17:13 GMT

    [ https://issues.apache.org/jira/browse/FILEUPLOAD-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598212#comment-13598212
] 

Thomas Neidhart commented on FILEUPLOAD-199:
--------------------------------------------

javax.mail.internet.MimeUtility.decodeText provides a method to decode text according to RFC
2047.
It is already used in commons-email to encode header values.

It is also part of the tomcat distribution, so we may copy it to fileupload.
                
> Uploads have unexpected results for files with non-ASCII names - support RFC2047
> --------------------------------------------------------------------------------
>
>                 Key: FILEUPLOAD-199
>                 URL: https://issues.apache.org/jira/browse/FILEUPLOAD-199
>             Project: Commons FileUpload
>          Issue Type: Bug
>    Affects Versions: 1.2.2
>            Reporter: Mark Thomas
>
> Uploading a file with a UTF-8 file name results in a garbled file name on the server.
Both the browser and Commons File Upload are at fault in this process.
> The headers for each uploaded part should only use ASCII. Non-ASCII header values - such
as UTF-8 file names - should be encoded as per RFC2047. The browsers are at fault for not
encoding the headers correctly. Commons File Upload is at fault for not handling RFC2047 encoded
header values.

--
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: http://www.atlassian.com/software/jira

Mime
View raw message