Manual Reference Pages - CURLOPT_COOKIEJAR (3)
CURLOPT_COOKIEJAR - file name to store cookies to
CURLcode curl_easy_setopt(CURL *handle, CURLOPT_COOKIEJAR, char *filename);
Pass a filename as char *, zero terminated. This will make libcurl write
all internally known cookies to the specified file when
curl_easy_cleanup(3) is called. If no cookies are known, no file will be
created. Specify "-" as filename to instead have the cookies written to
stdout. Using this option also enables cookies for this session, so if you for
example follow a location it will make matching cookies get sent accordingly.
Note that libcurl doesnt read any cookies from the cookie jar. If you want to
read cookies from a file, use CURLOPT_COOKIEFILE(3).
If the cookie jar file cant be created or written to (when the
curl_easy_cleanup(3) is called), libcurl will not and cannot report an
error for this. Using CURLOPT_VERBOSE(3) or
CURLOPT_DEBUGFUNCTION(3) will get a warning to display, but that is the
only visible feedback you get about this possibly lethal situation.
Since 7.43.0 cookies that were imported in the Set-Cookie format without a
domain name are not exported by this option.
Along with HTTP
Returns CURLE_OK if HTTP is supported, CURLE_UNKNOWN_OPTION if not, or
CURLE_OUT_OF_MEMORY if there was insufficient heap space.
|libcurl 7.37.0 ||CURLOPT_COOKIEJAR (3) ||17 Jun 2014 |
Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.