[
https://issues.apache.org/jira/browse/HTTPCLIENT-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179864#comment-16179864
]
Oleg Kalnichevski commented on HTTPCLIENT-293:
----------------------------------------------
bq. For example, it is not clear to me which specifications the
browser_compatible mode follows.
There is no specification to speak of. It just represents an attempt at
simulating the behavior of commons browsers.
bq. Also, should the HttpClient be backwards compatible with the currently
defined modes
Depends on what branch you decide to contribute to. It is certainly the case
for 4.5.x but we can be more flexible in 5.x.
Oleg
> 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]
