wsalembi
14 years agoOccasional Contributor
MTOM encoding bug
The enforce MTOM functionality in SoapUI 4.0 is incorrect. SoapUI does not decode the base64 content inside the MIME part. It just copies its value.
For example: dGVzdA== is the base64 representation of the string "test"
<soapenv:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="id-6">
<v1:MtomSecuredMessageRequest>
<BinaryContent>dGVzdA==</BinaryContent>
</v1:MtomSecuredMessageRequest>
</soapenv:Body>
So when MTOM is enforced, the MIME PART must contain the string "test" (base64 decoded).
SoapUI sends the following MIME part:
------=_Part_9_24755476.1316518486428
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-ID: <http://www.soapui.org/92398823628422>
dGVzdA==
------=_Part_9_24755476.1316518486428--
The MIME part has the same base64 string. So the transmission is not optimized.
Can your please confirm this and fix ASAP?
For example: dGVzdA== is the base64 representation of the string "test"
<soapenv:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="id-6">
<v1:MtomSecuredMessageRequest>
<BinaryContent>dGVzdA==</BinaryContent>
</v1:MtomSecuredMessageRequest>
</soapenv:Body>
So when MTOM is enforced, the MIME PART must contain the string "test" (base64 decoded).
SoapUI sends the following MIME part:
------=_Part_9_24755476.1316518486428
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-ID: <http://www.soapui.org/92398823628422>
dGVzdA==
------=_Part_9_24755476.1316518486428--
The MIME part has the same base64 string. So the transmission is not optimized.
Can your please confirm this and fix ASAP?