Thanks for the answer. 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.
I've added this<http://wiki.hcoop.net/DomTool/Examples#Allowingnon-secure.26secureconnectionwithsamebehaviour>to the DomTool examples page. Michael. On Fri, Jan 1, 2010 at 9:11 PM, Adam Chlipala <[email protected]> wrote: > Michael Shynar wrote: > > I am trying to allow secure alongside non-secure access to my website. > > (http[s]://shmichael.com <http://shmichael.com>) > > However, following the examples, it seems that adding the 'SSL = > > use_cert "/home/me/mycert.pem"' statement causes the non-secure > > http://shmichael.com to direct to the HCOOP front page. > > I've tried reading through DomTool manuals but I find it hard to > > understand the exact consequences of this statement. > > You need to define separate virtual hosts for the SSL and non-SSL > versions. If you had a single non-SSL vhost and just added an SSL > setting for it, then you will no longer have a non-SSL host. > > _______________________________________________ > HCoop-Help mailing list > [email protected] > https://lists.hcoop.net/listinfo/hcoop-help >
_______________________________________________ HCoop-Help mailing list [email protected] https://lists.hcoop.net/listinfo/hcoop-help
