On 11/2/06, Daniel Stenberg <daniel_at_haxx.se> wrote:
> No, the debugfunction gets called with data libcurl sends and receives, and it
> shouldn't send nor receive that data more than once.
>
> The dump looks fine all the way to line 185 where there's something _after_
> the final chunk.

It works now with the latest curl version. There's a problem with
curl_easy_free() though on my system; memcmp() in /lib/tls/libc.so.6
segfaults. Obviously not a curl issue. I'll take it up with the Debian
TLS package maintainers perhaps.

There is another issue. curl_easy_perform() returns an error "couldn't
send data to peer" even though immediately after that I get the error
string and the HTTP return code is 200. It works, but perhaps it tries
a few times, sets the error, then it works and hence the bad return
code but it's actually worked after a few tries?

-J
Received on 2006-11-02