<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Virtual Hosts and Wildcard SSL Certificates with Apache 2.2</title>
	<atom:link href="http://www.cb1inc.com/2008/09/11/virtual-hosts-and-wildcard-ssl-certificates-with-apache-2-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cb1inc.com/2008/09/11/virtual-hosts-and-wildcard-ssl-certificates-with-apache-2-2/</link>
	<description></description>
	<lastBuildDate>Fri, 13 Jan 2012 14:53:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: Luis Fernando Alen</title>
		<link>http://www.cb1inc.com/2008/09/11/virtual-hosts-and-wildcard-ssl-certificates-with-apache-2-2/comment-page-1/#comment-6770</link>
		<dc:creator>Luis Fernando Alen</dc:creator>
		<pubDate>Fri, 13 Jan 2012 12:49:21 +0000</pubDate>
		<guid isPermaLink="false">#comment-6770</guid>
		<description>Are you sure this works?

According to the Apache documentation, it is not possible to use Name-Based Virtual Hosting to identify different SSL virtual hosts, unless you use Apache 2.2.12 or later web server, built with 0.9.8j or later OpenSSL.

Is that the case?

http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#vhosts2

&quot;It is possible, but only if using a 2.2.12 or later web server, built with 0.9.8j or later OpenSSL. This is because it requires a feature that only the most recent revisions of the SSL specification added, called Server Name Indication (SNI).

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. The server receives an SSL request on IP address X and port Y (usually 443). Since the SSL request did not contain any Host: field, the server had no way to decide which SSL virtual host to use. Usually, it just used the first one it found which matched the port and IP address specified.&quot;</description>
		<content:encoded><![CDATA[<p>Are you sure this works?</p>
<p>According to the Apache documentation, it is not possible to use Name-Based Virtual Hosting to identify different SSL virtual hosts, unless you use Apache 2.2.12 or later web server, built with 0.9.8j or later OpenSSL.</p>
<p>Is that the case?</p>
<p><a href="http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#vhosts2" rel="nofollow">http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#vhosts2</a></p>
<p>&#8220;It is possible, but only if using a 2.2.12 or later web server, built with 0.9.8j or later OpenSSL. This is because it requires a feature that only the most recent revisions of the SSL specification added, called Server Name Indication (SNI).</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. The server receives an SSL request on IP address X and port Y (usually 443). Since the SSL request did not contain any Host: field, the server had no way to decide which SSL virtual host to use. Usually, it just used the first one it found which matched the port and IP address specified.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Huska</title>
		<link>http://www.cb1inc.com/2008/09/11/virtual-hosts-and-wildcard-ssl-certificates-with-apache-2-2/comment-page-1/#comment-3581</link>
		<dc:creator>Huska</dc:creator>
		<pubDate>Mon, 17 Oct 2011 17:50:25 +0000</pubDate>
		<guid isPermaLink="false">#comment-3581</guid>
		<description>This is similar to my setup, however I have a problem. The &quot;HTTPS=on&quot; server environment variable is not set on those simple vhosts. It seems as if you need a full set of SSL* directives on each vhost in order for the env vars to be set.</description>
		<content:encoded><![CDATA[<p>This is similar to my setup, however I have a problem. The &#8220;HTTPS=on&#8221; server environment variable is not set on those simple vhosts. It seems as if you need a full set of SSL* directives on each vhost in order for the env vars to be set.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Multiple subdomains (virtual hosts) using a wildcard cert and single ip &#124; Hosting Fit</title>
		<link>http://www.cb1inc.com/2008/09/11/virtual-hosts-and-wildcard-ssl-certificates-with-apache-2-2/comment-page-1/#comment-3204</link>
		<dc:creator>Multiple subdomains (virtual hosts) using a wildcard cert and single ip &#124; Hosting Fit</dc:creator>
		<pubDate>Thu, 08 Sep 2011 21:08:23 +0000</pubDate>
		<guid isPermaLink="false">#comment-3204</guid>
		<description>[...] http://www.cb1inc.com/2008/09/11/vir&#8230;ith-apache-2.2 [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.cb1inc.com/2008/09/11/vir&#8230;ith-apache-2.2" rel="nofollow">http://www.cb1inc.com/2008/09/11/vir&#8230;ith-apache-2.2</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Virtual Hosts and Wildcard SSL Certificates with Apache 2.2 &#124; TurboLinux Blog</title>
		<link>http://www.cb1inc.com/2008/09/11/virtual-hosts-and-wildcard-ssl-certificates-with-apache-2-2/comment-page-1/#comment-2820</link>
		<dc:creator>Virtual Hosts and Wildcard SSL Certificates with Apache 2.2 &#124; TurboLinux Blog</dc:creator>
		<pubDate>Thu, 04 Aug 2011 12:36:48 +0000</pubDate>
		<guid isPermaLink="false">#comment-2820</guid>
		<description>[...] Here is a good tutorial show you about Virtual Hosts and Wildcard SSL Certificates with Apache 2.2: In order for the certificate to be trusted, you need to obtain the certificate from a trusted certificate authority. Since we are using self-signed certificates, they are not trusted and we will see some warning messages. The data will still be encrypted. [...]</description>
		<content:encoded><![CDATA[<p>[...] Here is a good tutorial show you about Virtual Hosts and Wildcard SSL Certificates with Apache 2.2: In order for the certificate to be trusted, you need to obtain the certificate from a trusted certificate authority. Since we are using self-signed certificates, they are not trusted and we will see some warning messages. The data will still be encrypted. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Warwick</title>
		<link>http://www.cb1inc.com/2008/09/11/virtual-hosts-and-wildcard-ssl-certificates-with-apache-2-2/comment-page-1/#comment-114</link>
		<dc:creator>Warwick</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-114</guid>
		<description>The &quot;export&quot; command was truncated in the post above. Should have been:
&#160;  export SAN=&#039;DNS:[base-domain-name]&#039;
Eg,
&#160;  export SAN=&#039;DNS:site-a.com&#039;</description>
		<content:encoded><![CDATA[<p>The &#8220;export&#8221; command was truncated in the post above. Should have been:<br />
&nbsp;  export SAN=&#8217;DNS:[base-domain-name]&#8216;<br />
Eg,<br />
&nbsp;  export SAN=&#8217;DNS:site-a.com&#8217;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Warwick</title>
		<link>http://www.cb1inc.com/2008/09/11/virtual-hosts-and-wildcard-ssl-certificates-with-apache-2-2/comment-page-1/#comment-115</link>
		<dc:creator>Warwick</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-115</guid>
		<description>If you want browsers to be happy with the certificate when hitting the base domain (site-a.com), you might want to look at signing the certificate with a subjectAlternativeName set to the base domain as well.

My openssl.conf has &quot;subjectAltName=${ENV::SAN}&quot; in the [ usr_crt ] section, and I set the environment variable (eg &quot;export SAN=&#039;DNS:&lt;alt-domain-name&gt;&#039;&quot;) before running the openssl commands to create the certificate.</description>
		<content:encoded><![CDATA[<p>If you want browsers to be happy with the certificate when hitting the base domain (site-a.com), you might want to look at signing the certificate with a subjectAlternativeName set to the base domain as well.</p>
<p>My openssl.conf has &#8220;subjectAltName=${ENV::SAN}&#8221; in the [ usr_crt ] section, and I set the environment variable (eg &#8220;export SAN=&#8217;DNS:<alt -domain-name>&#8216;&#8221;) before running the openssl commands to create the certificate.</alt></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Barber</title>
		<link>http://www.cb1inc.com/2008/09/11/virtual-hosts-and-wildcard-ssl-certificates-with-apache-2-2/comment-page-1/#comment-121</link>
		<dc:creator>Chris Barber</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-121</guid>
		<description>I ran into a similar problem just the other day with redirects.  Your config looks good.  The problem was browser cache.  I had to empty my cache and restart my browser and then the redirects worked.
</description>
		<content:encoded><![CDATA[<p>I ran into a similar problem just the other day with redirects.  Your config looks good.  The problem was browser cache.  I had to empty my cache and restart my browser and then the redirects worked.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hackbard</title>
		<link>http://www.cb1inc.com/2008/09/11/virtual-hosts-and-wildcard-ssl-certificates-with-apache-2-2/comment-page-1/#comment-122</link>
		<dc:creator>hackbard</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-122</guid>
		<description>I configured my sites-enabled conf like yours, direkt SSL is working fine, but if I go to www.domain.com or xyz.domain.com I see a bad request (400) and a redirect to https://domain.com regardless what subdomain I used. (so the redirect is not working and www.domain.com didn&#039;t work too) only the direkt SSL will work like https://test.domain.com the wildcard certificate works well with the direkt SSL connection, so it have to be the config :hmm: I&#039;m not sure if the fcgi config have to be on every VirtualHost

  1 NameVirtualHost 84.200.208.192:80
  2 NameVirtualHost 84.200.208.192:443
  3
  4 &lt;VirtualHost 84.200.208.192:80 84.200.208.192:443&gt;
  5   ServerName suretodie.de
  6   ServerAlias www.suretodie.de
  7   ServerAdmin admin@suretodie.de
  8   DocumentRoot /var/www/web1/web/
  9
 10   &lt;IfModule mod_fcgid.c&gt;
 11       SuexecUserGroup web1 web1
 12       PHP_Fix_Pathinfo_Enable 1
 13       &lt;Directory /var/www/web1/web/&gt;
 14          Options +ExecCGI
 15          AllowOverride All
 16          AddHandler fcgid-script .php
 17          FCGIWrapper /var/www/php-fcgi-scripts/web1/php-fcgi-starter .php
 18             Order allow,deny
 19             Allow from all
 20       &lt;/Directory&gt;
 21    &lt;/IfModule&gt;
 22
 23 # ErrorLog /var/log/apache2/error.log
 24 # CustomLog /var/log/apache2/access.log combined
 25 ServerSignature Off
 26
 27 SSLEngine On
 28 SSLCertificateFile /etc/apache2/ssl/suretodie.crt
 29 SSLCertificateKeyFile /etc/apache2/ssl/suretodie.key
 30
 31 &lt;/VirtualHost&gt;
 32
 33 #Redirects
 34 # Not SSL, redirect to https://qmail.suretodie.de
 35 &lt;VirtualHost 84.200.208.192:80&gt;
 36     ServerName qmail.suretodie.de
 37     Redirect / https://qmail.suretodie.de/
 38 &lt;/VirtualHost&gt;
 39
 40 &lt;VirtualHost 84.200.208.192:80&gt;
 41     ServerName webmail.suretodie.de
 42     Redirect / https://webmail.suretodie.de/
 43 &lt;/VirtualHost&gt;
 44
 45
 46 &lt;VirtualHost 84.200.208.192:443&gt;
 47     ServerName qmail.suretodie.de
 48     ServerAdmin admin@suretodie.de
 49     DocumentRoot /var/www/web1/qmailad/
 50
 51    &lt;IfModule mod_fcgid.c&gt;
 52        SuexecUserGroup web1 web1
 53        PHP_Fix_Pathinfo_Enable 1
 54        &lt;Directory /var/www/web1/qmailad/&gt;
 55          Options +ExecCGI
 56          AllowOverride All
 57          AddHandler fcgid-script .php
 58          FCGIWrapper /var/www/php-fcgi-scripts/web1/php-fcgi-starter .php
 59          Order allow,deny
 60          Allow from all
 61        &lt;/Directory&gt;
 62    &lt;/IfModule&gt;
 63
 64 # ErrorLog /var/log/apache2/error.log
 65 # CustomLog /var/log/apache2/access.log combined
 66 ServerSignature Off
 67 &lt;/VirtualHost&gt;
 68
 69 &lt;VirtualHost 84.200.208.192:443&gt;
 70     ServerName webmail.suretodie.de
 71     ServerAdmin admin@suretodie.de
 72     DocumentRoot /var/www/web1/webmail/
 73
 74    &lt;IfModule mod_fcgid.c&gt;
 75        SuexecUserGroup web1 web1
 76        PHP_Fix_Pathinfo_Enable 1
 77        &lt;Directory /var/www/web1/webmail/&gt;
 78          Options +ExecCGI
 79          AllowOverride All
 80          AddHandler fcgid-script .php
 81          FCGIWrapper /var/www/php-fcgi-scripts/web1/php-fcgi-starter .php
 82          Order allow,deny
 83          Allow from all
 84       &lt;/Directory&gt;
 85    &lt;/IfModule&gt;
 86
 87 # ErrorLog /var/log/apache2/error.log
 88 # CustomLog /var/log/apache2/access.log combined
 89 ServerSignature Off
 90 &lt;/VirtualHost&gt;
</description>
		<content:encoded><![CDATA[<p>I configured my sites-enabled conf like yours, direkt SSL is working fine, but if I go to <a href="http://www.domain.com" rel="nofollow">http://www.domain.com</a> or xyz.domain.com I see a bad request (400) and a redirect to <a href="https://domain.com" rel="nofollow">https://domain.com</a> regardless what subdomain I used. (so the redirect is not working and <a href="http://www.domain.com" rel="nofollow">http://www.domain.com</a> didn&#8217;t work too) only the direkt SSL will work like <a href="https://test.domain.com" rel="nofollow">https://test.domain.com</a> the wildcard certificate works well with the direkt SSL connection, so it have to be the config :hmm: I&#8217;m not sure if the fcgi config have to be on every VirtualHost</p>
<p>  1 NameVirtualHost 84.200.208.192:80<br />
  2 NameVirtualHost 84.200.208.192:443<br />
  3<br />
  4 <virtualhost 84.200.208.192:80 84.200.208.192:443><br />
  5   ServerName suretodie.de<br />
  6   ServerAlias <a href="http://www.suretodie.de" rel="nofollow">http://www.suretodie.de</a><br />
  7   ServerAdmin <a href="mailto:admin@suretodie.de">admin@suretodie.de</a><br />
  8   DocumentRoot /var/www/web1/web/<br />
  9<br />
 10   <ifmodule mod_fcgid.c><br />
 11       SuexecUserGroup web1 web1<br />
 12       PHP_Fix_Pathinfo_Enable 1<br />
 13       <directory /var/www/web1/web/><br />
 14          Options +ExecCGI<br />
 15          AllowOverride All<br />
 16          AddHandler fcgid-script .php<br />
 17          FCGIWrapper /var/www/php-fcgi-scripts/web1/php-fcgi-starter .php<br />
 18             Order allow,deny<br />
 19             Allow from all<br />
 20<br />
 21    </ifmodule><br />
 22<br />
 23 # ErrorLog /var/log/apache2/error.log<br />
 24 # CustomLog /var/log/apache2/access.log combined<br />
 25 ServerSignature Off<br />
 26<br />
 27 SSLEngine On<br />
 28 SSLCertificateFile /etc/apache2/ssl/suretodie.crt<br />
 29 SSLCertificateKeyFile /etc/apache2/ssl/suretodie.key<br />
 30<br />
 31 </virtualhost><br />
 32<br />
 33 #Redirects<br />
 34 # Not SSL, redirect to <a href="https://qmail.suretodie.de" rel="nofollow">https://qmail.suretodie.de</a><br />
 35 <virtualhost 84.200.208.192:80><br />
 36     ServerName qmail.suretodie.de<br />
 37     Redirect / <a href="https://qmail.suretodie.de/" rel="nofollow">https://qmail.suretodie.de/</a><br />
 38 </virtualhost><br />
 39<br />
 40 <virtualhost 84.200.208.192:80><br />
 41     ServerName webmail.suretodie.de<br />
 42     Redirect / <a href="https://webmail.suretodie.de/" rel="nofollow">https://webmail.suretodie.de/</a><br />
 43 </virtualhost><br />
 44<br />
 45<br />
 46 <virtualhost 84.200.208.192:443><br />
 47     ServerName qmail.suretodie.de<br />
 48     ServerAdmin <a href="mailto:admin@suretodie.de">admin@suretodie.de</a><br />
 49     DocumentRoot /var/www/web1/qmailad/<br />
 50<br />
 51    <ifmodule mod_fcgid.c><br />
 52        SuexecUserGroup web1 web1<br />
 53        PHP_Fix_Pathinfo_Enable 1<br />
 54        <directory /var/www/web1/qmailad/><br />
 55          Options +ExecCGI<br />
 56          AllowOverride All<br />
 57          AddHandler fcgid-script .php<br />
 58          FCGIWrapper /var/www/php-fcgi-scripts/web1/php-fcgi-starter .php<br />
 59          Order allow,deny<br />
 60          Allow from all<br />
 61<br />
 62    </ifmodule><br />
 63<br />
 64 # ErrorLog /var/log/apache2/error.log<br />
 65 # CustomLog /var/log/apache2/access.log combined<br />
 66 ServerSignature Off<br />
 67 </virtualhost><br />
 68<br />
 69 <virtualhost 84.200.208.192:443><br />
 70     ServerName webmail.suretodie.de<br />
 71     ServerAdmin <a href="mailto:admin@suretodie.de">admin@suretodie.de</a><br />
 72     DocumentRoot /var/www/web1/webmail/<br />
 73<br />
 74    <ifmodule mod_fcgid.c><br />
 75        SuexecUserGroup web1 web1<br />
 76        PHP_Fix_Pathinfo_Enable 1<br />
 77        <directory /var/www/web1/webmail/><br />
 78          Options +ExecCGI<br />
 79          AllowOverride All<br />
 80          AddHandler fcgid-script .php<br />
 81          FCGIWrapper /var/www/php-fcgi-scripts/web1/php-fcgi-starter .php<br />
 82          Order allow,deny<br />
 83          Allow from all<br />
 84<br />
 85    </ifmodule><br />
 86<br />
 87 # ErrorLog /var/log/apache2/error.log<br />
 88 # CustomLog /var/log/apache2/access.log combined<br />
 89 ServerSignature Off<br />
 90 </virtualhost></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hackbard</title>
		<link>http://www.cb1inc.com/2008/09/11/virtual-hosts-and-wildcard-ssl-certificates-with-apache-2-2/comment-page-1/#comment-131</link>
		<dc:creator>hackbard</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-131</guid>
		<description>sry for that copy crap, here is a better pastebin
http://pastebin.com/m5a3d5201
you can delete my other post

&quot;I configured my sites-enabled conf like yours, direkt SSL is working fine, but if I go to www.domain.com or xyz.domain.com I see a bad request (400) and a redirect to https://domain.com regardless what subdomain I used. (so the redirect is not working and www.domain.com didn&#039;t work too) only the direkt SSL will work like https://test.domain.com the wildcard certificate works well with the direkt SSL connection, so it have to be the config :hmm: I&#039;m not sure if the fcgi config have to be on every VirtualHost&quot;

greets hackbard</description>
		<content:encoded><![CDATA[<p>sry for that copy crap, here is a better pastebin<br />
<a href="http://pastebin.com/m5a3d5201" rel="nofollow">http://pastebin.com/m5a3d5201</a><br />
you can delete my other post</p>
<p>&#8220;I configured my sites-enabled conf like yours, direkt SSL is working fine, but if I go to <a href="http://www.domain.com" rel="nofollow">http://www.domain.com</a> or xyz.domain.com I see a bad request (400) and a redirect to <a href="https://domain.com" rel="nofollow">https://domain.com</a> regardless what subdomain I used. (so the redirect is not working and <a href="http://www.domain.com" rel="nofollow">http://www.domain.com</a> didn&#8217;t work too) only the direkt SSL will work like <a href="https://test.domain.com" rel="nofollow">https://test.domain.com</a> the wildcard certificate works well with the direkt SSL connection, so it have to be the config :hmm: I&#8217;m not sure if the fcgi config have to be on every VirtualHost&#8221;</p>
<p>greets hackbard</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hackbard</title>
		<link>http://www.cb1inc.com/2008/09/11/virtual-hosts-and-wildcard-ssl-certificates-with-apache-2-2/comment-page-1/#comment-132</link>
		<dc:creator>hackbard</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-132</guid>
		<description>Hi Chris!

I checked it with deleted cache in IE and Firefox, the same as before. With the IE nothing is shown, no error, no redirect, no index :hmm:
In firefox the same as belwo shows up.

I don&#039;t get whats wrong :hmm:

my second domain shows the same error in FF, &quot;go to https://suretodie.de&quot;

:hmm:²</description>
		<content:encoded><![CDATA[<p>Hi Chris!</p>
<p>I checked it with deleted cache in IE and Firefox, the same as before. With the IE nothing is shown, no error, no redirect, no index :hmm:<br />
In firefox the same as belwo shows up.</p>
<p>I don&#8217;t get whats wrong :hmm:</p>
<p>my second domain shows the same error in FF, &#8220;go to <a href="https://suretodie.de" rel="nofollow">https://suretodie.de</a>&#8221;</p>
<p>:hmm:²</p>
]]></content:encoded>
	</item>
</channel>
</rss>

