Return-Path:
Host
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!
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.
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.
+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 Host
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!
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.
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.
+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.