I'm sorry to say that there is still a problem.
first I said:
>
>
> >During the handshaking, the client reports that the name on the
> >certificate does not
> >match the name of the site. I have tried generating certificates for
> >blah.com, mail.blah.com and www.blah.com and the same warning is
> generated
> >in each case. Any tip on how to configure SSL to avoid this warning will
> >expose my sincere gratitude.
>
Then Scott replied:
> The domain on the certificate needs to match the domain name that is
> entered in the browser. For example, if your users go to
> "http://mail.example.com";, you would need to use mail.example.com.
>
> -Scott
It does match, although there is a slight problem. When you enter
http://www.blah.com:8383 and select the "enter secure mode" option, Imail
tries to go to "https:\blah.com:8384/lots of other stuff" and so we get a
"page cannot be displayed" error since there is (yet) no A record for
blah.com (that's in the process of being fixed, it says here). However one
can manually edit the url to add the "www" part and the old problem
reappears. Even when the name on the certificate is blah.com, www.blah.com
or ever blah.com:8384 or www.blah.com:8384, the complaint that the the name
on the certificate does not match the name on the site still happens. I'd be
much obliged to anybody who can provide some insight into this.
Many advance thanks.
Peter Schotch
--
Dr. Peter Schotch
Webmaster, RPost Inc.
[voice] (902) 852-4103
[fax] (561) 619-5942
[email] [EMAIL PROTECTED]
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
