commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaime Hablutzel (JIRA)" <>
Subject [jira] [Commented] (FILEUPLOAD-199) Uploads have unexpected results for files with non-ASCII names - support RFC2047
Date Tue, 12 Mar 2013 16:11:16 GMT


Jaime Hablutzel commented on FILEUPLOAD-199:

Just to mention a couple of things, first rfc1867 which commons fileupload claims to implement
in the home page has a method for encoding not US ASCII (rfc1522) but this one is obsoleted
by rfc2047, the spec you are implementing here, so maybe a clarification of this would be
useful in the commons fileupload home page.

Second, browsers are still sending raw UTF-8 or whatever for 'filename' parameter (at least
chrome and firefox) . So I think commons fileupload implementation should be compatible with
that out-of-standards behaviour from browsers and accept the right RFC2047 encoding at the
same time. This is to "be liberal in what you accept from others." 

> Uploads have unexpected results for files with non-ASCII names - support RFC2047
> --------------------------------------------------------------------------------
>                 Key: FILEUPLOAD-199
>                 URL:
>             Project: Commons FileUpload
>          Issue Type: Bug
>    Affects Versions: 1.2.2
>            Reporter: Mark Thomas
>            Assignee: Simone Tripodi
>             Fix For: 1.3
> 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:

View raw message