[
https://issues.apache.org/jira/browse/HTTPCLIENT-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178410#comment-16178410
]
Ioannis Sermetziadis commented on HTTPCLIENT-293:
-------------------------------------------------
I believe that the HttpClient should implement RFC2231 by using asterisks (*)
to support use of header parameter values in character sets other than
US-ASCII, like in the Content-Disposition header.
So, when a file is uploaded using MultipartEntity, the FormBodyPart should
include a Content-Disposition header that follows the specification, in order
to correctly encode the file name, in case it uses a character set other than
US-ASCII.
An example of such a header is:
Content-Disposition=form-data; name=file; filename*=utf-8''test
If you agree, I could submit a patch on this.
> Provide support for non-ASCII charsets in the multipart disposition-content
> header
> ----------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-293
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-293
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient (classic)
> Affects Versions: 1.0 Alpha
> Environment: Operating System: All
> Platform: All
> Reporter: Eric Dofonsou
> Priority: Minor
> Fix For: 4.0 Beta 2
>
>
> Because of the the following line in getAsciiBytes
> data.getBytes("US-ASCII");
> The returned string is modified if has Latin Characters.
> Ex : Document non-controlé -> Document non-control?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
