Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 47926 invoked from network); 7 May 2007 09:36:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 May 2007 09:36:17 -0000 Received: (qmail 35335 invoked by uid 500); 7 May 2007 09:36:10 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 34812 invoked by uid 500); 7 May 2007 09:36:09 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 34800 invoked by uid 99); 7 May 2007 09:36:09 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 May 2007 02:36:09 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [194.192.81.140] (HELO delivery1.hostedsepo.dk) (194.192.81.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 May 2007 02:36:00 -0700 Received: from SEPO-CRYPTO04 ([10.0.81.157]) by dispatch-outgoing.hostedsepo.dk (JAMES SMTP Server 2.2.0TE13) with SMTP ID 8 for ; Mon, 7 May 2007 11:35:37 +0200 (CEST) Received: from mail.sepo.dk (mail.sepo.dk [80.166.233.75]) by outgoing-prescan.hostedsepo.dk (Postfix) with ESMTP id 64010DA80D for ; Mon, 7 May 2007 11:34:33 +0200 (CEST) Received: from [10.48.34.102] (unknown [10.48.34.102]) by mail.sepo.dk (Postfix) with ESMTP id 3B1692394A for ; Mon, 7 May 2007 11:35:29 +0200 (CEST) Message-ID: <463EF1B3.2090607@sepo.dk> Date: Mon, 07 May 2007 11:30:27 +0200 From: Subscriber User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Handling SSL Client Auth abort References: <4639C91E.6080400@sepo.dk> <4639DE2B.9090903@sepo.dk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, >> ...unfortunately I never get that far where I can catch the >> exception. >> The exception is thrown within Tomcat and in my application code. > > (I'll assume there's a rather critical "not" missing from the last > clause in the above sentence.) Of course - NOT in my application code :-) > If the client refuses the certificate or otherwise breaks the connection > during the SSL negotiation, no servlet has been selected to receive the > message, so there's no one to deliver the exception to. The servlet > spec doesn't seem to have any notion of container-oriented error pages, > so I think you're out of luck without custom code inside Tomcat. > > - Chuck This is OK - but how do I put custom code into the Tomcat? I've already coded a custom realm for the purpose of verifying the certificate - could I use this realm to catch the exception? Regards, kews --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org