On Fri, Nov 06, 1998, [EMAIL PROTECTED] wrote:
> I have the same problem that Carlos Horowicz <[EMAIL PROTECTED]>
> reported in Bug Database and is with "analysed" status.
>
> What does "analysed" exactly means? Has it any position from the developers?
"analyzed" means your problem report was recognized and read by the author.
But because after trying to analyze the problem a solution or good answer is
still not known. So it still remains in the "analyzed" stage.
> My system has an apache 1.3.3 with mod_ssl 2.0.14...
>
> The same error has ocurred to me with MS Explorer 3.02 + Windows 95 (What
> a terrible combination...).
>
> error_log-ssl:
> [Thu Nov 5 19:36:37 1998] [error] mod_ssl: SSL_accept failed
> [Thu Nov 5 19:37:23 1998] [error] mod_ssl: SSL_accept failed
> ...
>
> What could it really means?
> It works fine with MS internet Explorer 4.01, Netscape 4.0 and 4.5...
This error messages can mean a lot. It just says that the SSL handshake failed
for SSLeay. Usually you should get an additional error line prefixed with
"SSLeay: " which says why it failed. I don't know why but there are
situations (like yours) where SSLeay's SSL_accept() fails but there is no
such SSLeay error message. In this case we can only guess the problem.
Typically it has to do with client certificates. So try to check your MSIE3
configuration. Perhaps it uses a bogus client cert or whatever. But I've no
MSIE3 available so I cannot test it myself.
When all fails: Try to run SSLeay's s_server on port 443 and connect to it via
both your MSIE3 and MSIE4 and look where the difference is. Perhaps this gives
some hints.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
