[
https://issues.apache.org/jira/browse/HTTPCLIENT-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537259
]
Ortwin Glück commented on HTTPCLIENT-293:
-----------------------------------------
We should be spec compliant and not "compatible with most" implementations - I
don't care how wrong IE7 implements this. RFC 2183, Section 2.3 clearly states
the limitation to ASCII. People should just accept this limitation instead of
trying to bend the standard to their needs. Standards are made to ensure
interoperability, for $DIETY's sake. If you need to pass a non-ASCII filename,
this is simply not the place for it. You could add another text/plain MIME part
with a well-defined charset and pass the file name there for instance.
> 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
> Affects Versions: 1.0 Alpha
> Environment: Operating System: All
> Platform: All
> Reporter: Eric Dofonsou
> Priority: Minor
> Fix For: 4.0 Final
>
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
