@@ -1871,6 +1871,12 @@ request is associated with a virtual host which has an incompatible
18711871SSL/TLS configuration under the policy used, an HTTP error response
18721872with status code 421 ("Misdirected Request") will be sent.</p >
18731873
1874+ <p >The policy also applies to TLS connections where an SNI extension
1875+ is not sent during the handshake, implicitly using the default or
1876+ first virtual host definition. If the Host header in an HTTP request
1877+ on such a connection identifies any other non-default virtual host,
1878+ the compatibility policy is tested.</p >
1879+
18741880<p >The <code >strict</code > policy blocks all HTTP requests which are
18751881identified with a different virtual host to that identifed by SNI.
18761882The <code >insecure</code > policy allows all HTTP requests regardless
@@ -1884,6 +1890,14 @@ policies compare specific aspects of the SSL configuration for the two
18841890virtual hosts, which are grouped into two categories:</p >
18851891
18861892<ul >
1893+ <li ><strong >server certificate/key, or protocol/cipher
1894+ restrictions</strong >: directives which determine the server
1895+ certificate or key (<directive
1896+ module =" mod_ssl" >SSLCertificateKeyFile</directive > etc), cipher or
1897+ protocol restrictions (<directive
1898+ module =" mod_ssl" >SSLCipherSuite</directive > and <directive
1899+ module =" mod_ssl" >SSLProtocol</directive >)</li >
1900+
18871901 <li ><strong >client vertification and authentication
18881902 settings</strong >: directives which affect TLS client certificate
18891903 verification or authentication, such as <directive
@@ -1892,14 +1906,6 @@ virtual hosts, which are grouped into two categories:</p>
18921906 module =" mod_ssl" >SSLCACertificatePath</directive >, <directive
18931907 module =" mod_ssl" >SSLSRPVerifierFile</directive >; any use of <directive
18941908 module =" mod_ssl" >SSLOpenSSLConfCmd</directive ></li >
1895-
1896- <li ><strong >server certificate/key, or protocol/cipher
1897- restrictions</strong >: directives which determine the server
1898- certificate or key (<directive
1899- module =" mod_ssl" >SSLCertificateKeyFile</directive > etc), cipher or
1900- protocol restrictions (<directive
1901- module =" mod_ssl" >SSLCipherSuite</directive > and <directive
1902- module =" mod_ssl" >SSLProtocol</directive >)</li >
19031909</ul >
19041910
19051911<p >This table illustrates whether an HTTP request will be blocked or
@@ -1912,8 +1918,8 @@ under each different policy setting:</p>
19121918<tr >
19131919 <th >Policy mode</th >
19141920 <th >Any VirtualHost mismatch</th >
1915- <th >Client verification/<br />authentication settings</th >
19161921 <th >Server certificate/key, <br />or protocol/cipher restrictions</th >
1922+ <th >Client verification/<br />authentication settings</th >
19171923</tr >
19181924<tr >
19191925 <td ><code >strict</code ></td ><td >blocked</td ><td >blocked</td ><td >blocked</td >
@@ -1922,7 +1928,7 @@ under each different policy setting:</p>
19221928 <td ><code >secure</code ></td ><td >allowed</td ><td >blocked</td ><td >blocked</td >
19231929</tr >
19241930<tr >
1925- <td ><code >authonly</code ></td ><td >allowed</td ><td >blocked </td ><td >allowed </td >
1931+ <td ><code >authonly</code ></td ><td >allowed</td ><td >allowed </td ><td >blocked </td >
19261932</tr >
19271933<tr >
19281934 <td ><code >insecure</code ></td ><td >allowed</td ><td >allowed</td ><td >allowed</td >
0 commit comments