[
https://issues.apache.org/jira/browse/AXIS2-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maks resolved AXIS2-3649.
-------------------------
Resolution: Fixed
> Worng Content-Type HTTP header when sending MTOM (incompatible with JBossWS)
> ----------------------------------------------------------------------------
>
> Key: AXIS2-3649
> URL: https://issues.apache.org/jira/browse/AXIS2-3649
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Maks
> Original Estimate: 0.25h
> Remaining Estimate: 0.25h
>
> According to http://ws.apache.org/axis2/1_2/mtom-guide.html, the Content-Type
> should have the following form:
> Content-Type: multipart/related; boundary=MIMEBoundary4A7AE55984E7438034;
> type="application/xop+xml"; start="<[EMAIL
> PROTECTED]>";
> start-info="text/xml; charset=utf-8"
> The current Axis2 version sends start="[EMAIL PROTECTED]", without angle
> brackets. This gets incompatibility with JBossWS, which expects angle
> brackets.
> JBossWS reports error for such Content-Type:
> multipart/related stream invalid, no root part was found
> The other implementations: JBossWS, JAXWS-RI and .NET do include angle
> brackets for start value in Content-Type - that's why I think it is correct
> behaviour to include them.
--
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]
