Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Date: Wed, 19 Jun 2013 21:28:20 +0000 (UTC)
From: "Karl Wright (JIRA)" <jira@apache.org>
To: dev@hc.apache.org
Message-ID: <JIRA.12652840.1371201345504.143635.1371677300077@arcas>
In-Reply-To: <JIRA.12652840.1371201345504@arcas>
References: <JIRA.12652840.1371201345504@arcas>
Subject: [jira] [Commented] (HTTPCLIENT-1372) Content-Disposition header in
 form data does not adhere to RFC6266
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688481#comment-13688481 ] 

Karl Wright commented on HTTPCLIENT-1372:
-----------------------------------------

Almost done with rearranging things.  The only thing I find to be a bridge too far is folding HttpMultipartFactory into MultipartEntityBuilder.  The reason is that for backwards compatibility the MultipartEntity class needs to continue to have constructors that take the mode, and thus we'd wind up with MultipartEntityBuilder calling MultipartEntity which calls right back into MultipartEntityBuilder - which would be convoluted and too weird for me. ;-)

                
> 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org