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 -----Original Message----- From: Rick Faircloth [mailto:[EMAIL PROTECTED] Sent: Monday, August 07, 2006 10:32 PM To: CF-Talk Subject: RE: SSL Certificates > I see. That would only work if your sites were within the same domain, however. Are you certain about that, Dave? I didn't see anything in the text that would indicate all the sites had to be part of the same domain...I now wildcard certs seem to work that way now, but perhaps it's different in Win 2003 Server and IIS 6? Rick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:249124 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
