diff options
author | Bob Richmond <bob.richmond@ticketmaster.com> | 2010-03-24 17:02:17 +0100 |
---|---|---|
committer | Daniel Stenberg <daniel@haxx.se> | 2010-03-24 17:02:17 +0100 |
commit | 05632d5db9b67264826c53d99eaa81943e36275c (patch) | |
tree | 2a8854d88d1bbdf460c83f703b498a76ba74a6d7 /tests/certs/Server-localhost0h-sv.p12 | |
parent | c245a8f92e7bb2b5bfe181af647ee4766a0f33fe (diff) |
fix: timeout after last data chunk was handled
Bob Richmond: 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.
Diffstat (limited to 'tests/certs/Server-localhost0h-sv.p12')
0 files changed, 0 insertions, 0 deletions