You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2013/06/14 13:01:21 UTC
[jira] [Updated] (HTTPCLIENT-1372) Content-Disposition header in
form data does not adhere to RFC6266
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski updated HTTPCLIENT-1372:
------------------------------------------
Component/s: (was: HttpClient)
HttpMime
Fix Version/s: 4.3 Beta3
I believe the latest RFC that amends 2045 is 6532 [1]. I think we should keep RFC 2045 compatibility by default for now but you are very welcome to contribute RFC 6532 compliant mode.
Oleg
[1] http://tools.ietf.org/html/rfc6532
> 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
> Fix For: 4.3 Beta3
>
>
> 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org