curlopt_username(3) [mojave man page]
CURLOPT_USERNAME(3) curl_easy_setopt options CURLOPT_USERNAME(3) NAME
CURLOPT_USERNAME - user name to use in authentication SYNOPSIS
#include <curl/curl.h> CURLcode curl_easy_setopt(CURL *handle, CURLOPT_USERNAME, char *username); DESCRIPTION
Pass a char * as parameter, which should be pointing to the zero terminated user name to use for the transfer. CURLOPT_USERNAME(3) sets the user name to be used in protocol authentication. You should not use this option together with the (older) CUR- LOPT_USERPWD(3) option. When using Kerberos V5 authentication with a Windows based server, you should include the domain name in order for the server to success- fully obtain a Kerberos Ticket. If you don't then the initial part of the authentication handshake may fail. When using NTLM, the user name can be specified simply as the user name without the domain name should the server be part of a single domain and forest. To include the domain name use either Down-Level Logon Name or UPN (User Principal Name) formats. For example, EXAMPLEuser and user@exam- ple.com respectively. Some HTTP servers (on Windows) support inclusion of the domain for Basic authentication as well. To specify the password and login options, along with the user name, use the CURLOPT_PASSWORD(3) and CURLOPT_LOGIN_OPTIONS(3) options. The application does not have to keep the string around after setting this option. DEFAULT
blank PROTOCOLS
Most EXAMPLE
TODO AVAILABILITY
Added in 7.19.1 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_USERPWD(3), CURLOPT_PASSWORD(3), CURLOPT_HTTPAUTH(3), CURLOPT_PROXYAUTH(3) libcurl 7.54.0 December 21, 2016 CURLOPT_USERNAME(3)
Check Out this Related 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)