Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

curlopt_errorbuffer(3) [mojave man page]

CURLOPT_ERRORBUFFER(3)					     curl_easy_setopt options					    CURLOPT_ERRORBUFFER(3)

NAME
CURLOPT_ERRORBUFFER - set error buffer for error messages SYNOPSIS
#include <curl/curl.h> CURLcode curl_easy_setopt(CURL *handle, CURLOPT_ERRORBUFFER, char *buf); DESCRIPTION
Pass a char * to a buffer that the libcurl may store human readable error messages in on failures or problems. This may be more helpful than just the return code from curl_easy_perform(3) and related functions. The buffer must be at least CURL_ERROR_SIZE bytes big. You must keep the associated buffer available until libcurl no longer needs it. Failing to do so will cause very odd behavior or even crashes. libcurl will need it until you call curl_easy_cleanup(3) or you set the same option again to use a different pointer. Consider CURLOPT_VERBOSE(3) and CURLOPT_DEBUGFUNCTION(3) to better debug and trace why errors happen. If the library does not return an error, the buffer may not have been touched. Do not rely on the contents in those cases. DEFAULT
NULL PROTOCOLS
All EXAMPLE
curl = curl_easy_init(); if(curl) { CURLcode res; char errbuf[CURL_ERROR_SIZE]; curl_easy_setopt(curl, CURLOPT_URL, "http://example.com"); /* provide a buffer to store errors in */ curl_easy_setopt(curl, CURLOPT_ERRORBUFFER, errbuf); /* set the error buffer as empty before performing a request */ errbuf[0] = 0; /* perform the request */ res = curl_easy_perform(curl); /* if the request did not complete correctly, show the error information. if no detailed error information was written to errbuf show the more generic information from curl_easy_strerror instead. */ if(res != CURLE_OK) { size_t len = strlen(errbuf); fprintf(stderr, " libcurl: (%d) ", res); if(len) fprintf(stderr, "%s%s", errbuf, ((errbuf[len - 1] != ' ') ? " " : "")); else fprintf(stderr, "%s ", curl_easy_strerror(res)); } } AVAILABILITY
Always RETURN VALUE
Returns CURLE_OK SEE ALSO
CURLOPT_DEBUGFUNCTION(3), CURLOPT_VERBOSE(3), curl_easy_strerror(3), curl_multi_strerror(3), curl_share_strerror(3) libcurl 7.54.0 February 03, 2016 CURLOPT_ERRORBUFFER(3)

Check Out this Related Man Page

CURLOPT_UPLOAD(3)					     curl_easy_setopt options						 CURLOPT_UPLOAD(3)

NAME
CURLOPT_UPLOAD - enable data upload SYNOPSIS
#include <curl/curl.h> CURLcode curl_easy_setopt(CURL *handle, CURLOPT_UPLOAD, long upload); DESCRIPTION
The long parameter upload set to 1 tells the library to prepare for and perform an upload. The CURLOPT_READDATA(3) and CURLOPT_INFILE- SIZE(3) or CURLOPT_INFILESIZE_LARGE(3) options are also interesting for uploads. If the protocol is HTTP, uploading means using the PUT request unless you tell libcurl otherwise. Using PUT with HTTP 1.1 implies the use of a "Expect: 100-continue" header. You can disable this header with CURLOPT_HTTPHEADER(3) as usual. If you use PUT to a HTTP 1.1 server, you can upload data without knowing the size before starting the transfer if you use chunked encoding. You enable this by adding a header like "Transfer-Encoding: chunked" with CURLOPT_HTTPHEADER(3). With HTTP 1.0 or without chunked transfer, you must specify the size. DEFAULT
0, default is download PROTOCOLS
Most EXAMPLE
CURL *curl = curl_easy_init(); if(curl) { /* we want to use our own read function */ curl_easy_setopt(curl, CURLOPT_READFUNCTION, read_callback); /* enable uploading */ curl_easy_setopt(curl, CURLOPT_UPLOAD, 1L); /* specify target */ curl_easy_setopt(curl, CURLOPT_URL, "ftp://example.com/dir/to/newfile"); /* now specify which pointer to pass to our callback */ curl_easy_setopt(curl, CURLOPT_READDATA, hd_src); /* Set the size of the file to upload */ curl_easy_setopt(curl, CURLOPT_INFILESIZE_LARGE, (curl_off_t)fsize); /* Now run off and do what you've been told! */ curl_easy_perform(curl); } AVAILABILITY
Always RETURN VALUE
Returns CURLE_OK SEE ALSO
CURLOPT_PUT(3), CURLOPT_READFUNCTION(3), CURLOPT_INFILESIZE_LARGE(3), libcurl 7.54.0 February 03, 2016 CURLOPT_UPLOAD(3)
Man Page