On Thu, 27 Jan 2005, Daniel Stenberg wrote:

> It would thus be interesting to single-step through libcurl to see what it
> does after this read until it hangs.

Just did that, and I'm on to something!

The first SSL_read() libcurl does (when running this command line in my end)
fills the whole buffer (16383 bytes - there's one byte left to zero-terminate
with internally).

It then goes back to the poll/select and never gets any more data.

Now, fast-forward to the interesting part:

If you edit include/curl/curl.h and extend the buffer size WITH ONE BYTE. It
works just fine. You can extend it more than so, and it works fine too!

It seems that 16384 is a very bad match for this particular site/read. This
indicates:

1. OpenSSL bugs in this case.

and/or

2. libcurl doesn't use OpenSSL properly and it shows in this case.

I used this curl for testing:

curl 7.13.0-CVS (i686-pc-linux-gnu) libcurl/7.13.0-CVS OpenSSL/0.9.7e
zlib/1.2.2 libidn/0.5.2
Protocols: ftp gopher telnet dict ldap http file https ftps
Features: Debug GSS-Negotiate IDN IPv6 Largefile NTLM SSL libz

-- 
      Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
       Dedicated custom curl help for hire: http://haxx.se/curl.html