There's an annoying situation where libcurl will read new HTTP response
data from a socket, then check if it's a timeout if one is set. If the
last packet received constitutes the end of the response body, libcurl
still treats it as a timeout condition and reports a message like:

"Operation timed out after 3000 milliseconds with 876 out of 876 bytes
received"

It should only a timeout if the timer lapsed and we DIDN'T receive the
end of the response body yet.

I've attached a patch that will correct that behaviour.
CONFIDENTIALITY NOTICE:

This message contains information which may be confidential or privileged. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this transmission in error, please notify me immediately by telephone.

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html