On Wed, Jan 31, 2007, Ian Fette wrote:
Sometimes a SSL_read() operation on toClientSSL will return 0, and
SSL_get_error yields SSL_ERROR_SYSCALL, and if I look at errno (from
errno.h) it's set to EWOULDBLOCK. I had thought that if something was
going to block, SSL_get_error would return
Dr. Stephen Henson wrote:
On Wed, Jan 31, 2007, Ian Fette wrote:
Sometimes a SSL_read() operation on toClientSSL will return 0, and
SSL_get_error yields SSL_ERROR_SYSCALL, and if I look at errno (from
errno.h) it's set to EWOULDBLOCK. I had thought that if something was
going to block,
On Wed, Jan 31, 2007, Ian C. Fette wrote:
I also tried implementing your reply. Before calling SSL_read() etc I'm
now calling ERR_clear_error(). Unfortunately, I still seem to be getting
cases where I see SSL_ERROR_SYSCALL and errno is set to EWOULDBLOCK. Do
you have any other ideas as to
Dr. Stephen Henson wrote:
On Wed, Jan 31, 2007, Ian C. Fette wrote:
I also tried implementing your reply. Before calling SSL_read() etc I'm
now calling ERR_clear_error(). Unfortunately, I still seem to be getting
cases where I see SSL_ERROR_SYSCALL and errno is set to EWOULDBLOCK. Do
you
Ian C. Fette wrote:
Dr. Stephen Henson wrote:
On Wed, Jan 31, 2007, Ian C. Fette wrote:
I also tried implementing your reply. Before calling SSL_read() etc I'm
now calling ERR_clear_error(). Unfortunately, I still seem to be getting
cases where I see SSL_ERROR_SYSCALL and errno is set to
I have what I hope to be a relatively simple question regarding
SSL_read/write/etc operations on nonblocking sockets, and the errors
they return. I would like to preface this by saying that I have spent
hours scouring google and also searching the archives and I haven't
really found an answer,
