We use wildcard certs with 3.0.18Pro and 3.1.6Pro (JSSE and 32bit) without problems.
If only we could correctly limit the cipher suites. http://bugs.caucho.com/view.php?id=3431 (which is a reopen of) http://bugs.caucho.com/view.php?id=2360 Scott or Emil, either of you had a chance to review my suggested changes, yet? + jay Rob Lockstone wrote: > Does anyone know if Resin (Pro 3.1.9 64-bit with OpenSSL) would have > any problems handling a wildcard ssl certificate, as opposed to a > domain specific cert, e.g. *.blahblah.com vs. poolOne.blahblah.com, > poolTwo.blahblah.com, poolThree.blahblah.com. > > We're considering getting one because a few of our pools require ssl > and it's easier to manage, though more expensive, to get just one > certificate for all of them rather than deal with multiple different > certs for the different pools (i.e. remembering to renew them and make > sure they're deployed, etc). > > We know it works with IIS, but have never tried a wildcard cert with > Resin and OpenSSL. I wouldn't anticipate there being a problem, but > obviously we'd rather not spend the money only to find out it won't > work for some reason. Anyone know? > > Rob > > > > _______________________________________________ > resin-interest mailing list > [email protected] > http://maillist.caucho.com/mailman/listinfo/resin-interest _______________________________________________ resin-interest mailing list [email protected] http://maillist.caucho.com/mailman/listinfo/resin-interest
