Re: SslLib timeout: SslWrite timeout after timed out SslRead Proble

Hello

Did you reslove your problem?

I have the similar problem. I am using non-blocking sockets. I set the
socket to non-blocking right after the SSL session is established.

I have no problems in sequential calls to SslWrite(). First invoke of
SslRead() reads the incoming data. But every next call to SslRead() and
SslWrite() return -1 and error is set to netErrWouldBlock.

If you call SslRead() with buffer's length _equal_ to the data received
you will not face this problem.

If you are sure that there is a data in the socket you can you SslPeek()
and SslConsume() to implement read operation. But if you call SslPeek()
over an empty buffer you will face again the problem as when you use
SslRead().
Maybe it is because when SslPeek() is called over an empty buffer this
cause read operation over the socket. And the problems come again!