@@ -1834,6 +1834,12 @@ request is associated with a virtual host which has an incompatible
18341834SSL/TLS configuration under the policy used, an HTTP error response
18351835with 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
18381844identified with a different virtual host to that identifed by SNI.
18391845The <code >insecure</code > policy allows all HTTP requests regardless
@@ -1847,6 +1853,14 @@ policies compare specific aspects of the SSL configuration for the two
18471853virtual 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