View raw server response

[Al Twohill <mo...@gmail.com>]

Hi there,

Apologies if it is inappropriate to post non-dev questions on this
list, but I could not find any other point of contact.

I'm currently developing a Java module to link H-Sphere to our local
domain registrar, which uses XML-RPC. They only deal with PHP so
aren't able to be very helpful with the particular problem I'm having.

Some queries are working fine, so communication with the server isn't
a problem, but when I try other methods I get:

org.apache.xmlrpc.client.XmlRpcClientException: Failed to parse
servers response: Expected methodResponse element, got br

Is there a way I can retrieve the "raw" server response in order to
debug this further? The server I'm communicating with is HTTPS so
packet sniffers aren't too helpful.

Any assistance at all is appreciated.

Cheers, Al

-- 
The project has begun...

Re: View raw server response

[Don Albertson <dg...@psu.edu>]

Al Twohill wrote:
> On Mon, Nov 17, 2008 at 1:28 PM, Jochen Wiedmann
> <jo...@gmail.com> wrote:
>   
>> On Mon, Nov 17, 2008 at 12:51 AM, Al Twohill <mo...@gmail.com> wrote:
>>
>>     
>>> Is there a way I can retrieve the "raw" server response in order to
>>> debug this further? The server I'm communicating with is HTTPS so
>>> packet sniffers aren't too helpful.
>>>       
>> Use Wireshark, Tcpmon, or a similar tool.
>>     
>
> Like I said, the communication is over HTTPS. All I see in Wireshark is
>
>  sE4@8Y+
>
> &7"ofP7Y
> 8J!
>
> etc...
>
> If you do know of a way to see the actual response of an encrypted
> connection, I'm all ears ;)
>
> Al
>
>   
>> Jochen
>>
>> --
>> I have always wished for my computer to be as easy to use as my
>> telephone; my wish has come true because I can no longer figure out
>> how to use my telephone.
>>
>>    -- (Bjarne Stroustrup,
>> http://www.research.att.com/~bs/bs_faq.html#really-say-that
>>       My guess: Nokia E50)
>>
>>     
>
>
>
>   
You might try WebScarab which allows you to intercept the request and 
the response.

Re: View raw server response

[Hybris <hy...@gmail.com>]

Al Twohill wrote:

> If you do know of a way to see the actual response of an encrypted
> connection, I'm all ears ;)

if you know the keys used to encrypt you can decrypt the dialog with 
wireshark but i never did it.

google: wireshark decrypt https

Re: View raw server response

[Jochen Wiedmann <jo...@gmail.com>]

On Mon, Nov 17, 2008 at 2:01 AM, Al Twohill <mo...@gmail.com> wrote:

> Like I said, the communication is over HTTPS. All I see in Wireshark is

Sorry for the fast shot. AFAIK, you might use
http://donsproxy.sourceforge.net/ for that.


-- 
I have always wished for my computer to be as easy to use as my
telephone; my wish has come true because I can no longer figure out
how to use my telephone.

    -- (Bjarne Stroustrup,
http://www.research.att.com/~bs/bs_faq.html#really-say-that
       My guess: Nokia E50)

Re: View raw server response

[Al Twohill <mo...@gmail.com>]

On Mon, Nov 17, 2008 at 1:28 PM, Jochen Wiedmann
<jo...@gmail.com> wrote:
> On Mon, Nov 17, 2008 at 12:51 AM, Al Twohill <mo...@gmail.com> wrote:
>
>> Is there a way I can retrieve the "raw" server response in order to
>> debug this further? The server I'm communicating with is HTTPS so
>> packet sniffers aren't too helpful.
>
> Use Wireshark, Tcpmon, or a similar tool.

Like I said, the communication is over HTTPS. All I see in Wireshark is

 sE4@8Y+

&7"ofP7Y
8J!

etc...

If you do know of a way to see the actual response of an encrypted
connection, I'm all ears ;)

Al

>
> Jochen
>
> --
> I have always wished for my computer to be as easy to use as my
> telephone; my wish has come true because I can no longer figure out
> how to use my telephone.
>
>    -- (Bjarne Stroustrup,
> http://www.research.att.com/~bs/bs_faq.html#really-say-that
>       My guess: Nokia E50)
>



-- 
The project has begun...

Re: View raw server response

[Jochen Wiedmann <jo...@gmail.com>]

On Mon, Nov 17, 2008 at 12:51 AM, Al Twohill <mo...@gmail.com> wrote:

> Is there a way I can retrieve the "raw" server response in order to
> debug this further? The server I'm communicating with is HTTPS so
> packet sniffers aren't too helpful.

Use Wireshark, Tcpmon, or a similar tool.

Jochen

-- 
I have always wished for my computer to be as easy to use as my
telephone; my wish has come true because I can no longer figure out
how to use my telephone.

    -- (Bjarne Stroustrup,
http://www.research.att.com/~bs/bs_faq.html#really-say-that
       My guess: Nokia E50)