Contributions
Content-Type text/html in default mock Soap Fault
Good afternoon everyone, In SoapUI 5.4.0, the default Soap Fault for mock services is using HTTP Content-Type 'text/html' instead of 'text/xml' as recommended in RFC2616. I was able to customize soap fault at operation level, but not at mock-service level, so when a client is making error on operation or binded message, the soap fault is using the wrong content-type. This is causing me some trouble. Here is an example : HTTP/1.1 500 Internal Server Error Content-Type: text/html; charset=iso-8859-1 Transfer-Encoding: chunked Server: Jetty(6.1.26) <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"> <soap:Body> <soap:Fault> <soap:Code> <soap:Value>Server</soap:Value> </soap:Code> <soap:Reason> <!--1 or more repetitions:--> <soap:Text xml:lang="en">Missing operation for soapAction [http://docs.oasis-open.org/ws-sx/ws-trust/200512/RST/Issue] and body element [{http://docs.oasis-open.org/ws-sx/ws-trust/200512}RequestSecurityTokenType] with SOAP Version [SOAP 1.2]</soap:Text> </soap:Reason> </soap:Fault> </soap:Body> </soap:Envelope> Is there any way to modify this default Soap Fault content-type ? Or is it possible to fix it in the SoapUI code ?1.3KViews1like0Comments