Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 12395 invoked from network); 20 Mar 2006 16:41:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Mar 2006 16:41:55 -0000 Received: (qmail 52911 invoked by uid 500); 20 Mar 2006 16:41:46 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 52897 invoked by uid 500); 20 Mar 2006 16:41:45 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 52850 invoked by uid 99); 20 Mar 2006 16:41:45 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Mar 2006 08:41:45 -0800 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=FROM_NO_LOWER,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [206.39.12.245] (HELO dns24b.dfas.mil) (206.39.12.245) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Mar 2006 08:41:44 -0800 Received: from iso-e2-w-1.DS.DFAS.MIL (iso-e2-w-1.ds.dfas.mil [158.18.1.127]) by dns24b.dfas.mil with ESMTP id k2KGfIr7022429 for ; Mon, 20 Mar 2006 11:41:18 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C64C3D.0F46E066" Date: Mon, 20 Mar 2006 11:40:55 -0500 Message-ID: <932ACD88A2215048AB039F28F23CC14307C5C72B@iso-e2-w-1.ds.dfas.mil> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SSL Handshake error handling Thread-Index: AcZMPQ7y1O8wVEy/TM6sNr4dfKUQ+w== From: "TAYLOR, TIM \(CONTRACTOR\)" To: X-Virus-Checked: Checked by ClamAV on apache.org Subject: [users@httpd] SSL Handshake error handling X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C64C3D.0F46E066 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Does anyone know if it is possible to put in a custom response for errors that occur during the handshake. Apparently, these are not HTTP errors that I can use the ErrorDocument directive with. Specifically, I want to give a meaningful message to users who don't provide a valid X.509 certificate when SSLClientVerify require is set. Any ideas? regards, tt 317-510-7346 ------_=_NextPart_001_01C64C3D.0F46E066 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable SSL Handshake error handling

Does anyone know if it is possible to = put in a custom response for errors that occur during the handshake. = Apparently, these are not HTTP errors that I can use the ErrorDocument = directive with.

Specifically, I want to give a = meaningful message to users who don't provide a valid X.509 certificate = when SSLClientVerify require is set.

Any ideas?

regards,
tt
317-510-7346

------_=_NextPart_001_01C64C3D.0F46E066--