bsheward
New Contributor
Joined 15 years ago
User Profile
User Widgets
Contributions
SOAP 1.2 .Net WCF Service expecting text/xml content?
Hi, I have imported a WSDL file from a .Net WCF web service. If I right-click on the entry within soapUI 3.6 and select "Show Interface Viewer", I can clearly see SOAP Version: SOAP 1.2. If I open a request against that service, and view the raw output, I see: POST http://... HTTP/1.1 Accept-Encoding: gzip, deflate Content-Type: application/soap+xml; charset=UTF-8; action="http://tempuri.org/..." However, if I run the request and check the raw response, I see: HTTP/1.1 415 Cannot process the message because the content type 'application/soap+xml; charset=utf-8' was not the expected type 'text/xml; charset=utf-8'. Server: Microsoft-IIS/7.0 X-Powered-By: ASP.NET As I understand it, (according to http://hadleynet.org/marc/whatsnew.html#S3.7.1) , A SOAP 1.2 service should be expecting type 'application/soap+xml'. Has anyone else experienced this and know of a workaround? Thanks and Regards, Barry5KViews0likes1CommentRe: calling a basic WCF service problem
I saw this problem when the WCF web service was configured to use Windows Authentication and binding="wsHttpBinding". See http://msdn.microsoft.com/en-us/library/ms731361.aspx for more details on bindings. You can comment out the windows authentication, and switch the binding="basicHttpBinding" on development systems to allow SOAP UI to work.3.5KViews1like0Comments