I'm actually *trying* make a failure here to simulate an SSL handshake exception failure so I can confirm my application handles an SSL handshake exception properly. So it's not not like I expect it to work. I just need the exception to be handled in the same way as a real *normal*
If an SSL negotation fails on an async request, where is that failure detectable? (other than the logs) On Mon, Oct 16, 2017 at 8:44 AM, Joakim Erdfelt <[email protected]> wrote: > This configuration ... > > >> SslContextFactory ssl = new SslContextFactory(); >> >> ssl.setExcludeProtocols(".*"); >> ssl.setIncludeProtocols(); >> ssl.setIncludeCipherSuites(); >> ssl.setExcludeCipherSuites(".*"); >> > > Excludes all protocols and cipher suites. > You have nothing left to connect with. > > Simone, has the request even started in this situation? > > - Joakim > > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
