[
https://issues.apache.org/jira/browse/HTTPCLIENT-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688983#comment-13688983
]
Oleg Kalnichevski commented on HTTPCLIENT-1372:
-----------------------------------------------
> One other quick point: the test "testMultipartFormBrowserCompatible" actually
> uses STRICT mode.
> Without it, there are no Content-Transfer-Encoding headers generated. Was
> this test behavior intentional?
Most likely not.
Oleg
> 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, 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]
