From: Daniel Stenberg <daniel@haxx.se>
Date: Mon, 21 Jun 2004 14:10:39 +0000 (+0000)
Subject: CURL_READFUNC_ABORT stuff
X-Git-Tag: pre-aifix~24
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=941374b573b681119bfaf579da90c4563c9c33e2;p=curl

CURL_READFUNC_ABORT stuff
---

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