Query: curlopt_writedata
OS: mojave
Section: 3
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
CURLOPT_WRITEDATA(3) curl_easy_setopt options CURLOPT_WRITEDATA(3)NAMECURLOPT_WRITEDATA - custom pointer passed to the write callbackSYNOPSIS#include <curl/curl.h> CURLcode curl_easy_setopt(CURL *handle, CURLOPT_WRITEDATA, void *pointer);DESCRIPTIONA data pointer to pass to the write callback. If you use the CURLOPT_WRITEFUNCTION(3) option, this is the pointer you'll get in that call- back's 4th argument. If you don't use a write callback, you must make pointer a 'FILE *' (cast to 'void *') as libcurl will pass this to fwrite(3) when writing data. The internal CURLOPT_WRITEFUNCTION(3) will write the data to the FILE * given with this option, or to stdout if this option hasn't been set. If you're using libcurl as a win32 DLL, you MUST use the CURLOPT_WRITEFUNCTION(3) if you set this option or you will experience crashes.DEFAULTBy default, this is a FILE * to stdout.PROTOCOLSUsed for all protocols.EXAMPLEA common technique is to use the write callback to store the incoming data into a dynamically growing allocated buffer, and then this CUR- LOPT_WRITEDATA(3) is used to point to a struct or the buffer to store data in. Like in the getinmemory example: https://curl.haxx.se/libcurl/c/getinmemory.htmlAVAILABILITYAvailable in all libcurl versions. This option was formerly known as CURLOPT_FILE, the name CURLOPT_WRITEDATA(3) was introduced in 7.9.7.RETURN VALUEThis will return CURLE_OK.SEE ALSOCURLOPT_WRITEFUNCTION(3), CURLOPT_READDATA(3), libcurl 7.54.0 February 03, 2016 CURLOPT_WRITEDATA(3)
Related Man Pages |
---|
curlopt_conv_from_utf8_function(3) - mojave |
curlopt_errorbuffer(3) - mojave |
curlopt_protocols(3) - mojave |
curlopt_sockoptfunction(3) - mojave |
curlopt_upload(3) - mojave |
Similar Topics in the Unix Linux Community |
---|
coverting html data to text in 'c' |
Need a simple example of passing FILE pointers |
Curl and write custom result to file |