The description doesn't make it terribly clear that:

1 - the example uses the multi interface and

2 - the paused transfer is being resumed almost immediately (to no effect)

... my notes after having read the example source.

---
** [bugs:#1286] libcurl stopes upload to file:// url if CURL_READFUNC_PAUSE is returned**
**Status:** open
**Created:** Wed Oct 02, 2013 08:06 AM UTC by Maxim
**Last Updated:** Wed Oct 02, 2013 08:06 AM UTC
**Owner:** Daniel Stenberg
Whenever I return CURL_READFUNC_PAUSE from read_callback function the upload stops.
A test code is attached.
Checked with the latest version from git (as of 1 Oct 2013, commit 3d43a487813a94dc8521bd8d970725efbd922bf7)
for the given test file I've got the following output:
> handles OK
    read_callback: try read 16384, paused 0
    read_callback: try read 16384, paused 0
    pause
    upload result: No error
    resume
    upload result: No error
    upload finished at 1
    upload result: No error
    upload finished at 2
    upload result: No error
    upload finished at 3
    upload result: No error
    upload finished at 4
PS The file is actually is created but it stored only the first block.
> $ ll /tmp/curloutfile.tmp 
    -rw-r--r-- 1 max max 16384 Oct.   2 14:57 /tmp/curloutfile.tmp
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to https://sourceforge.net/p/curl/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/curl/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.