Rewriting content-type for MTOM requests with a Web Service Proxy
I recently had an issue trying to proxy the content-type for an MTOM with SOAP 1.2 request through a web service proxy. All the typical tricks as outlined here didn't work: https://developer.ibm.com/answers/questions/177137/how-to-proxy-soap-mtom-using-ibm-datapower-gateway.html
Was seeing original Content-Type sent by source: multipart/related; boundary="----=_Boundary";start-info="application/soap+xml"; type="application/xop+xml";start=""; action=""
Content-Type sent to backend: multipart/related;boundary="----=_Boundary";start-info="application/soap+xml"; type="text/xml";start=""; action=""
Check the WSDL the web service proxy is based on to see what version of SOAP it declares. In my use case the WSDL was using the SOAP 1.1 namespace and as a result DataPower was trying to send a SOAP 1.1 message to the backend even if we accept a SOAP 1.2. message on the front. To get the configuration up and running, I edited the WSDL, to declare
the SOAP 1.2 namespace instead of SOAP 1.1.