RE: FW: SSL_ERROR_SYSCALL

2002-11-18 Thread Fisk, Kevin
: [EMAIL PROTECTED] Subject: Re: FW: SSL_ERROR_SYSCALL On Mon, Nov 18, 2002 at 08:00:16AM -0800, Moffet, Scott wrote: > err is being set to -1 > SSL_get_error is returning SSL_ERROR_SYSCALL > errno is 11, EAGAIN > ERR_get_error is returning 0 In fact, SSL_ERROR_SYSCALL is the "catch

Re: FW: SSL_ERROR_SYSCALL

2002-11-18 Thread Lutz Jaenicke
On Mon, Nov 18, 2002 at 08:00:16AM -0800, Moffet, Scott wrote: > err is being set to -1 > SSL_get_error is returning SSL_ERROR_SYSCALL > errno is 11, EAGAIN > ERR_get_error is returning 0 In fact, SSL_ERROR_SYSCALL is the "catchall" message that is given when no other condition applies. > err is

RE: FW: SSL_ERROR_SYSCALL

2002-11-18 Thread Moffet, Scott
D] > Subject: Re: FW: SSL_ERROR_SYSCALL > > > On Fri, Nov 15, 2002 at 05:04:02PM -0800, Moffet, Scott wrote: > > After reading many of the archived messages, I see a common > question is the error return. It's -1. So, it's not just a > closed connection. It

Re: FW: SSL_ERROR_SYSCALL

2002-11-16 Thread Lutz Jaenicke
On Fri, Nov 15, 2002 at 05:04:02PM -0800, Moffet, Scott wrote: > After reading many of the archived messages, I see a common question is the error >return. It's -1. So, it's not just a closed connection. It's some sort of protocol >error. If a SSL_* function returns -1, it leaves a more detai