So...is the final answer to our discussion that I can use regular (not wildcard certs) for a single domain on Win 2003 Server using host headers, but I have to purchase an individual cert for each domain? (Regular certs are cheap and I can pass that on to each client without any heartburn over the cost to secure transmissions)
I don't need a wildcard cert, I don't think, because each domain has just one version...in other words, no subdomains. Would this be correct? Rick -----Original Message----- From: Dawson, Michael [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 08, 2006 6:37 AM To: CF-Talk Subject: RE: SSL Certificates I would agree with Dave that a wildcard works for only one domain. Ours, basically, is *.evansville.edu. As long as we host any ...evansville.edu site, we can secure it. If we add another domain, such as newdomain.edu, we would need to purchase another wildcard cert. Go to https://cce.evansville.edu. Then, examine the cert. You will see that the Common Name is *.evansville.edu. It cannot work with another domain. BTW, my prior post that said certs work with host headers was somewhat misleading. This CCE web site does have it's own IP address, but it is also on a server that is using host headers. If a site with host headers is called with HTTPS, then you get the warning, but it works perfectly with regular HTTP. Sorry for the confusion. M!ke ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:249131 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
