curlopt_post(3) [mojave man page]

CURLOPT_POST(3) 					     curl_easy_setopt options						   CURLOPT_POST(3)

NAME

       CURLOPT_POST - request a HTTP POST

SYNOPSIS

       #include <curl/curl.h>

       CURLcode curl_easy_setopt(CURL *handle, CURLOPT_POST, long post);

DESCRIPTION

       A  parameter set to 1 tells libcurl to do a regular HTTP post. This will also make the library use a "Content-Type: application/x-www-form-
       urlencoded" header. (This is by far the most commonly used POST method).

       Use one of CURLOPT_POSTFIELDS(3) or CURLOPT_COPYPOSTFIELDS(3) options to specify what data to post  and	CURLOPT_POSTFIELDSIZE(3)  or  CUR-
       LOPT_POSTFIELDSIZE_LARGE(3) to set the data size.

       Optionally,  you  can provide data to POST using the CURLOPT_READFUNCTION(3) and CURLOPT_READDATA(3) options but then you must make sure to
       not set CURLOPT_POSTFIELDS(3) to anything but NULL. When providing data with a callback, you must transmit it using chunked transfer-encod-
       ing  or	you  must  set the size of the data with the CURLOPT_POSTFIELDSIZE(3) or CURLOPT_POSTFIELDSIZE_LARGE(3) options. To enable chunked
       encoding, you simply pass in the appropriate Transfer-Encoding header, see the post-callback.c example.

       You can override the default POST Content-Type: header by setting your own with CURLOPT_HTTPHEADER(3).

       Using POST 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 POST to a HTTP 1.1 server, you can send data without knowing the size before starting the POST 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 in the request.

       When setting CURLOPT_POST(3) to 1, it will automatically set CURLOPT_NOBODY(3) to 0.

       If you issue a POST request and then want to make a HEAD or GET using the same re-used handle, you must explicitly set the new request type
       using CURLOPT_NOBODY(3) or CURLOPT_HTTPGET(3) or similar.

DEFAULT

       0, disabled

PROTOCOLS

       HTTP

EXAMPLE

       TODO

AVAILABILITY

       Along with HTTP

RETURN VALUE

       Returns CURLE_OK if HTTP is supported, and CURLE_UNKNOWN_OPTION if not.

SEE ALSO

       CURLOPT_POSTFIELDS(3), CURLOPT_HTTPPOST(3),

libcurl 7.54.0							 February 03, 2016						   CURLOPT_POST(3)

Check Out this Related Man Page

CURLOPT_POSTREDIR(3)					     curl_easy_setopt options					      CURLOPT_POSTREDIR(3)

NAME

       CURLOPT_POSTREDIR - how to act on a HTTP POST redirect

SYNOPSIS

       #include <curl/curl.h>

       CURLcode curl_easy_setopt(CURL *handle, CURLOPT_POSTREDIR,
				 long bitmask);

DESCRIPTION

       Pass  a	bitmask to control how libcurl acts on redirects after POSTs that get a 301, 302 or 303 response back.	A parameter with bit 0 set
       (value CURL_REDIR_POST_301) tells the library to respect RFC 7231 (section 6.4.2 to 6.4.4) and not convert POST requests into GET  requests
       when following a 301 redirection.  Setting bit 1 (value CURL_REDIR_POST_302) makes libcurl maintain the request method after a 302 redirect
       whilst  setting	bit  2	(value	CURL_REDIR_POST_303)  makes  libcurl  maintain	the  request  method  after  a	303  redirect.	The  value
       CURL_REDIR_POST_ALL is a convenience define that sets all three bits.

       The  non-RFC  behaviour	is  ubiquitous	in web browsers, so the library does the conversion by default to maintain consistency. However, a
       server may require a POST to remain a POST after such a redirection. This option is meaningful only when setting CURLOPT_FOLLOWLOCATION(3).

DEFAULT

       0

PROTOCOLS

       HTTP(S)

EXAMPLE

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

	 /* a silly POST example */
	 curl_easy_setopt(curl, CURLOPT_POSTFIELDS, "data=true");

	 /* example.com is redirected, so we tell libcurl to send POST on 301, 302 and
	    303 HTTP response codes */
	 curl_easy_setopt(curl, CURLOPT_POSTREDIR, CURL_REDIR_POST_ALL);

	 curl_easy_perform(curl);
       }

AVAILABILITY

       Added in 7.17.1. This option was known as CURLOPT_POST301 up to 7.19.0 as it only supported the 301 then. CURL_REDIR_POST_303 was added	in
       7.26.0.

RETURN VALUE

       Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not.

SEE ALSO

       CURLOPT_FOLLOWLOCATION(3), CURLOPT_POSTFIELDS(3),

libcurl 7.54.0							 February 03, 2016					      CURLOPT_POSTREDIR(3)

Linux and UNIX Man Pages

curlopt_post(3) [mojave man page]

Check Out this Related Man Page