From c9ee0acba09b296575a0b6010a8833326b01ce60 Mon Sep 17 00:00:00 2001
From: Eric Covener <covener@apache.org>
Date: Sat, 17 Sep 2016 13:09:33 +0000
Subject: [PATCH] xform

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1761216 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/mod/mod_ssl.html.en | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/docs/manual/mod/mod_ssl.html.en b/docs/manual/mod/mod_ssl.html.en
index 942319d8c5..4bce563b41 100644
--- a/docs/manual/mod/mod_ssl.html.en
+++ b/docs/manual/mod/mod_ssl.html.en
@@ -2665,13 +2665,9 @@ The following levels are available for <em>level</em>:</p>
      the client <em>has to</em> present a valid Certificate</li>
 <li><strong>optional_no_ca</strong>:
      the client may present a valid Certificate<br />
-     but it need not to be (successfully) verifiable.</li>
+     but it need not to be (successfully) verifiable. This option
+     cannot be relied upon for client authentication.  </li>
 </ul>
-<p>In practice only levels <strong>none</strong> and
-<strong>require</strong> are really interesting, because level
-<strong>optional</strong> doesn't work with all browsers and level
-<strong>optional_no_ca</strong> is actually against the idea of
-authentication (but can be used to establish SSL test pages, etc.)</p>
 <div class="example"><h3>Example</h3><pre class="prettyprint lang-config">SSLVerifyClient require</pre>
 </div>
 
-- 
2.50.1