[EMAIL PROTECTED] wrote:
> I have an application which is occasionally hanging. I have tracked it
> down to an SSL_shutdown call.
There is an issue with SSL_shutdown() on non-blocking sockets in respect
of knowing when to use the shutdown() call.
I'm not exactly sure if you have run into this
Hi,
Can you tell me, is this a bug in all versions, even OpenSSL 0.9.8i?
Solveig
On Sat, Oct 4, 2008 at 6:45 PM, David Schwartz <[EMAIL PROTECTED]> wrote:
>
> > Thank you for your response. I have checked the
> > error code using SSL_get_error.
>
> > I get an SSL_ERROR_SYSCALL (5) return code,
> Thank you for your response. I have checked the
> error code using SSL_get_error.
> I get an SSL_ERROR_SYSCALL (5) return code,
> indicating an I/O, but the error queue is empty.
> My application continues to function. It is fetching
> an HTML document over an HTTPS connection.
This is a docu
DS
Thank you for your response. I have checked the error code using
SSL_get_error.
I get an SSL_ERROR_SYSCALL (5) return code, indicating an I/O, but the
error queue is empty. My application continues to function. It is fetching
an HTML document over an HTTPS connection.
My concern is that, sin
Solveig Viste wrote:
> I have an application which is occasionally hanging.
> I have tracked it down to an SSL_shutdown call.
> The value (0) returned from the shutdown call indicates
> that the shutdown is not finished.
As happens with non-blocking sockets, sometimes the operation does not
com
I have an application which is occasionally hanging. I have tracked it down
to an SSL_shutdown call.
The value (0) returned from the shutdown call indicates that the shutdown is
not finished. The shutdown man page indicates that a second call to
SSL_shutdown should cause a bidirectional shutdown,
