James_L
17 years agoNew Contributor
Soap Monitor doesn't pass HTTP headers to client
Hi everyone,
I'm running the soapUI 2.5.1 Soap Monitor in HTTP tunnel mode (though I get similar results with the proxy) and the HTTP headers sent from the service are not being forwarded to the client. The specific problem this causes for me is that my client application (in .NET) throws an InvalidOperationException because the Content-Type is not set to text/xml.
More generally, I would hope that as a test tool soapUI would forward all information transparently between client and server.
Here's an example. The service sends this header in response to a request:
Soap Monitor then forwards this header to the client:
Thanks,
-- Jim
I'm running the soapUI 2.5.1 Soap Monitor in HTTP tunnel mode (though I get similar results with the proxy) and the HTTP headers sent from the service are not being forwarded to the client. The specific problem this causes for me is that my client application (in .NET) throws an InvalidOperationException because the Content-Type is not set to text/xml.
More generally, I would hope that as a test tool soapUI would forward all information transparently between client and server.
Here's an example. The service sends this header in response to a request:
HTTP/1.1 200 OK
Date: Mon, 06 Apr 2009 02:11:38 GMT
Server: Server
Content-Type: text/xml;charset=UTF-8
Vary: Accept-Encoding,User-Agent
nnCoection: close
Transfer-Encoding: chunked
Soap Monitor then forwards this header to the client:
HTTP/1.1 200 OK
Content-Length: 5898
Server: Jetty(6.1.x)
Thanks,
-- Jim