View Single Post
  #2  
Old 14th June 2013, 09:48
zenny zenny is offline
Senior Member
 
Join Date: Nov 2006
Posts: 176
Thanks: 20
Thanked 6 Times in 6 Posts
Exclamation Some additional info

Hi with bump!

1. According to http://debian-handbook.info/browse/w...eb-server.html, it simply states that:

Quote:
The Apache package provided in Debian is built with support for SNI; no particular configuration is therefore needed, apart from enabling name-based virtual hosting on port 443 (SSL) as well as the usual port 80. This is a simple matter of editing /etc/apache2/ports.conf so it includes the following:

Code:
<IfModule mod_ssl.c>
    NameVirtualHost *:443
    Listen 443
</IfModule>
2. And /etc/apache2/ports.conf categorically states that:
Quote:
# If you add NameVirtualHost *:443 here, you will also have to change
# the VirtualHost statement in /etc/apache2/sites-available/default-ssl
# to <VirtualHost *:443>

# Server Name Indication for SSL named virtual hosts is currently not
# supported by MSIE on Windows XP.
3. Thus, in the /etc/apache2/sites-available/default-ssl, it has been changed from:

Code:
<VirtualHost _default_:443>
to:

Code:
<VirtualHost *:443>
4. Now, how does ISPconfig3 handles SNI? Do one need to enable SSL option in domain to enable SNI in the ISPConfig3 server?

Expecting an ISPConfig3 way of SNI for multiple domains from Falko. Thanks in advance!
Reply With Quote