I would not expect to find that in the Android docs. But since you are already starting to use Wireshark, there is a way to let Wireshark have access to your session key and decode the packets. I have never actually done this myself, but see http://www.novell.com/coolsolutions/appnote/19321.html (though this is server side).
On Aug 24, 10:38 am, Bret Foreman <[email protected]> wrote: > Ah, I think I found one source of difficulty. The protocol is HTTPS, > not HTTP. I found a bunch of HTTPS traffic in the cap file but it's > pretty hard to determine what's wrong. Everything looks normal, though > it's a little more complicated than the usual case because of the > HTTPS key exchange and stuff. The server only supports HTTPS so > there's no option to turn it off for debugging. Maybe the HTTP client > needs some special settings to make HTTPS work? I don't see anything > about it in the Android docs. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
