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
Hi,
I am facing a similar issue with MTOM enabled .net service. I am using SOAPUIv4.5.0 free version and enabling MTOM in soapui for a soap1.2 .net service gets me a HTTP 400 bad request from the IIS7.5 server.
A simple java client works fine sending/receiving MTOM messages to/from the service.
I was wondering if the issue mentioned in this topic could be a possible cause. Is the code change mentioned above, in the any of the release yet.
Appreciate any help.
Thanks.
I am facing a similar issue with MTOM enabled .net service. I am using SOAPUIv4.5.0 free version and enabling MTOM in soapui for a soap1.2 .net service gets me a HTTP 400 bad request from the IIS7.5 server.
A simple java client works fine sending/receiving MTOM messages to/from the service.
I was wondering if the issue mentioned in this topic could be a possible cause. Is the code change mentioned above, in the any of the release yet.
Appreciate any help.
Thanks.