curlopt_cookiesession(3) [mojave man page]

CURLOPT_COOKIESESSION(3)				     curl_easy_setopt options					  CURLOPT_COOKIESESSION(3)

NAME

       CURLOPT_COOKIESESSION - start a new cookie session

SYNOPSIS

       #include <curl/curl.h>

       CURLcode curl_easy_setopt(CURL *handle, CURLOPT_COOKIESESSION, long init);

DESCRIPTION

       Pass a long set to 1 to mark this as a new cookie "session". It will force libcurl to ignore all cookies it is about to load that are "ses-
       sion cookies" from the previous session. By default, libcurl always stores and loads all cookies, independent if they are  session  cookies
       or not. Session cookies are cookies without expiry date and they are meant to be alive and existing for this "session" only.

       A "session" is usually defined in browser land for as long as you have your browser up, more or less.

DEFAULT

       0

PROTOCOLS

       HTTP

EXAMPLE

       TODO

AVAILABILITY

       Along with HTTP

RETURN VALUE

       Returns CURLE_OK

SEE ALSO

       CURLOPT_COOKIEFILE(3), CURLOPT_COOKIE(3),

libcurl 7.54.0							 February 03, 2016					  CURLOPT_COOKIESESSION(3)

CURLOPT_COOKIEJAR(3)					     curl_easy_setopt options					      CURLOPT_COOKIEJAR(3)

NAME

       CURLOPT_COOKIEJAR - file name to store cookies to

SYNOPSIS

       #include <curl/curl.h>

       CURLcode curl_easy_setopt(CURL *handle, CURLOPT_COOKIEJAR, char *filename);

DESCRIPTION

       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 writ-
       ten to stdout. Using this option also enables cookies for this session, so if you for example follow a location it will make matching cook-
       ies get sent accordingly.

       Note that libcurl doesn't 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 can't 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.

       The application does not have to keep the string around after setting this option.

DEFAULT

       NULL

PROTOCOLS

       HTTP

EXAMPLE

       TODO

AVAILABILITY

       Along with HTTP

RETURN VALUE

       Returns CURLE_OK if HTTP is supported, CURLE_UNKNOWN_OPTION if not, or CURLE_OUT_OF_MEMORY if there was insufficient heap space.

SEE ALSO

       CURLOPT_COOKIEFILE(3), CURLOPT_COOKIE(3), CURLOPT_COOKIELIST(3),

libcurl 7.54.0							 December 21, 2016					      CURLOPT_COOKIEJAR(3)