Skip to content

Commit 6d9c7ad

Browse files
committed
Update docs on SSLVhostSNIPolicy to cover the impact on
non-SNI connections. Reorder the table for clarity. Submitted by: Aaron Ogburn <aogburn redhat.com>, jorton git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1929361 13f79535-47bb-0310-9956-ffa450edef68
1 parent 34298bd commit 6d9c7ad

File tree

1 file changed

+16
-10
lines changed

1 file changed

+16
-10
lines changed

docs/manual/mod/mod_ssl.xml

Lines changed: 16 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1834,6 +1834,12 @@ request is associated with a virtual host which has an incompatible
18341834
SSL/TLS configuration under the policy used, an HTTP error response
18351835
with status code 421 ("Misdirected Request") will be sent.</p>
18361836

1837+
<p>The policy also applies to TLS connections where an SNI extension
1838+
is not sent during the handshake, implicitly using the default or
1839+
first virtual host definition. If the Host header in an HTTP request
1840+
on such a connection identifies any other non-default virtual host,
1841+
the compatibility policy is tested.</p>
1842+
18371843
<p>The <code>strict</code> policy blocks all HTTP requests which are
18381844
identified with a different virtual host to that identifed by SNI.
18391845
The <code>insecure</code> policy allows all HTTP requests regardless
@@ -1847,6 +1853,14 @@ policies compare specific aspects of the SSL configuration for the two
18471853
virtual hosts, which are grouped into two categories:</p>
18481854

18491855
<ul>
1856+
<li><strong>server certificate/key, or protocol/cipher
1857+
restrictions</strong>: directives which determine the server
1858+
certificate or key (<directive
1859+
module="mod_ssl">SSLCertificateKeyFile</directive> etc), cipher or
1860+
protocol restrictions (<directive
1861+
module="mod_ssl">SSLCipherSuite</directive> and <directive
1862+
module="mod_ssl">SSLProtocol</directive>)</li>
1863+
18501864
<li><strong>client vertification and authentication
18511865
settings</strong>: directives which affect TLS client certificate
18521866
verification or authentication, such as <directive
@@ -1855,14 +1869,6 @@ virtual hosts, which are grouped into two categories:</p>
18551869
module="mod_ssl">SSLCACertificatePath</directive>, <directive
18561870
module="mod_ssl">SSLSRPVerifierFile</directive>; any use of <directive
18571871
module="mod_ssl">SSLOpenSSLConfCmd</directive></li>
1858-
1859-
<li><strong>server certificate/key, or protocol/cipher
1860-
restrictions</strong>: directives which determine the server
1861-
certificate or key (<directive
1862-
module="mod_ssl">SSLCertificateKeyFile</directive> etc), cipher or
1863-
protocol restrictions (<directive
1864-
module="mod_ssl">SSLCipherSuite</directive> and <directive
1865-
module="mod_ssl">SSLProtocol</directive>)</li>
18661872
</ul>
18671873

18681874
<p>This table illustrates whether an HTTP request will be blocked or
@@ -1875,8 +1881,8 @@ under each different policy setting:</p>
18751881
<tr>
18761882
<th>Policy mode</th>
18771883
<th>Any VirtualHost mismatch</th>
1878-
<th>Client verification/<br />authentication settings</th>
18791884
<th>Server certificate/key, <br />or protocol/cipher restrictions</th>
1885+
<th>Client verification/<br />authentication settings</th>
18801886
</tr>
18811887
<tr>
18821888
<td><code>strict</code></td><td>blocked</td><td>blocked</td><td>blocked</td>
@@ -1885,7 +1891,7 @@ under each different policy setting:</p>
18851891
<td><code>secure</code></td><td>allowed</td><td>blocked</td><td>blocked</td>
18861892
</tr>
18871893
<tr>
1888-
<td><code>authonly</code></td><td>allowed</td><td>blocked</td><td>allowed</td>
1894+
<td><code>authonly</code></td><td>allowed</td><td>allowed</td><td>blocked</td>
18891895
</tr>
18901896
<tr>
18911897
<td><code>insecure</code></td><td>allowed</td><td>allowed</td><td>allowed</td>

0 commit comments

Comments
 (0)