Debug REST callbacks in vCO

[ahola]

Folks -

We seem to be running into a sporadic issue with REST invocations made from an external client back into vCO. We are expecting a JSON string as part of this callback. However, at times, we see that the JSON string is empty. Note that it works for most part but does fail at times.

On the client side, I have put tracing to ensure that the invocations were done as expected. I'd like to do the same tracing on the vCO end to see all of the REST messages exactly as-is as they are received over HTTP transport before it is parsed. Wondering how I could accomplish this?

Thanks much.
Shashi

[sanchezs · Accepted solution]

Hi Shashi,

I'm not sure what is the service you're trying to trace, but in any case you can always put an external proxy "next to the server" to see what you get actually. You can use something simple like tcpmon (http://code.google.com/p/tcpmon/), or in case you need something more sophisticated with SSL support and so you can try with Burp (http://www.portswigger.net/burp/help/proxy.html).

I hope it helps

Sergio