You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xmlrpc-dev@ws.apache.org by Gwyn <gw...@gmail.com> on 2007/06/01 13:16:03 UTC
Re: View the xml-rpc response
Thomas Gärtner wrote:
>
> On Friday 25 May 2007 12:29, Davide wrote:
>> how can I do to view the xml-rpc server response? When client executes
>> a request, I'd like to view the response in xml and save it into a
>> file. Can you help me?
>>
> If it is for debugging reasons only, I'd recommend using Wireshark. It
> allows
> in depth analysis of the complete network communication.
>
Hmm, I guess that means there's no logging built-in?
I checked the FAQs & the "Advanced Usage" on the website but there's
nothing there about logging, which surprises me a little, as I'd hoped that
things would have moved on since I was last looking a few years ago!
My problem with Wireshark is that I need to do this on a customer's remote
Solaris system, to which I have command-line user-level SSH access but it's
just not practical to install that sort of app there, let alone try & build
it...
Using the Commons HttpClient I can switch on 'wire' logging, but that gives
me this sort of logging:
2007/05/31 22:18:09:638 GMT+07:00 [DEBUG] content - >> "<"
2007/05/31 22:18:09:639 GMT+07:00 [DEBUG] content - >> "?"
2007/05/31 22:18:09:641 GMT+07:00 [DEBUG] content - >> "x"
2007/05/31 22:18:09:642 GMT+07:00 [DEBUG] content - >> "m"
2007/05/31 22:18:09:643 GMT+07:00 [DEBUG] content - >> "l"
2007/05/31 22:18:09:644 GMT+07:00 [DEBUG] content - >> " "
I can pick out the info needed, but it would be nice to have something a
/little/ less verbose...
/Gwyn
--
View this message in context: http://www.nabble.com/View-the-xml-rpc-response-tf3815332.html#a10910925
Sent from the Apache Xml-RPC - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: xmlrpc-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: xmlrpc-dev-help@ws.apache.org
Re: View the xml-rpc response
Posted by Jochen Wiedmann <jo...@gmail.com>.
On 6/1/07, Gwyn <gw...@gmail.com> wrote:
> My problem with Wireshark is that I need to do this on a customer's remote
> Solaris system, to which I have command-line user-level SSH access but it's
> just not practical to install that sort of app there, let alone try & build
> it...
Solaris has a builtin packet tracer in the style of tcpdump. I do not
remember the name exactly, maybe "snoop"? I typically use snoop to
create a packet trace and Wireshark to analyze the trace.
Apart from that, I agree that the ability to log input and output
would be a valuable addition. Patches welcome.
Jochen
--
Women have the ability to wind you round their little finger.
Daughters can use all of the fingers together.
---------------------------------------------------------------------
To unsubscribe, e-mail: xmlrpc-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: xmlrpc-dev-help@ws.apache.org