MTOM and soap 1.2 .net service -> Bad Request
I'm trying to invoke a .net web service with soap 1.2, WS-A and MTOM using SoapUI 3.5.1 and 3.6 open source, but the answer is always 400 - Bad Request. Looking at the exception thrown, .net is com...
Forum Discussion
This is still broken in soapUI 4.6.0. In addition to the Content-Type of the SOAP part being messed up (the action embedded inside the type quotes), the line endings are just LF in Fiddler's hex view inspector. This is not valid MIME. Line endings should always be CRLF. In my scenario, I fixed the Content-Type in Fiddler, but WCF still couldn't parse the MTOM encoded response from soapUI. I'm assuming its because of the line ending issue I'm seeing.