https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5692
--- Comment #4 from Sake <sake@xxxxxxxxxx> 2011-02-14 07:38:55 PST ---
(In reply to comment #3)
> Hmmmm, even after getting the SSL to decrypt properly now, "follow SSL stream"
> shows the request decoded but the server replies are shown in their raw
> version.
>
> In the packets (and the reassembled PDU) I do see the reply in clear text
> (decrypted) on the relevant tabs.
>
> Again an overlooked option somewhere?
Do you see the response headers in cleartext, but the response data in
gibberish? If so, was there a "Content-Encoding: gzip" or "Content-Encoding:
deflate" in the response header? If so, the content is compressed and
Follow-SSL stream does not support decompression (neither does Follow-TCP
stream).
If not, are you able to share the private key of the server? You can restrict
access to it by marking it private. That way, only core-developers will be able
to look at it.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
