<div dir="ltr">Thanks for the answer.<br><br>If I understand correctly, the solution would be to replicate the web directive and add the 'SSL =' statement to the copy. This indeed works. If there is a more elegant way, I'd be happy to know.<br>
<br>I've <a href="http://wiki.hcoop.net/DomTool/Examples#Allowingnon-secure.26secureconnectionwithsamebehaviour">added this</a> to the DomTool examples page.<br><br>Michael.<br><br><div class="gmail_quote">On Fri, Jan 1, 2010 at 9:11 PM, Adam Chlipala <span dir="ltr"><<a href="mailto:adamc@hcoop.net">adamc@hcoop.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">Michael Shynar wrote:<br>
> I am trying to allow secure alongside non-secure access to my website.<br>
</div>> (http[s]://<a href="http://shmichael.com" target="_blank">shmichael.com</a> <<a href="http://shmichael.com" target="_blank">http://shmichael.com</a>>)<br>
<div class="im">> However, following the examples, it seems that adding the 'SSL =<br>
> use_cert "/home/me/mycert.pem"' statement causes the non-secure<br>
> <a href="http://shmichael.com" target="_blank">http://shmichael.com</a> to direct to the HCOOP front page.<br>
> I've tried reading through DomTool manuals but I find it hard to<br>
> understand the exact consequences of this statement.<br>
<br>
</div>You need to define separate virtual hosts for the SSL and non-SSL<br>
versions. If you had a single non-SSL vhost and just added an SSL<br>
setting for it, then you will no longer have a non-SSL host.<br>
<br>
_______________________________________________<br>
HCoop-Help mailing list<br>
<a href="mailto:HCoop-Help@lists.hcoop.net">HCoop-Help@lists.hcoop.net</a><br>
<a href="https://lists.hcoop.net/listinfo/hcoop-help" target="_blank">https://lists.hcoop.net/listinfo/hcoop-help</a><br>
</blockquote></div><br></div>