This one has me stumped and rather frustrated. The problem
happens with MSIE 5.0.2314.1003 but not with netscape 4.76.
I have a site, in testing, which for various reasons is
accessed by going to a particular URL in a directory
with a .htaccess file in it. Let's say:
https://my.test.site/keepaway/login.htm
Our server certificate for the site is not for our domain.
This is because the test site
With Netscape, if I do https://.../... or http://.../...
I get the username/password basic authentication
challenge. However, under https I get a warning to the
effect that the cert isn't for the domain. Fair enough.
With MSIE, I only get the challenge with http://.../...,
whereas with https://.../... I get a "friendly" error.
Once I do a mod_auth basic authentication against http,
if I replace http with https I get the "friendly" error
message back.
I suspect that MSIE barfs because the domain of the
certificate doesn't match the domain in the URL. Is
this correct, and is there a workaround?
Probably irrelevant, but
.htacess contains something like:
Deny from all
Allow from 1.2.3.4
AuthType Basic
AuthName "My Test Site"
AuthUserFile /etc/httpd/conf/auth/valid.users
require valid-user
satisfy all
Thanks,
Adam.
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
