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

Posted to cvs@httpd.apache.org by rb...@apache.org on 2026/03/16 03:27:08 UTC

svn commit: r1932313 - httpd/httpd/branches/2.4.x/docs/manual/mod

Author: rbowen
Date: Mon Mar 16 03:27:08 2026
New Revision: 1932313

Log:
bz52670 - clarify SSLStrictSNIVHostCheck scope

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

Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/mod_ssl.xml
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/mod_ssl.xml	Mon Mar 16 03:27:06 2026	(r1932312)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/mod_ssl.xml	Mon Mar 16 03:27:08 2026	(r1932313)
@@ -1802,6 +1802,15 @@ If set to <code>on</code> in any other v
 are not allowed to access this particular virtual host.
 </p>
 
+<p>
+If set to <code>on</code> in server context (globally, outside any
+<directive module="core" type="section">VirtualHost</directive> block),
+the setting is inherited by all virtual hosts that do not override it.
+This has the same effect as setting it to <code>on</code> in every
+default name-based virtual host: non-SNI clients will be denied access
+to any name-based virtual host.
+</p>
+
 <note type="warning"><p>
 This option is only available if httpd was compiled against an SNI capable
 version of OpenSSL.