On Tue, May 23, 2000 at 02:32:19PM +0200, Sander Alberink wrote:
> Hi,
>
> We are using libwww-ssl to fetch pages from secure webservers on the
> internet, but we find that there are some problems in the way this happens.
> Since requests failed in strange ways, we conducted tests to see where the
> connection attempts failed. After increasing the logging using in libwww, it
> became obvious that it was the SSL connect stage that failed every time.
> Further investigation revealed that this problem appears only when the
> connect was done using a non-blocking socket.
> Searching the mailing-lists, it seemed that we are not the only ones having
> problems using OpenSSL/libwwwssl with non-blocking sockets. Did anybody
> verify whether or not there is a bug in OpenSSL regarding SSL_connect on a
> nonblocking socket?
It is always dangerous to say that there is no bug because somebody may
prove you wrong later.
Having this said: are you aware of the fact that the programming interface
changes when using non-blocking sockets? You may have to call SSL_connect
several times in a row and check the error code, since SSL_connect will
also lose its blocking behaviour.
Details have been discussed on the openssl-* mailings lists in the recent
past. Please check the mailing-list archives and search for "non-blocking"
or e.g. SSL_ERROR_WANT_READ (a typical state that occurs during non-blocking
I/O).
Best regards,
Lutz
--
Lutz Jaenicke [EMAIL PROTECTED]
BTU Cottbus http://www.aet.TU-Cottbus.DE/personen/jaenicke/
Lehrstuhl Allgemeine Elektrotechnik Tel. +49 355 69-4129
Universitaetsplatz 3-4, D-03044 Cottbus Fax. +49 355 69-4153
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
