https://bz.apache.org/bugzilla/show_bug.cgi?id=58244
Christopher Schultz <ch...@christopherschultz.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #3 from Christopher Schultz <ch...@christopherschultz.net> ---
If you use Wireshark or a similar packet-capture rig, can you see
whether the browser is changing the way it sends its data?
With Wireshark, you can install the server's private key and then you
can read all the encrypted traffic. Wireshark will disassemble all the
packets and even give you rich information at the protocol-level about
what's in there. You can probably tell the difference between what
Firefox or Chrome sends to the server both before and after the "loss"
of the certificate.
I'd like to confirm whether the browser or Tomcat is causing this problem... my
suspicion is that it's the browser.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
