Bodo Moeller via RT wrote:
>Ralph via RT <[EMAIL PROTECTED]>:
>
>
>
>>But so far, I can tell you that when SSL_get_error() returns
>>SSL_ERROR_SYSCALL and you inspect errno, it tells EWOULDBLOCK or EAGAIN.
>>By repeating the SSL_* call as long as this condition occurs, I can
>>overcome th
> >>Methods SSL_connect(), SSL_read() and SSL_write() should return
> >>SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE if they need to complete
> >>their tasks but the socket couldn't handle all the work.
> >>
> >>But instead, the methods return SSL_ERROR_SYSCALL when the underlying
> >>socket gave
Ralph via RT <[EMAIL PROTECTED]>:
> But so far, I can tell you that when SSL_get_error() returns
> SSL_ERROR_SYSCALL and you inspect errno, it tells EWOULDBLOCK or EAGAIN.
> By repeating the SSL_* call as long as this condition occurs, I can
> overcome the problem and the SSL handshake and co
Bodo Moeller via RT wrote:
>On Wed, Feb 19, 2003 at 06:10:13PM +0100, Ralph via RT wrote:
>
>
>
>>on AIX (64bit) I noticed a major problem with non-blocking sockets.
>>Methods SSL_connect(), SSL_read() and SSL_write() should return
>>SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE if they need
On Wed, Feb 19, 2003 at 06:10:13PM +0100, Ralph via RT wrote:
> on AIX (64bit) I noticed a major problem with non-blocking sockets.
> Methods SSL_connect(), SSL_read() and SSL_write() should return
> SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE if they need to complete
> their tasks but the soc
Hi,
on AIX (64bit) I noticed a major problem with non-blocking sockets.
Methods SSL_connect(), SSL_read() and SSL_write() should return
SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE if they need to complete
their tasks but the socket couldn't handle all the work.
But instead, the methods return
