From: Rich Bowen
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. diff --git a/docs/manual/ssl/ssl_faq.xml b/docs/manual/ssl/ssl_faq.xml index 8fa2ce3bbe..96d0938c98 100644 --- a/docs/manual/ssl/ssl_faq.xml +++ b/docs/manual/ssl/ssl_faq.xml @@ -607,6 +607,11 @@ error when connecting to my newly installed server? handshake is finished, but the information is needed in order to complete the SSL handshake phase. See the next question for how to circumvent this issue.
+ +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.