You are viewing a plain text version of this content. The canonical link for it is here.

Posted to cvs@httpd.apache.org by rp...@apache.org on 2009/10/13 18:20:03 UTC

svn commit: r824832 - /httpd/httpd/branches/2.2.x/docs/manual/mod/mod_ssl.xml

Author: rpluem
Date: Tue Oct 13 16:20:03 2009
New Revision: 824832

URL: http://svn.apache.org/viewvc?rev=824832&view=rev
Log:
* Link note to SSLProxyCheckPeerCN and SSLProxyCheckPeerExpire directives which
  can be used to fix the warning.

Modified:
    httpd/httpd/branches/2.2.x/docs/manual/mod/mod_ssl.xml

Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mod_ssl.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/mod/mod_ssl.xml?rev=824832&r1=824831&r2=824832&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mod_ssl.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mod_ssl.xml Tue Oct 13 16:20:03 2009
@@ -1473,7 +1473,12 @@
 server is "secure" beyond the fact that the certificate is signed by
 one of the CAs configured using the
 <directive>SSLProxyCACertificatePath</directive> and/or
-<directive>SSLProxyCACertificateFile</directive> directives.</p>
+<directive>SSLProxyCACertificateFile</directive> directives.
+In order to get this check done please have a look at
+<directive>SSLProxyCheckPeerCN</directive> and
+<directive>SSLProxyCheckPeerExpire</directive> directives which are off by
+default.
+</p>
 </note>
 
 <p>