> (they need to create a ptr record for 216.122.43.95
> that resolves to your web site name)
Thanks for this tip. It really did seem to resolve the problem. Apparently
the AOL HTTPS code does the reverse lookup to see if the hostname for the
specified IP address matches.
What's interesting, of course, is that this is not been a problem for any
browser we've tested before we ran into the AOL issue. And the concept
seems broken, though, as a means of making SSL work. Most reverse IP
addresses point to the real host name which is often different than name of
the web server. After all, something as simple as www.yozons.com may be
routed to several different IP addresses (based on DNS round robin), and
many computers have multiple names and don't name their server 'www'. 'www'
is just the name of the web server application running on a computer that
may also do email or other applications.
It also means that if I want to run HTTPS on port 443 as well as another on
port 4430 (since SSL doesn't really work for virtual domain naming in
Apache), that there would be a problem because only one IP address exists
and I've got two web servers running using different names.
Anyway, thanks so much for helping us troubleshoot this. It was a real
mystery why we could have so many testers hit our site just fine, but
couldn't get AOL to connect at all.
David
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
