Simple nonblocking client produces SSL_R_UNINITIALIZED

I'm trying to add nonblocking https client-side retrieval to my application. I'm getting an SSL_ERROR_SSL when I run it, after calling SSL_write() for the first time, when the handshake needs to occur. The error queue provides reason 276: SSL_R_UNINITIALIZED (see ssl_lib.c:733), because handsh

Re: Simple nonblocking client produces SSL_R_UNINITIALIZED

Thanks for the attempt -- but it was a typo in the message -- my source code does properly use ||. Any other ideas? Thanks, David At 09:44 AM 8/3/00 -0700, you wrote: >Didn't look carefully enough, so I'm not sure if I hit anything useful, but >I found something that looks like a typo. > > > i

Re: Simple nonblocking client produces SSL_R_UNINITIALIZED

Didn't look carefully enough, so I'm not sure if I hit anything useful, but I found something that looks like a typo. > if ((!SSL_CTX_load_verify_locations(_contextPtr, _caFilePtr, _caFilePathPtr)) | > (!SSL_CTX_set_default_verify_paths(_contextPtr))) '|' should probably be '||'. -

Simple nonblocking client produces SSL_R_UNINITIALIZED

I'm trying to add nonblocking https client-side retrieval to my application. I'm getting an SSL_ERROR_SSL when I run it, after calling SSL_write() for the first time, when the handshake needs to occur. The error queue provides reason 276: SSL_R_UNINITIALIZED (see ssl_lib.c:733), because handsh