Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

curlopt_progressfunction(3) [mojave man page]

CURLOPT_PROGRESSFUNCTION(3)				     curl_easy_setopt options				       CURLOPT_PROGRESSFUNCTION(3)

NAME
CURLOPT_PROGRESSFUNCTION - callback to progress meter function SYNOPSIS
#include <curl/curl.h> int progress_callback(void *clientp, double dltotal, double dlnow, double ultotal, double ulnow); CURLcode curl_easy_setopt(CURL *handle, CURLOPT_PROGRESSFUNCTION, progress_callback); DESCRIPTION
Pass a pointer to your callback function, which should match the prototype shown above. We encourage users to use the newer CURLOPT_XFERINFOFUNCTION(3) instead, if you can. This function gets called by libcurl instead of its internal equivalent with a frequent interval. While data is being transferred it will be called very frequently, and during slow periods like when nothing is being transferred it can slow down to about one call per second. clientp is the pointer set with CURLOPT_PROGRESSDATA(3), it is not used by libcurl but is only passed along from the application to the callback. The callback gets told how much data libcurl will transfer and has transferred, in number of bytes. dltotal is the total number of bytes libcurl expects to download in this transfer. dlnow is the number of bytes downloaded so far. ultotal is the total number of bytes libcurl expects to upload in this transfer. ulnow is the number of bytes uploaded so far. Unknown/unused argument values passed to the callback will be set to zero (like if you only download data, the upload size will remain 0). Many times the callback will be called one or more times first, before it knows the data sizes so a program must be made to handle that. Returning a non-zero value from this callback will cause libcurl to abort the transfer and return CURLE_ABORTED_BY_CALLBACK. If you transfer data with the multi interface, this function will not be called during periods of idleness unless you call the appropriate libcurl function that performs transfers. CURLOPT_NOPROGRESS(3) must be set to 0 to make this function actually get called. DEFAULT
By default, libcurl has an internal progress meter. That's rarely wanted by users. PROTOCOLS
All EXAMPLE
https://curl.haxx.se/libcurl/c/progressfunc.html AVAILABILITY
Always RETURN VALUE
Returns CURLE_OK. SEE ALSO
CURLOPT_VERBOSE(3), CURLOPT_NOPROGRESS(3), libcurl 7.54.0 February 03, 2016 CURLOPT_PROGRESSFUNCTION(3)

Check Out this Related Man Page

curl_easy_cleanup(3)						  libcurl Manual					      curl_easy_cleanup(3)

NAME
curl_easy_cleanup - End a libcurl easy handle SYNOPSIS
#include <curl/curl.h> void curl_easy_cleanup(CURL *handle); DESCRIPTION
This function must be the last function to call for an easy session. It is the opposite of the curl_easy_init(3) function and must be called with the same handle as input that a curl_easy_init(3) call returned. This might close all connections this handle has used and possibly has kept open until now - unless it was attached to a multi handle while doing the transfers. Don't call this function if you intend to transfer more files, re-using handles is a key to good performance with libcurl. Occasionally you may get your progress callback or header callback called from within curl_easy_cleanup(3) (if previously set for the han- dle using curl_easy_setopt(3)). Like if libcurl decides to shut down the connection and the protocol is of a kind that requires a com- mand/response sequence before disconnect. Examples of such protocols are FTP, POP3 and IMAP. Any use of the handle after this function has been called and have returned, is illegal. curl_easy_cleanup(3) kills the handle and all mem- ory associated with it! For libcurl versions before 7.17,: after you've called this function, you can safely remove all the strings you've previously told libcurl to use, as it won't use them anymore now. RETURN VALUE
None EXAMPLE
CURL *curl = curl_easy_init(); if(curl) { CURLcode res; curl_easy_setopt(curl, CURLOPT_URL, "http://example.com"); res = curl_easy_perform(curl); curl_easy_cleanup(curl); } SEE ALSO
curl_easy_init(3), curl_easy_duphandle(3), curl_easy_reset(3), curl_multi_cleanup(3), curl_multi_remove_handle(3) libcurl 7.54.0 February 03, 2016 curl_easy_cleanup(3)
Man Page