https://issues.apache.org/bugzilla/show_bug.cgi?id=54690
--- Comment #3 from Mark Thomas <ma...@apache.org> --- Some issues at $work have prompted me to look into this further. Fundamentally, this is a JVM bug. I think the way forward is to use socket.getEnabledProtocols() to determine what the default protocols really are rather than using context.getDefaultSSLParameters().getProtocols() That should then be JVM neutral. We can also add a test case that will pick up if this ever gets fixed in the JVM. I'll look into patching this tomorrow. -- 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
