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 a
g; it seems that it's trying to get the "Error 400"
> page...
>
> (client IP) - - [(Sysdate)] "GET /(app. directory)/ HTTP/1.1" 400 45
>
>
>
> -Mensaje original-
> De: news [mailto:[EMAIL PROTECTED] En nombre de Bill Barker
> Enviado
s the access log; it seems that it's trying to get the "Error 400"
page...
(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
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 th
