What happens when I run in ssldebug mode then? If I could capture those errors I can make them available offline at the very least?
--Maarten On Mar 14, 2013, at 5:53 PM, Joakim Erdfelt <[email protected]> wrote: > That would be a bit tough... > > As you need to establish a proper SSL connection in order to even talk HTTP. > If the SSL connection fails, there's no HTTP exchange, hence no way to > respond. > > -- > Joakim Erdfelt <[email protected]> > > On Thu, Mar 14, 2013 at 9:49 AM, Maarten Koopmans <[email protected]> > wrote: > Hi, > > I have a SSL-protected application (client certificates) in Jetty 8, where I > do some custom logic with client certificates from the application layer. > > Is there a way to propagate and catch the errors like SSL handshakes etc. to > the application/war, so I can provide user-friendly feedback to my end users? > > A typical error case: > 1- REST client tries to connect with client certificate > 2- SSL error, say we don't have the CA in our trust chain > 3- blurb follows > > I'd like to catch 2 so I can "massage" 3. Is there a way to write a > filter/handler/whatnot/... to do this. > > Any thoughts, pointers our feedback greatly appreciated! > > Thanks, > > Maarten > > > > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users > > > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
