Forum Discussion
vaibhav8783
16 years agoNew Contributor
Hi,
I am using SoapUI Pro 3.0.1 and facing a similar issue.
My Scenario: Send soap request which is MTOM enabled with WS-Security for Signature and Encryption.
When I send the MTOM enabled request with WS-Security for Encryption, then following soap fault is received in the soap response:-
MTOM Attachments Processing Failed: Cannot de-serialize the input MIME Stream; value of the 'type' parameter of the 'Content-Type' header of the MIME message is not equal to 'application/xop+xml'
On debugging, I found that the soap request that is sent by SoapUI contains the Content-Type as "application/soap+xml"
This content Type should have been "application/xop+xml" for MTOM enabled soap request.
Please refer to the below excerpts from the request sent bu SoapUI: -
------=_Part_41_25519477.1262942422094
Content-Type: application/soap+xml; charset=UTF-8
Content-Transfer-Encoding: 8bit
Content-ID:
Please provide your feedback on this issue.
Thanks,
Vaibhav
I am using SoapUI Pro 3.0.1 and facing a similar issue.
My Scenario: Send soap request which is MTOM enabled with WS-Security for Signature and Encryption.
When I send the MTOM enabled request with WS-Security for Encryption, then following soap fault is received in the soap response:-
On debugging, I found that the soap request that is sent by SoapUI contains the Content-Type as "application/soap+xml"
This content Type should have been "application/xop+xml" for MTOM enabled soap request.
Please refer to the below excerpts from the request sent bu SoapUI: -
------=_Part_41_25519477.1262942422094
Content-Type: application/soap+xml; charset=UTF-8
Content-Transfer-Encoding: 8bit
Content-ID:
Please provide your feedback on this issue.
Thanks,
Vaibhav