Hey

I decided to take the further discussions about this bug report[1] to the
mailing list. It is a better forum to discuss things.

I don't think I've made myself clear about this report. Getting an error 52
back in the situation you describe - is a bug. If we could detect the
situation well enough to return a different error code, well, then we could
just as well stop doing it wrong and behave correctly instead! Thus, returning
a different error code just can't be the correct fix for this.

I would like you to strace a failing operation (or similar) to allow us to
better understand what's going on. libcurl should detect the closed socket and
it should retry both the connection and the request itself.

I take it your source code example still fails when using a very recent daily
snapshot of curl? Can you tell us a URL which shows the problem for you? Also,
what operating system are you using when you get the problems?

[1] =
http://sourceforge.net/tracker/index.php?func=detail&aid=894613&group_id=976&atid=100976

-- 
    Daniel Stenberg -- http://curl.haxx.se/ -- http://daniel.haxx.se/
   [[ Do not send mails to this email address. They won't reach me. ]]