-
Bug
-
Resolution: Done
-
Blocker
-
3.6.1.Final, 3.6.2.Final, 4.0.0.Beta7
-
None
A change was introduced for RESTEASY-2046 to encode non-US-ASCII filenames per RFC 5987, but the fix was incorrect/incomplete.
Also latest RFC for multipart messages inside HTTP is defined in RFC-7578 and there is stated:
- NOTE: The encoding method described in RFC5987, which would add a "filename*" parameter to the Content-Disposition header field, MUST NOT be used.
Commons FileUpload library cannot consume file correctly if filename is like filename*=utf-8''Test%20file.pdf
Therefore, please add into method MultipartFormDataOutput.addFormData(String key, Object entity, MediaType mediaType, String filename) the parameter that will disable filename encoding
- is caused by
-
RESTEASY-1779 Filename encoding is wrong in MultipartFormDataInput with RestEasy and Wildfly 11
- Resolved
- is incorporated by
-
JBEAP-16359 Add the ability to disable Filename encoding in Content-Disposition
- Closed
-
JBEAP-16427 (7.2.z) RESTEASY-2148 - Add the ability to disable Filename encoding in Content-Disposition
- Closed
- is related to
-
RESTEASY-2159 Review multipart provider documentation
- Resolved
-
RESTEASY-2178 Prepare tests for RESTEASY-2148
- Open
- relates to
-
RESTEASY-546 Please provide access to raw undecoded request headers
- Open
-
RESTEASY-1214 WildFly breaks utf-8 encoded strings in Content-Disposition header
- Open