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 2012/03/05 02:18:04 UTC
svn commit: r1296921 - in /httpd/httpd/branches/2.2.x/docs/manual/ssl:
ssl_faq.html.en ssl_faq.xml
Author: rbowen
Date: Mon Mar 5 01:18:03 2012
New Revision: 1296921
URL: http://svn.apache.org/viewvc?rev=1296921&view=rev
Log:
As per https://issues.apache.org/bugzilla/show_bug.cgi?id=51746, note
that wildcard certs and subjectAltName are viable solutions.
Modified:
httpd/httpd/branches/2.2.x/docs/manual/ssl/ssl_faq.html.en
httpd/httpd/branches/2.2.x/docs/manual/ssl/ssl_faq.xml
Modified: httpd/httpd/branches/2.2.x/docs/manual/ssl/ssl_faq.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/ssl/ssl_faq.html.en?rev=1296921&r1=1296920&r2=1296921&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/ssl/ssl_faq.html.en (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/ssl/ssl_faq.html.en Mon Mar 5 01:18:03 2012
@@ -762,7 +762,13 @@ error when connecting to my newly instal
Apache has to know the <code>Host</code> HTTP header field. To do this, the
HTTP request header has to be read. This cannot be done before the SSL
handshake is finished, but the information is needed in order to
- complete the SSL handshake phase. Bingo!</p>
+ complete the SSL handshake phase. See the next question for how to
+ circumvent this issue.</p>
+
+ <p>Note that if you have a wildcard SSL certificate, or a
+ certificate that has multple hostnames on it using subjectAltName
+ fields, you can use SSL on name-based virtual hosts without further
+ workarounds.</p>
<h3><a name="vhosts2" id="vhosts2">Why is it not possible to use Name-Based
@@ -778,6 +784,11 @@ Virtual Hosting to identify different SS
feature that only the most recent revisions of the SSL
specification added, called Server Name Indication (SNI).</p>
+ <p>Note that if you have a wildcard SSL certificate, or a
+ certificate that has multple hostnames on it using subjectAltName
+ fields, you can use SSL on name-based virtual hosts without further
+ workarounds.</p>
+
<p>The reason is that the SSL protocol is a separate layer which
encapsulates the HTTP protocol. So the SSL session is a separate
transaction, that takes place before the HTTP session has begun.
Modified: httpd/httpd/branches/2.2.x/docs/manual/ssl/ssl_faq.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/ssl/ssl_faq.xml?rev=1296921&r1=1296920&r2=1296921&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/ssl/ssl_faq.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/ssl/ssl_faq.xml Mon Mar 5 01:18:03 2012
@@ -771,7 +771,13 @@ error when connecting to my newly instal
Apache has to know the <code>Host</code> HTTP header field. To do this, the
HTTP request header has to be read. This cannot be done before the SSL
handshake is finished, but the information is needed in order to
- complete the SSL handshake phase. Bingo!</p>
+ complete the SSL handshake phase. See the next question for how to
+ circumvent this issue.</p>
+
+ <p>Note that if you have a wildcard SSL certificate, or a
+ certificate that has multple hostnames on it using subjectAltName
+ fields, you can use SSL on name-based virtual hosts without further
+ workarounds.</p>
</section>
<section id="vhosts2"><title>Why is it not possible to use Name-Based
@@ -787,6 +793,11 @@ Virtual Hosting to identify different SS
feature that only the most recent revisions of the SSL
specification added, called Server Name Indication (SNI).</p>
+ <p>Note that if you have a wildcard SSL certificate, or a
+ certificate that has multple hostnames on it using subjectAltName
+ fields, you can use SSL on name-based virtual hosts without further
+ workarounds.</p>
+
<p>The reason is that the SSL protocol is a separate layer which
encapsulates the HTTP protocol. So the SSL session is a separate
transaction, that takes place before the HTTP session has begun.