curlopt_readfunction(3) [mojave man page]

CURLOPT_READFUNCTION(3) 				     curl_easy_setopt options					   CURLOPT_READFUNCTION(3)

NAME

       CURLOPT_READFUNCTION - read callback for data uploads

SYNOPSIS

       #include <curl/curl.h>

       size_t read_callback(char *buffer, size_t size, size_t nitems, void *instream);

       CURLcode curl_easy_setopt(CURL *handle, CURLOPT_READFUNCTION, read_callback);

DESCRIPTION

       Pass a pointer to your callback function, as the prototype shows above.

       This  callback  function  gets  called  by libcurl as soon as it needs to read data in order to send it to the peer - like if you ask it to
       upload or post data to the server. The data area pointed at by the pointer buffer should be filled up with at  most  size  multiplied  with
       nmemb number of bytes by your function.

       Your  function  must  then return the actual number of bytes that it stored in that memory area. Returning 0 will signal end-of-file to the
       library and cause it to stop the current transfer.

       If you stop the current transfer by returning 0 "pre-maturely" (i.e before the server expected it, like when you've said you will upload  N
       bytes and you upload less than N bytes), you may experience that the server "hangs" waiting for the rest of the data that won't come.

       The  read callback may return CURL_READFUNC_ABORT to stop the current operation immediately, resulting in a CURLE_ABORTED_BY_CALLBACK error
       code from the transfer.

       The callback can return CURL_READFUNC_PAUSE to cause reading from this connection to pause. See curl_easy_pause(3) for further details.

       Bugs: when doing TFTP uploads, you must return the exact amount of data that the callback wants, or it will be considered the final  packet
       by the server end and the transfer will end there.

       If  you	set this callback pointer to NULL, or don't set it at all, the default internal read function will be used. It is doing an fread()
       on the FILE * userdata set with CURLOPT_READDATA(3).

DEFAULT

       The default internal read callback is fread().

PROTOCOLS

       This is used for all protocols when doing uploads.

EXAMPLE

       Here's an example setting a read callback for reading that to upload to an FTP site: https://curl.haxx.se/libcurl/c/ftpupload.html

AVAILABILITY

       CURL_READFUNC_PAUSE return code was added in 7.18.0 and CURL_READFUNC_ABORT was added in 7.12.1.

RETURN VALUE

       This will return CURLE_OK.

SEE ALSO

       CURLOPT_READDATA(3), CURLOPT_WRITEFUNCTION(3), CURLOPT_SEEKFUNCTION(3), CURLOPT_UPLOAD(3), CURLOPT_POST(3),

libcurl 7.54.0							 February 03, 2016					   CURLOPT_READFUNCTION(3)

CURLOPT_WRITEFUNCTION(3)				     curl_easy_setopt options					  CURLOPT_WRITEFUNCTION(3)

NAME

       CURLOPT_WRITEFUNCTION - set callback for writing received data

SYNOPSIS

       #include <curl/curl.h>

       size_t write_callback(char *ptr, size_t size, size_t nmemb, void *userdata);

       CURLcode curl_easy_setopt(CURL *handle, CURLOPT_WRITEFUNCTION, write_callback);

DESCRIPTION

       Pass a pointer to your callback function, which should match the prototype shown above.

       This  callback function gets called by libcurl as soon as there is data received that needs to be saved.  ptr points to the delivered data,
       and the size of that data is size multiplied with nmemb.

       The callback function will be passed as much data as possible in all invokes, but you must not make any assumptions. It may be one byte, it
       may  be	thousands.  The  maximum  amount  of  body  data  that	will be passed to the write callback is defined in the curl.h header file:
       CURL_MAX_WRITE_SIZE (the usual default is 16K). If CURLOPT_HEADER(3) is enabled, which makes header data get passed to the write  callback,
       you can get up to CURL_MAX_HTTP_HEADER bytes of header data passed into it. This usually means 100K.

       This function may be called with zero bytes data if the transferred file is empty.

       The data passed to this function will not be zero terminated!

       Set the userdata argument with the CURLOPT_WRITEDATA(3) option.

       Your  callback  should  return  the  number of bytes actually taken care of. If that amount differs from the amount passed to your callback
       function, it'll signal an error condition to the library. This will cause the transfer to get aborted and the libcurl  function	used  will
       return CURLE_WRITE_ERROR.

       If  your  callback  function returns CURL_WRITEFUNC_PAUSE it will cause this transfer to become paused.	See curl_easy_pause(3) for further
       details.

       Set this option to NULL to get the internal default function used instead of your callback. The internal default function  will	write  the
       data to the FILE * given with CURLOPT_WRITEDATA(3).

DEFAULT

       libcurl will use 'fwrite' as a callback by default.

PROTOCOLS

       For all protocols

AVAILABILITY

       Support for the CURL_WRITEFUNC_PAUSE return code was added in version 7.18.0.

RETURN VALUE

       This will return CURLE_OK.

EXAMPLE

       A  common technique is to use this callback to store the incoming data into a dynamically growing allocated buffer. Like in the getinmemory
       example: https://curl.haxx.se/libcurl/c/getinmemory.html

SEE ALSO

       CURLOPT_WRITEDATA(3), CURLOPT_READFUNCTION(3),

libcurl 7.54.0							 February 03, 2016					  CURLOPT_WRITEFUNCTION(3)