curlopt_cookie(3) [mojave man page]

CURLOPT_COOKIE(3)					     curl_easy_setopt options						 CURLOPT_COOKIE(3)

NAME

       CURLOPT_COOKIE - set contents of HTTP Cookie header

SYNOPSIS

       #include <curl/curl.h>

       CURLcode curl_easy_setopt(CURL *handle, CURLOPT_COOKIE, char *cookie);

DESCRIPTION

       Pass  a	pointer  to  a	zero terminated string as parameter. It will be used to set a cookie in the HTTP request. The format of the string
       should be NAME=CONTENTS, where NAME is the cookie name and CONTENTS is what the cookie should contain.

       If you need to set multiple cookies, set them all using a single option concatenated like this: "name1=content1; name2=content2;" etc.

       This option sets the cookie header explicitly in the outgoing request(s). If multiple requests are done	due  to  authentication,  followed
       redirections or similar, they will all get this cookie passed on.

       The  cookies  set by this option are separate from the internal cookie storage held by the cookie engine and will not be modified by it. If
       you enable the cookie engine and either you've imported a cookie of the same name (e.g. 'foo') or the server has set one, it will  have	no
       effect  on the cookies you set here.  A request to the server will send both the 'foo' held by the cookie engine and the 'foo' held by this
       option. To set a cookie that is instead held by the cookie engine and can be modified by the server use CURLOPT_COOKIELIST(3).

       Using this option multiple times will only make the latest string override the previous ones.

       This option will not enable the cookie engine. Use CURLOPT_COOKIEFILE(3) or CURLOPT_COOKIEJAR(3) to  enable  parsing  and  sending  cookies
       automatically.

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

DEFAULT

       NULL, no cookies

PROTOCOLS

       HTTP

EXAMPLE

       CURL *curl = curl_easy_init();
       if(curl) {
	 curl_easy_setopt(curl, CURLOPT_URL, "http://example.com");

	 curl_easy_setopt(curl, CURLOPT_COOKIE, "tool=curl; fun=yes;");

	 curl_easy_perform(curl);
       }

AVAILABILITY

       If HTTP is enabled

RETURN VALUE

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

SEE ALSO

       CURLOPT_COOKIEFILE(3), CURLOPT_COOKIEJAR(3), CURLOPT_COOKIELIST(3), CURLOPT_HTTPHEADER(3),

libcurl 7.54.0							 December 21, 2016						 CURLOPT_COOKIE(3)

CURLOPT_ACCEPT_ENCODING(3)				     curl_easy_setopt options					CURLOPT_ACCEPT_ENCODING(3)

NAME

       CURLOPT_ACCEPT_ENCODING - enables automatic decompression of HTTP downloads

SYNOPSIS

       #include <curl/curl.h>

       CURLcode curl_easy_setopt(CURL *handle, CURLOPT_ACCEPT_ENCODING, char *enc);

DESCRIPTION

       Pass a char * argument specifying what encoding you'd like.

       Sets the contents of the Accept-Encoding: header sent in a HTTP request, and enables decoding of a response when a Content-Encoding: header
       is received.  Three encodings are supported: identity, meaning non-compressed, deflate which requests the server to compress  its  response
       using the zlib algorithm, and gzip which requests the gzip algorithm.

       If a zero-length string is set like "", then an Accept-Encoding: header containing all built-in supported encodings is sent.

       Set this option to NULL to explicitly disable it, which makes libcurl not send an Accept-Encoding: header and not decompress contents auto-
       matically.

       You can also opt to just include the Accept-Encoding: header in your request with CURLOPT_HTTPHEADER(3) but then there will be no automatic
       decompressing when receiving data.

       This  is a request, not an order; the server may or may not do it.  This option must be set (to any non-NULL value) or else any unsolicited
       encoding done by the server is ignored.

       Servers might respond with Content-Encoding even without getting a Accept-Encoding: in the request. Servers might respond with a  different
       Content-Encoding than what was asked for in the request.

       The Content-Length: servers send for a compressed response is supposed to indicate the length of the compressed content so when auto decod-
       ing is enabled it may not match the sum of bytes reported by the write callbacks (although, sending the length of the  non-compressed  con-
       tent is a common server mistake).

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

DEFAULT

       NULL

PROTOCOLS

       HTTP

EXAMPLE

       CURL *curl = curl_easy_init();
       if(curl) {
	 curl_easy_setopt(curl, CURLOPT_URL, "http://example.com");

	 /* enable all supported built-in compressions */
	 curl_easy_setopt(curl, CURLOPT_ACCEPT_ENCODING, "");

	 /* Perform the request */
	 curl_easy_perform(curl);
       }

AVAILABILITY

       This option was called CURLOPT_ENCODING before 7.21.6

RETURN VALUE

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

SEE ALSO

       CURLOPT_TRANSFER_ENCODING(3), CURLOPT_HTTPHEADER(3), CURLOPT_HTTP_CONTENT_DECODING(3),

libcurl 7.54.0							 December 21, 2016					CURLOPT_ACCEPT_ENCODING(3)