I am having a problem using libcurl when talking to an IIS 5.0 server.

Basically I am using an SSL connection and sending a post request. The
response is application/octet-stream data. Everything works great
until the response is greater than 64K at which point I get a 500
Server error from IIS. Other web browsers can access this data without
problems.

It looks like that libcurl package closes the socket after getting an
SSL read error, which triggers the IIS response.

I have tried this with 7.9.8 and 7.10.3 and both fail in the same way.

-kevin

-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your
clients even if they use browsers that are limited to 40 bit encryption.
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
Received on 2003-01-18