>> CURL DEBUG TEXT: transfer closed with outstanding read data remaining

>Ahah, I posted too soon--I assume this is the problem. A fix went in a
>couple of weeks ago for a case similar to this to deal with a race
>condition where a persistent connection is closed at the same time that a
>new request goes out over the wire. Try building against the latest
>daily snapshot curl build and see if the problem is solved.

>>> Dan

Dan,

thanks for your answer. Guess I should have been clear on what the
actual error was...
The problem is that curl_easy_perform returns CURLE_PARTIAL_FILE.

I tried it again today with daily snapshot 7.19.1-20081017 but got the
same result.
I don't have more than one connection open and I use the easy interface.

I guess the strange part is the following:

After the headers are sent the following headers are returned:
HTTP/1.1 100 Continue
Content-Length: 0

then I send the data and get the following headers back:

HTTP/1.1 200 OK
Content-Encoding: gzip
Server:
Content-Type: text/xml; charset=utf-8
Transfer-Encoding: chunked
Date: Sat, 18 Oct 2008 00:57:19 GMT

Then all of a sudden curl says "transfer closed with outstanding read
data remaining".
I'm not too familiar with the http protocol. Are the headers and data
sent on different connections?
It could also be that there is a bug on the server side. If I request
chunked Transfer-Encoding then everything is fine.
Any suggestions about how to go about debugging this?

/Thanks
Emanuel
Received on 2008-10-18