summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2004-06-21 14:10:39 +0000
committerDaniel Stenberg <daniel@haxx.se>2004-06-21 14:10:39 +0000
commit941374b573b681119bfaf579da90c4563c9c33e2 (patch)
treec6ddf13ce6a3d913c56a14b8a4f4503e82089226
parent1886893d66356634a7d13b466a1ced38265f68e2 (diff)
downloadgnurl-941374b573b681119bfaf579da90c4563c9c33e2.tar.gz
gnurl-941374b573b681119bfaf579da90c4563c9c33e2.tar.bz2
gnurl-941374b573b681119bfaf579da90c4563c9c33e2.zip
CURL_READFUNC_ABORT stuff
-rw-r--r--CHANGES10
1 files changed, 10 insertions, 0 deletions
diff --git a/CHANGES b/CHANGES
index 2fe26613b..de7a319d8 100644
--- a/CHANGES
+++ b/CHANGES
@@ -6,6 +6,16 @@
Changelog
+Daniel (21 June 2004)
+- Kjetil Jacobsen brought my attention to the fact that you cannot properly
+ abort an upload with the readfunction callback, since returning 0 or -1 only
+ stops the upload and libcurl will continue waiting for downloaded data and
+ the server often waits for the rest of the upload data to arrive.
+
+ Thus, I've now added the ability for read callbacks to return
+ CURL_READFUNC_ABORT to abort an upload from a read callback. This will stop
+ the transfer immediately with a CURLE_ABORTED_BY_CALLBACK return code.
+
Daniel (19 June 2004)
- Luca Alteas provided a test case with a failing curl operation: when we POST
to a site with --digest (or similar) set, and the server responded with a 302