[
https://issues.apache.org/jira/browse/HTTPCLIENT-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186245#comment-16186245
]
ASF GitHub Bot commented on HTTPCLIENT-293:
-------------------------------------------
Github user sermojohn commented on the issue:
https://github.com/apache/httpcomponents-client/pull/85
@ok2c pushed the suggested changes. Thank you for the feedback.
Removed both FormBodyPartBuilder.encodeForHeader and the corresponding unit
test, as I did not find anywhere in the spec this encoding rule.
Fyi, I could not build the 4.6.x branch with java 1.6 version, as it is
reported by animal-sniffer-maven-plugin that undefined references are used
(AuthSchemeRegistry.java:127, SchemeRegistry.java:151,
CookieSpecRegistry.java:139). It worked when I switched to java 1.8 source
compilation and target.
> 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]
