[
https://issues.apache.org/jira/browse/HTTPCLIENT-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829662#action_12829662
]
Peter Klotz commented on HTTPCLIENT-317:
----------------------------------------
It would be fixed in HttpMime, could you please explain how?
Because if I even look into HttpMime 4.1 alpha2 in trunk
there is nothing that generates the Content-ID header in the parts with
HttpMultipartMode.STRICT only Content-Type, Content-Disposition and
Content-Transfer-Encoding. But Content-ID is NEEDED e.g. in Servicemix as
target.
so the above mentioned problem is still open in the latest version but the
workaround only would work in 3.1 (legacy)
> HTTP Client doesn't support multipart/related content-type
> ----------------------------------------------------------
>
> Key: HTTPCLIENT-317
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-317
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpMime
> Affects Versions: 2.0 Final
> Environment: Operating System: Windows XP
> Platform: PC
> Reporter: peter
> Priority: Minor
> Fix For: 4.0 Beta 2
>
>
> It is not possible to sent data easely as a multipart/related content-type
> (as
> discribed in rfc 2387) using Http Client.
--
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]
