Brian When you buy an SSL certificate, it will work for one domain only. Say you purchase the cert for www.mydomain.com if you were to go to https://www.mydomain.com all would be well. If however, you went to https://mydomain.com (without the www) you would get a security alert. The certs are very specific that way.
With that in mind, the problem with using SSL on vhosts is not a Sambar problem, it is simply a problem with how the certificates work. Here's how I run my vhosts off 1 SSL certificate using Sambar. Just use document mapping to map the directory of the vhost so it can be used with your main domain. if you host a site called host.com, just map it's document directory so you can use it with your main domain like https://www.mydomain.com/host.com/ That is pretty much how all the small mom and pop hosting companies do. Paul Alger Ironclad.net ----------------------- I have a couple of questions about SSL. With Sambar 5.3, is it still the case that SSL cannot be run with vhost? What are the alternatives? I'm thinking, to avoid the need of a second IP, to let the router send https traffic to a second server, set up exclusively for that purpose. Or . . . to a second concurrently running service (and NIC?) on the same server? Thanks for your help! Brian --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.532 / Virus Database: 326 - Release Date: 10/27/2003 ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/
