On Tue, 29 Jan 2002, Andrew Pollock wrote: > On 29.01.2002 at 11:12:02, "Julian C. Dunn" <[EMAIL PROTECTED]> wrote: > > > Nope... there's no more to it than that. At least that's the experience > > I've had. Apache will complain (warn) that your CN doesn't match the name > > of the server, but everything works fine. I'm using Apache 1.3.12 with > > modssl 2.6.6. > > Hmm, I'm not aware of any complaints from Apache, however Internet > Explorer (6) is complaining that the name on the certificate doesn't > match the hostname...
Is that when you go to https://sitename.com as opposed to https://www.sitename.com/? In the former case, I believe the wildcard will not work because there is nothing for the "*" to match. Of course, you could just write a mod_rewrite rule (or use another such mechanism) to force people to use the latter version. - Julian -- Julian C. Dunn, B.A.Sc <[EMAIL PROTECTED]> Senior Software Developer, VerticalScope Inc. Tel.: (416) 341-8950 x236 Fax: (416) 341-8959 WWW: www.verticalscope.com "Windows NT encountered the following error: The operation was completed successfully." ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
