Hi Amit,

It is sometimes useful (and sometimes necessary) to get at the HTTP traffic itself for troubleshooting a SOAP/HTTP issues such as this.

I usually use the (very old, not-maintained, but still useful) Apache 'tcpmon' tool for this: basically you can proxy your PRPC SOAP CONNECTOR through it and examine the response : kinda like using 'Fiddler' for Web Services.

'tpcmon' is available still on Apache Web Sites: http://ws.apache.org/tcpmon/tcpmontutorial.html

The basic approach is to fire up tcpmon as a 'listener' (not a proxy) and change the host/port configuration on your PRPC Connector to talk to that endpoint. *

You then configure 'tpcmon' to forward it's requests to the original host:port of the original endpoint: and then read off the HTTP traffic (including HTTP responses and headers etc).

Thanks,

John

*[ Sometimes this simplistic  approach doesn't work : the endpoint may insert the original endpoint hostname (via HTTP headers)  in the traffic, which will cause the client to attempt to contact the original endpoint...defeating the object of this diagnostic.

In that case: you can usually get round this by having three physical hosts (prpc, endpoint and tcpmon): edit the 'hosts' file of the prpc host, to 'lie' about the 'endpoints' IP address - instead you map that to the 'tcpmon' host.

From the 'tcpmon' host, you just set up the normal forwarding. ]