noodl at apache
Aug 20, 2008, 3:53 PM
Post #1 of 1
(145 views)
Permalink
|
|
svn commit: r687494 - /httpd/httpd/trunk/docs/manual/mod/mod_ssl.xml
|
|
Author: noodl
Date: Wed Aug 20 15:53:35 2008
New Revision: 687494
URL: http://svn.apache.org/viewvc?rev=687494&view=rev
Log:
Minor grammar corrections for mod_ssl.xml
Modified:
httpd/httpd/trunk/docs/manual/mod/mod_ssl.xml
Modified: httpd/httpd/trunk/docs/manual/mod/mod_ssl.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_ssl.xml?rev=687494&r1=687493&r2=687494&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_ssl.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_ssl.xml Wed Aug 20 15:53:35 2008
@@ -787,10 +787,10 @@
module="mod_ssl">SSLCACertificatePath</directive> has the same effect
for the certificate chain construction, it has the side-effect that
client certificates issued by this same CA certificate are also
-accepted on client authentication. That's usually not one expect.</p>
+accepted on client authentication.</p>
<p>
But be careful: Providing the certificate chain works only if you are using a
-<em>single</em> (either RSA <em>or</em> DSA) based server certificate. If you are
+<em>single</em> RSA <em>or</em> DSA based server certificate. If you are
using a coupled RSA+DSA certificate pair, this will work only if actually both
certificates use the <em>same</em> certificate chain. Else the browsers will be
confused in this situation.</p>
|
