In some situations it does work (a little mysteriously IMO). For example, I have these in my private home server and it does work correctly (verified extensively):<div><br></div><div><VirtualHost *:443></div><div>DocumentRoot /var/www</div>
<div>ServerName <a href="http://app1.home.mysite.com" target="_blank">app1.home.mysite.com</a></div><div>SSLCertificateFile app1cert.crt</div><div>... (other SSL directives)</div><div><br></div><div>and:</div><div><br></div>
<div><VirtualHost _default_:443></div>
<div><div>DocumentRoot /var/www</div><div>ServerName <a href="http://home.mysite.com" target="_blank">home.mysite.com</a></div><div>SSLCertificateFile homecert.crt</div><div>... (other SSL directives)</div></div><div><br>
</div><div>It works correctly for both <a href="http://app1.home.mysite.com" target="_blank">app1.home.mysite.com</a> and <a href="http://home.mysite.com" target="_blank">home.mysite.com</a>. And app1 does not work when I remove the *:443 virtualhost.</div>
<div><br></div><div>Furthermore, SSL will most certainly work, even in principle, if you use one wildcard subdomain certificate in conjunction with multiple virtualhosts. What you cannot do is put two SSL directives in one virtualhost, in which case the second is ignored.</div>
<div><br></div><div>However, in the original topic, the server in question used IP:Port to identify the virtualhosts so he could not use this technique.</div><div><br></div><div>--Mizst<br><br></div><div><br><div class="gmail_quote">
On Fri, May 13, 2011 at 6:40 PM, Randall Rowe <span dir="ltr"><<a href="mailto:r.rowe@lincolnlibraries.org" target="_blank">r.rowe@lincolnlibraries.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Direct from <a href="http://httpd.apache.org/docs/2.0/ssl/ssl_faq.html" target="_blank">Apache.org SSL FAQ</a><br>
<br>
<h3><a name="12fe9f351ef288d0_12fe928a065eac44_vhosts2">Why is it not possible to use Name-Based
Virtual Hosting to identify different SSL virtual hosts?</a></h3>
<p>Name-Based Virtual Hosting is a very popular method of identifying
different virtual hosts. It allows you to use the same IP address and
the same port number for many different sites. When people move on to
SSL, it seems natural to assume that the same method can be used to have
lots of different SSL virtual hosts on the same server.</p>
<p>It comes as rather a shock to learn that it is impossible.</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 does not contain any Host:
field, the server has no way to decide which SSL virtual host to use.
Usually, it will just use the first one it finds, which matches the
port and IP address specified.</p>
<p>You can, of course, use Name-Based Virtual Hosting to identify many
non-SSL virtual hosts (all on port 80, for example) and then
have a single SSL virtual host (on port 443). But if you do this,
you must make sure to put the non-SSL port number on the NameVirtualHost
directive, e.g.</p>
<div>
<p><code>
NameVirtualHost <a href="http://192.168.1.1:80" target="_blank">192.168.1.1:80</a>
</code></p>
</div>
<p>Other workaround solutions include: </p>
<p>Using separate IP addresses for different SSL hosts.
Using different port numbers for different SSL hosts.</p>
<br>
<br>
<p>Randy Rowe<br>
Lincoln City Libraries I.T.<br>
<br>
<br>
</p>
<br>
<br>
-----Original Message-----<br>
From: "Martin Renvoize" <<a href="mailto:martin.renvoize@ptfs-europe.com" target="_blank">martin.renvoize@ptfs-europe.com</a>><br>
Sent 5/13/2011 3:33:09 AM<br>
To: "Mizst Audens" <<a href="mailto:mizstik@gmail.com" target="_blank">mizstik@gmail.com</a>><br>
Cc: <a href="mailto:koha@lists.katipo.co.nz" target="_blank">koha@lists.katipo.co.nz</a><br>
Subject: Re: [Koha] Enabling SSL for Koha staff view<div><div></div><div><br>
<br>
You could however,
<div><br>
</div>
<div>Use Name based Virtualhosts (like <a href="http://kohaapoc.yourlibrary.com" target="_blank">kohaapoc.yourlibrary.com</a> and <a href="http://kohastaff.yourlibrary.com" target="_blank">kohastaff.yourlibrary.com</a>) and run both on port 443 for secure. To do this you'll either need two certificates (one for each domain) or a SAN shared certificate with both domain names in it.</div>
<div><br>
</div>
<div>An example http.conf might look like (assuming the two certificate approach);</div>
<div><br>
</div>
<div>
<div>## OPAC Default Access</div>
<div><VirtualHost <a href="http://127.0.1.1:80" target="_blank">127.0.1.1:80</a>></div>
<div> DocumentRoot /home/koha/kohaclone/koha-tmpl</div>
<div> ServerName <a href="http://kohalibrary.halton.gov.uk" target="_blank">kohalibrary.halton.gov.uk</a></div>
</div>
<div> . . . </div>
<div>
<div></VirtualHost></div>
<div>
<br>
</div>
<div>## OPAC Secure</div>
<div><VirtualHost <a href="http://127.0.1.1:443" target="_blank">127.0.1.1:443</a>></div>
<div> DocumentRoot /home/koha/kohaclone/koha-tmpl</div>
<div> ServerName <a href="http://kohalibrary.halton.gov.uk" target="_blank">kohalibrary.halton.gov.uk</a></div>
</div>
<div> . . .</div>
<div><br>
</div>
<div>
<div># SSL Setup</div>
<div># CA Root and Intermediate Certificates</div>
<div> SSLEngine On</div>
<div> SSLCACertificatePath /etc/apache2/ssl/certs/</div>
<div> SSLCACertificateFile /etc/apache2/ssl/certs/gs_combined_ca.crt</div>
<div><br>
</div>
<div> SSLCertificateFile /etc/apache2/ssl/certs/kohalibrary.crt</div>
<div> SSLCertificateKeyFile /etc/apache2/ssl/certs/kohalibrary.key</div>
<div><br>
</div>
<div></VirtualHost></div>
</div>
<div><br>
</div>
<div>
<div>## Intranet Secure</div>
<div><VirtualHost <a href="http://109.75.173.120:443" target="_blank">109.75.173.120:443</a>></div>
<div> DocumentRoot /home/koha/kohaclone/koha-tmpl</div>
<div> ServerName <a href="http://kohastaff.halton.gov.uk" target="_blank">kohastaff.halton.gov.uk</a></div>
</div>
<div> . . . </div>
<div>
<div># SSL Setup</div>
<div># CA Root and Intermediate Certificates</div>
<div> SSLEngine On</div>
<div> SSLCACertificatePath /etc/apache2/ssl/certs/</div>
<div> SSLCACertificateFile /etc/apache2/ssl/certs/gs_combined_ca.crt</div>
<div><br>
</div>
<div> SSLCertificateFile /etc/apache2/ssl/certs/kohastaff.crt</div>
<div> SSLCertificateKeyFile /etc/apache2/ssl/certs/kohastaff.key</div>
<div></VirtualHost></div>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
<div class="gmail_quote">2011/5/8 Mizst Audens <span dir="ltr"><<a href="mailto:mizstik@gmail.com" target="_blank">mizstik@gmail.com</a>></span><br>
<blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid #cccccc;padding-left:1ex" class="gmail_quote">
<div>No, it's not possible due to the limitation of the architecture. A port can serve only http or https but not both at the same time.</div>
<div><br>
</div>
<div>The transparency of http/https in normal websites is due to the standardization of port 80 and 443. (port 80 runs http, and port 443 runs https, so each port only runs one type of connection) When you don't use these standard ports, you will need to specify the correct combination of protocol and port in order to reach a service.</div>
<div><br>
</div>
<span style="color:#888888">
<div>--Mizst</div>
</span>
<div>
<div></div>
<div><br>
<br>
<div class="gmail_quote">On Sun, May 8, 2011 at 12:33 PM, Altaf Mahmud <span dir="ltr"><<a href="mailto:altaf.mahmud@gmail.com" target="_blank">altaf.mahmud@gmail.com</a>></span> wrote:<br>
<blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid #cccccc;padding-left:1ex" class="gmail_quote">
Is it possible to use port 8080 for both purposes (HTTP and HTTPS)? Actually, I just wanted to secure port 8080, can I do that?<br>
<br>
Thanks a lot!
<div>
<div></div>
<div><br>
<br>
<div class="gmail_quote">On Sat, May 7, 2011 at 8:34 PM, Mizst Audens <span dir="ltr"><<a href="mailto:mizstik@gmail.com" target="_blank">mizstik@gmail.com</a>></span> wrote:<br>
<blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid #cccccc;padding-left:1ex" class="gmail_quote">You must create another virtual host at another port (for example, 8081) for the staff area and enable SSL for that virtual host, and it will require another SSL certificate. Your staff will need to use (example) <a href="https://127.0.1.1:8081" target="_blank">https://127.0.1.1:8081</a> if they want to use SSL, and <a href="http://127.0.1.1:8080" target="_blank">http://127.0.1.1:8080</a> if they don't want to use SSL.
<div>
<br>
</div>
<div>Note that <a href="https://127.0.1.1" target="_blank">https://127.0.1.1</a> is in fact an alias for <a href="https://127.0.1.1:443" target="_blank">https://127.0.1.1:443</a>. You already used 443 for the OPAC, so you'll need another port for the staff.<br>
<div><br>
</div>
<div>--Mizst<br>
<div><br>
<br>
<div class="gmail_quote">
<div>
<div></div>
<div>2011/5/7 Altaf Mahmud <span dir="ltr"><<a href="mailto:altaf.mahmud@gmail.com" target="_blank">altaf.mahmud@gmail.com</a>></span><br>
</div>
</div>
<blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid #cccccc;padding-left:1ex" class="gmail_quote">
<div>
<div></div>
<div>
Hello,<br>
<br>
I'm trying to implement SSL in my Koha server running on Debian 6.0 (squeeze). I've implemented it for my OPAC view, I've created another file 'koha-ssl' in ../apache2/sites-available/ directory and enabled it. I've edited ../apache2/sites-available/koha like following:<br>
<br>
NameVirtualHost *:80<br>
<VirtualHost <a href="http://127.0.1.1:80" target="_blank">127.0.1.1:80</a>><br clear="all">
<br>
.....<br>
.....<br>
<br>
</VirtualHost><br>
<br>
And ../apache2/sites-available/koha-ssl like following:<br>
<br>
NameVirtualHost *:443<br>
<VirtualHost <a href="http://127.0.1.1:443" target="_blank">127.0.1.1:443</a>><br>
.....<br>
<br>
SSLEngine On<br>
SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem<br>
SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key<br>
<br>
.....<br>
</VirtualHost><br>
<br>
Now <a href="https://127.0.1.1/" target="_blank">https://127.0.1.1/</a> is showing the OPAC. But I can't figure it out how to implement it for staff-view <VirtualHost <a href="http://127.0.1.1:8080" target="_blank">127.0.1.1:8080</a>> <br>
Request for port 80 is redirecting to port 443, how can I do that for port 8080? In fact, I don't have any prior idea on doing this; a descriptive suggestion is appropriate for me.<br>
<br>
Thanks.<br>
<span style="color:#888888"><br>
<br>
<br>
-- <br>
Altaf Mahmud<br>
System Programmer<br>
Ayesha Abed Library<br>
BRAC University<br>
Bangladesh.<br>
<br>
</span><br>
</div>
</div>
_______________________________________________<br>
Koha mailing list <a href="http://koha-community.org" target="_blank">http://koha-community.org</a><br>
<a href="mailto:Koha@lists.katipo.co.nz" target="_blank">Koha@lists.katipo.co.nz</a><br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>
<br>
</blockquote></div>
<br>
</div>
</div>
</div>
</blockquote></div>
<br>
<br clear="all">
<br>
-- <br>
Altaf Mahmud<br>
System Programmer<br>
Ayesha Abed Library<br>
BRAC University<br>
Bangladesh.<br>
<br>
</div>
</div>
</blockquote></div>
<br>
</div>
</div>
<br>
_______________________________________________<br>
Koha mailing list <a href="http://koha-community.org" target="_blank">http://koha-community.org</a><br>
<a href="mailto:Koha@lists.katipo.co.nz" target="_blank">Koha@lists.katipo.co.nz</a><br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>
<br>
</blockquote></div>
<br>
<br clear="all">
<br>
-- <br>
<div>Martin Renvoize</div>
<div>Software Developer, PTFS Europe Ltd</div>
<div>Content Management and Library Solutions</div>
<div><a href="mailto:martin.renvoize@ptfs-europe.com" target="_blank">martin.renvoize@ptfs-europe.com</a></div>
<div>skype: Martin Renvoize</div>
<div><br>
</div>
<div><a href="http://www.ptfs-europe.com" target="_blank">http://www.ptfs-europe.com</a></div>
<br>
</div>
<pre>_______________________________________________
Koha mailing list <a href="http://koha-community.org" target="_blank">http://koha-community.org</a>
<a href="mailto:Koha@lists.katipo.co.nz" target="_blank">Koha@lists.katipo.co.nz</a>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a>
</pre></div></div></blockquote></div><br></div>