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)

CURLOPT_CUSTOMREQUEST(3)				     curl_easy_setopt options					  CURLOPT_CUSTOMREQUEST(3)

NAME

       CURLOPT_CUSTOMREQUEST - custom string for request

SYNOPSIS

       #include <curl/curl.h>

       CURLcode curl_easy_setopt(CURL *handle, CURLOPT_CUSTOMREQUEST, char *request);

DESCRIPTION

       Pass a pointer to a zero terminated string as parameter.

       When  you change the request method by setting CURLOPT_CUSTOMREQUEST(3) to something, you don't actually change how libcurl behaves or acts
       in regards to the particular request method, it will only change the actual string sent in the request.

       Restore to the internal default by setting this to NULL.

       This option can be used to specify the request:

       HTTP   Instead of GET or HEAD when performing HTTP based requests. This is particularly useful, for example, for performing a  HTTP  DELETE
	      request.

	      For example:

	      When  you  tell  libcurl to do a HEAD request, but then specify a GET though a custom request libcurl will still act as if it sent a
	      HEAD. To switch to a proper HEAD use CURLOPT_NOBODY(3), to switch to a proper POST use CURLOPT_POST(3) or CURLOPT_POSTFIELDS(3)  and
	      to switch to a proper GET use CURLOPT_HTTPGET(3).

	      Many  people  have  wrongly  used this option to replace the entire request with their own, including multiple headers and POST con-
	      tents. While that might work in many cases, it will cause libcurl to send invalid requests and it could possibly confuse the  remote
	      server badly. Use CURLOPT_POST(3) and CURLOPT_POSTFIELDS(3) to set POST data. Use CURLOPT_HTTPHEADER(3) to replace or extend the set
	      of headers sent by libcurl. Use CURLOPT_HTTP_VERSION(3) to change HTTP version.

       FTP    Instead of LIST and NLST when performing FTP directory listings.

       IMAP   Instead of LIST when issuing IMAP based requests.

       POP3   Instead of LIST and RETR when issuing POP3 based requests.

	      For example:

	      When you tell libcurl to use a custom request it will behave like a LIST or RETR command was  sent  where  it  expects  data  to	be
	      returned by the server. As such CURLOPT_NOBODY(3) should be used when specifying commands such as DELE and NOOP for example.

       SMTP   Instead of a HELP or VRFY when issuing SMTP based requests.

	      For example:

	      Normally	a  multiline response is returned which can be used, in conjunction with CURLOPT_MAIL_RCPT(3), to specify an EXPN request.
	      If the CURLOPT_NOBODY(3) option is specified then the request can be used to issue NOOP and RSET commands.

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

DEFAULT

       NULL

PROTOCOLS

       HTTP, FTP, IMAP, POP3 and SMTP

EXAMPLE

       TODO

AVAILABILITY

       IMAP is supported since 7.30.0, POP3 since 7.26.0 and SMTP since 7.34.0.

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_HTTPHEADER(3), CURLOPT_NOBODY(3),

libcurl 7.54.0							 December 21, 2016					  CURLOPT_CUSTOMREQUEST(3)