[ 
https://issues.apache.org/jira/browse/WSCOMMONS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wendy Raschke updated WSCOMMONS-510:
------------------------------------

    Attachment: WSCOMMONS-510.patch

> In a SOAP attachment message, the Content-Type header's boundary parameter 
> value must be quoted
> -----------------------------------------------------------------------------------------------
>
>                 Key: WSCOMMONS-510
>                 URL: https://issues.apache.org/jira/browse/WSCOMMONS-510
>             Project: WS-Commons
>          Issue Type: Bug
>          Components: AXIOM
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>         Attachments: WSCOMMONS-510.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> If SOAP Messages with Attachments (SwA) or SOAP Message Transmission 
> Optimization Mechanism (MTOM) is used to send attachments, the Axis2 runtime 
> will send a Content-Type header with a boundary parameter whose value is not 
> quoted. Here is an example:
> This problem was originally opened against AXIS2, AXIS2-4556.  It is moved to 
> Axiom after discovering that the code change will be in Axiom.
> Wendy Raschke will be providing the patch.
> -------------------------
> Content-Type: multipart/related;
> boundary=MIMEBoundaryurn_uuid_9152FA64BB334CBE261257799614016;
> type="application/xop xml";
> start="<0.urn:uuid:[email protected]>";
> start-info="application/soap xml";
> action="http://xmlsoap.org/EchoStringArrayAsBinaryArray";
> In order to be WS-I-compliant, the boundary value should be quoted. In this 
> case, the boundary parameter should appear as
> boundary="MIMEBoundaryurn_uuid_9152FA64BB334CBE261257799614016";
> The WS-I Basic Profile 2.0 Specification, Rule R1109 states, "Parameters on 
> the Content-Type MIME header field-value in a request MESSAGE MUST be a 
> quoted string." 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to