Contributions
Re: Does SoapUI works for WSHttpBinding WCF now?
shelingzhang wrote: Do you guy figure out the problem? I have the same problem, but it is on hold. if you found the solution, please let people know to avoid they ask the same question again and again, even it is wsdl specific problem, you can still post snip of wsdl, or a fake wsdl which doesn't contain info you don't want us to know. Please help others also help yourself in some way. Thanks I haven't got any feedback so far,15 years agoPlace ReadyAPI QuestionsReadyAPI Questions3KViews0likes0Comments- 15 years agoPlace ReadyAPI QuestionsReadyAPI Questions3KViews0likes0Comments
Does SoapUI works for WSHttpBinding WCF now?
HI I saw similar topic on this forum, but i can't find out the solution to solve the problem. Please help. We are using SoapUI 3.0.1 Pro, and calling the WCF (WSHttpBinding) from our testing server. Our SoapUI project works fine for BasicHttpBinding, but once we set it up to WSHttpBinding, it gives us the following error: (I already enabled the WSA-Addressing in my SoapUI project.) For Soap 1.1: #status# HTTP/1.1 415 Cannot process the message because the content type 'text/xml;charset=UTF-8' was not the expected type 'application/soap+xml; charset=utf-8'. For Soap 1.2: #status# HTTP/1.1 500 Internal Server Error The message could not be processed. This is most likely because the action 'http://tempuri.org/IPricingService/GetPricingRequest' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding. please help. Thanks.15 years agoPlace ReadyAPI QuestionsReadyAPI Questions9KViews0likes5Comments