I'm sorry to insist...anyone at Jakarta knows about this problem??
Gustavo Rodríguez wrote:
Hi everyone! We were working in this issue some time ago, and
reported that when using the clientAuth=want parameter, we got the
following exception:
java.net.SocketException: Socket Closed at
Hi everyone! We were working in this issue some time ago, and
reported that when using the clientAuth=want parameter, we got the
following exception:
java.net.SocketException: Socket Closed
at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:177)
We left it for some time, as
...
(client IP) - - [(Sysdate)] GET /(app. directory)/ HTTP/1.1 400 45
-Mensaje original-
De: news [mailto:[EMAIL PROTECTED] En nombre de Bill Barker
Enviado el: viernes, 05 de marzo de 2004 3:20
Para: [EMAIL PROTECTED]
Asunto: Re: Client authentication and customized error pages
Using
-Mensaje original-
De: news [mailto:[EMAIL PROTECTED] En nombre de Bill Barker
Enviado el: viernes, 05 de marzo de 2004 3:20
Para: [EMAIL PROTECTED]
Asunto: Re: Client authentication and customized error pages
Using clientAuth=true, the error happens too early to be able to invoke
Hi everyone!
I'm using SSL client authentication in a tomcat 5.0.19. Everything goes
fine, but i need some help customizing error pages.
When a client want to use my application, the browser asks him to choose
a valid certificate, but perhaps he hasn't a valid one. If he doesn't
have a
Using clientAuth=true, the error happens too early to be able to invoke an
error-page. You might try using clientAuth=want instead. In this case,
the user still gets prompted for a cert, but the request continues if she
hits cancel. It is then the responsibility of your webapp to handle the
