I got a report that it works succesfully. This is what was tested: You can *.foo.com. This will work with www.foo.com, mail.foo.com but not secure.mail.foo.com
IE5.5 works this way Mozilla 1.3 will allow secure.mail.foo.com and mail.foo.com Mozilla will only complain with foo.com. This could have been fixed in newer versions of Mozilla if it is a bug. --Travis -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Jorgensen Sent: Friday, July 11, 2003 10:03 AM To: BYU Unix Users Group Subject: Re: [uug] Name-based SSL virtual hosting I've heard that wildcard certs don't work. I've seen problems with them in mozilla for instance. Travis Stevenson wrote: >>1) Buy (or license) 3 copies -- one for each machine -- of an SSL > > certificate for each virtual host. > > The certificate is matched by hostname. > > www.foo.com has to match www.foo.com in the certificate. If you do > subdomains than you can get a wildcard cert for *.foo.com > > > >>2) Have one IP address per virtual host. > > > Has to happen. The SSL connection is made before the virtualhost > entry is touched. > > >>We have thought to use a dedicated machine that would sit in front of >>the > > cluster and just > >>handle the SSL processing, but some employees here believe there is a > > better way. > > > Thanks, > Dan > > http://www.fastmail.fm > > ____________________ > BYU Unix Users Group > http://uug.byu.edu/ > ___________________________________________________________________ > List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list > > > ____________________ > BYU Unix Users Group > http://uug.byu.edu/ > ___________________________________________________________________ > List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list > ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
