Hi,
I did some more testing and it looks that this error has nothing to do with
cURL so I'll check with the OpenSSL developers

Just for informtaion.

The openssl command I used initially was 0.9.6 and not 0.9.7 as I thought.

When I tried openssl s_client -connect ... with openssl newer the 0.9.6h
the connection to the server was closed imediately after sending the request
and no data is received back.

I also noticed that when this happens cURL waits for several minutes before
returning the error message. May be a check should be added to see if there
is data available for reading after sending the request headers to the HTTPS
server to avoid this.

Dobromir Velev

----- Original Message -----
From: "Daniel Stenberg" <daniel_at_haxx.se>
To: "libcurl Mailing list" <curl-library_at_lists.sourceforge.net>
Sent: Wednesday, April 30, 2003 19:48
Subject: Re: SSL read error: 5

> On Wed, 30 Apr 2003, Dobromir Velev wrote:
>
> > I have some problems opening some HTTPS URLs using libcurl/7.10.3
> > OpenSSL(0.9.7) on RedHat 6.2
>
> > There were no problems when I tried to open the same page with
> >
> > curl 7.10.3 OpenSSL 0.9.6
> > curl 7.10.3 OpenSSL 0.9.6b
> >
> > or using the OpenSSL interface
> >
> > openssl s_client ....
>
> When you used the s_client thing, did you try the openssl version 0.9.7
then?
> The same that failed with curl 7.10.3?
>
> > Please let me know if you need more information to check this problem
>
> The same curl version fails to function when you use 0.9.7 and works when
you
> use 0.9.6b?
>
> --
> Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
>

-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
Received on 2003-05-07