commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simone Tripodi (JIRA)" <>
Subject [jira] [Updated] (FILEUPLOAD-206) Encoding of parts incorrectly determined and assumed to be
Date Thu, 07 Mar 2013 08:42:13 GMT


Simone Tripodi updated FILEUPLOAD-206:

    Fix Version/s:     (was: 1.3)
> Encoding of parts incorrectly determined and assumed to be
> ----------------------------------------------------------
>                 Key: FILEUPLOAD-206
>                 URL:
>             Project: Commons FileUpload
>          Issue Type: Bug
>    Affects Versions: 1.2.2
>            Reporter: Holger Sunke
> When submitting user input form fields with a form having enctype="multipart/form-data",
FileUpload assumes "ISO-8...-1" to be the default encoding for each part, not taking into
account that request.getContentEncoding() returns "UTF-8".
> The description of FILEUPLOAD-101 states: "Each individual part in the 'multipart/form-data'
encoded requests may have its own content type definition."
> In my opinion, this assumption is wrong, as the the multipart/form-data encoding algorithm
tells the right opposite regarding non file form fields:
> "... The parts of the generated multipart/form-data resource that correspond to non-file
fields must not have a Content-Type header specified. Their names and values must be encoded
using the character encoding selected above (field names in particular do not get converted
to a 7-bit safe encoding as suggested in RFC 2388)..."
> See:
> So for now as user of FileUpload, i don't see a way to tell FileUpload that my FormFields
are UTF-8 encoded, resulting in corrupted user input.
> Even request.setContentEncoding("UTF-8"); does not help, neither <form ... accept-charset="UTF-8"
...> does.

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