Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Mon, 11 Mar 2013 14:45:16 +0000 (UTC)
From: "Simone Tripodi (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12514893.1311248975851.418637.1363013116745@arcas>
In-Reply-To: <JIRA.12514893.1311248975851@arcas>
References: <JIRA.12514893.1311248975851@arcas>
Subject: [jira] [Updated] (FILEUPLOAD-199) Uploads have unexpected results
 for files with non-ASCII names - support RFC2047
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/FILEUPLOAD-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simone Tripodi updated FILEUPLOAD-199:
--------------------------------------

    Issue Type: Improvement  (was: Bug)
    
> 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: Improvement
>    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