https://bz.apache.org/bugzilla/show_bug.cgi?id=65975
--- Comment #18 from Christopher Schultz <ch...@christopherschultz.net> --- (In reply to Martin Stangl from comment #17) > I captured the traffic from when the client certificate is submitted to the > server until the authentication completed. So basically the full 60 seconds > of delay. > > Wireshark could not capture anything while my machine was offline, which is > understandable. I think you misunderstood what I was suggesting: using Wireshark to monitor *outbound* traffic during your testing. We want to catch whatever process is making an outgoing connection and timing out. Wireshark should definitely be able to tell you *something* is happening. DNS lookup, or connection-attempt to some remote service which fails after 60 seconds when you are connected and fails *immediately* when you are not connected. > Let me know if we also need to capture the communication between the browser > and tomcat as this requires for me to setup Wireshark for Loopback capturing. No need to capture anything between the browser and the server. I'm only interested in seeing what the server is trying to do when you authenticate. I suspect if you look for new connection attempts (on any protocol, to any host/port) as you authenticate, and you ignore the connection from the browser -> Tomcat, you'll find the answer pretty quickly. -- 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
