summaryrefslogtreecommitdiff
path: root/CHANGES
diff options
context:
space:
mode:
authorBob Richmond <bob.richmond@ticketmaster.com>2010-03-24 17:02:17 +0100
committerDaniel Stenberg <daniel@haxx.se>2010-03-24 17:02:17 +0100
commit05632d5db9b67264826c53d99eaa81943e36275c (patch)
tree2a8854d88d1bbdf460c83f703b498a76ba74a6d7 /CHANGES
parentc245a8f92e7bb2b5bfe181af647ee4766a0f33fe (diff)
downloadcurl-05632d5db9b67264826c53d99eaa81943e36275c.tar.gz
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 'CHANGES')
-rw-r--r--CHANGES11
1 files changed, 11 insertions, 0 deletions
diff --git a/CHANGES b/CHANGES
index b6a5d4227..fa3f4000a 100644
--- a/CHANGES
+++ b/CHANGES
@@ -7,6 +7,17 @@
Changelog
Daniel Stenberg (24 Mar 2010)
+- 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.
+
- Christopher Conroy fixed a problem with RTSP and GET_PARAMETER reported
to us by Massimo Callegari. There's a new test case 572 that verifies this
now.