[
https://issues.apache.org/jira/browse/HTTPCLIENT-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687739#comment-13687739
]
Karl Wright edited comment on HTTPCLIENT-1372 at 6/19/13 10:21 AM:
-------------------------------------------------------------------
This patch represents a refactoring with no functional changes which is more
conducive to having three (or more) operational modes of form encoding. Oleg,
do you have any objections if this is committed, once the tests pass? Or would
you prefer a different structure?
was (Author: [email protected]):
This patch represents a refactoring with no functional changes which is
more conducive to having three (or more) operational modes of form encoding.
Oleg, do you have any objections if this is committed? Or would you prefer a
different structure?
> Content-Disposition header in form data does not adhere to RFC6266
> ------------------------------------------------------------------
>
> Key: HTTPCLIENT-1372
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1372
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpMime
> Affects Versions: 4.2.5
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: 4.3 Beta3
>
> Attachments: HTTPCLIENT-1372.patch
>
>
> The Content-disposition header, as it appears for an item of form data, does
> not allow for UTF-8 encoding as specified in RFC6266, as described here:
> http://tools.ietf.org/html/rfc6266
> This is causing ManifoldCF severe problems working in Japan with Solr, since
> Solr content extraction relies on accurate filenames in order to determine
> the likely document encoding.
> A fix for the 4.2.x branch will be needed, I am afraid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
