Does anyone have experience with wildcard SSL certs, like *.mycompany.com,
which could theoretically be installed on www1.mycompany.com,
www2.mycompany.com, etc? I am specifically wondering:
1) Are there compatibility problems with web server or web browser software?
2) Are they harder to work with in any other way than "normal" server certs?
I'm investigating this because I think I have a problem. Right now I have
server A and server B, each with an individual server cert. I have
ClusterCats failover set up, so if server A dies server B will assume A's IP
address. But the browser is still trying to connect to ServerA.com, and
server B doesn't have the right cert for that, so I predict chaos. But I
haven't tested it yet.
------------------------------------
Martin Herbener
Kentucky Department of Education
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body or visit the list page at www.houseoffusion.com
