GNURLOPT_WRITEFUNCTION(3)

πŸ“¦ version 7.72.0, in nixos 26.05, nixpkgs unstable

πŸ’… GNURLOPT_WRITEFUNCTION(3) πŸ’…

okay so bestie, this page lives in the curl_easy_setopt options manual, and it’s the GNURLOPT_WRITEFUNCTION(3) page β€” aka the CURLOPT_WRITEFUNCTION write callback situation. stay with me, it’s lowkey iconic. πŸ¦‹

✨ NAME ✨

  • CURLOPT_WRITEFUNCTION β€” set callback for writing received data

✨ SYNOPSIS ✨

#include <gnurl/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 πŸ’–

okay so you pass a pointer to your callback function, and it should match the prototype up there. no cap. 🫢

libcurl calls this callback function as soon as there’s data received that needs to be saved. for most transfers, this callback gets called many times, and each invoke delivers another chunk of data. ptr points to the delivered data, and the size of that data is nmemb; size is always 1. πŸ’…

libcurl will try to pass 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 null-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 πŸ”₯

        struct memory {
          char *response;
          size_t size;
        };

        static size_t cb(void *data, size_t size, size_t nmemb, void *userp)
        {
          size_t realsize = size * nmemb;
          struct memory *mem = (struct memory *)userp;

          char *ptr = realloc(mem->response, mem->size + realsize + 1);
          if(ptr == NULL)
            return 0;  /* out of memory! */

          mem->response = ptr;
          memcpy(&(mem->response[mem->size]), data, realsize);
          mem->size += realsize;
          mem->response[mem->size] = 0;

          return realsize;
        }

        struct memory chunk;

        /* send all data to this function  */
        curl_easy_setopt(curl_handle, CURLOPT_WRITEFUNCTION, cb);

        /* we pass our 'chunk' struct to the callback function */
        curl_easy_setopt(curl_handle, CURLOPT_WRITEDATA, (void *)&chunk);

πŸ‘‘ SEE ALSO πŸ‘‘


mwah πŸ’‹ β€” signed off by libcurl 7.37.0, dated 16 Jun 2014. go write that callback, bestie 🫢✨

πŸ“¦ where this page comes from