Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] catching SSLHandShakeExceptions in HttpClient

Hi,

9.3.6

On Mon, Oct 16, 2017 at 3:50 PM, Simone Bordet <sbordet@xxxxxxxxxxx> wrote:
Hi,

On Mon, Oct 16, 2017 at 4:01 PM, Java CodeSmith <jcodesmith@xxxxxxxxx> wrote:
> 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)

Cut and pasted your code, and I get:

2017-10-16 21:49:21.940:INFO::main: Logging initialized @219ms to
org.eclipse.jetty.util.log.StdErrLog
2017-10-16 21:49:22.230:WARN:oejus.SslContextFactory:main: No
supported ciphers from [<snipped ciphers>]
oncomplete was run

What exact Jetty version are you using ?

--
Simone Bordet
----
http://cometd.org
http://webtide.com
Developer advice, training, services and support
from the Jetty & CometD experts.
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users


Back to the top