align: top;">CURLOPT_IPRESOLVE *
| Option | *Set value to |
* Notes | *
|---|---|---|
| CURLOPT_CAINFO | ** The name of a file holding one or more certificates to verify the * peer with. This only makes sense when used in combination with * CURLOPT_SSL_VERIFYPEER. * | ** Might require an absolute path. * | *
| CURLOPT_CAPATH | ** A directory that holds multiple CA certificates. Use this option * alongside CURLOPT_SSL_VERIFYPEER. * | ** | *
| CURLOPT_COOKIE | ** The contents of the "Cookie: " header to be * used in the HTTP request. * Note that multiple cookies are separated with a semicolon followed * by a space (e.g., "fruit=apple; colour=red") * | ** | *
| CURLOPT_COOKIEFILE | ** The name of the file containing the cookie data. The cookie file can * be in Netscape format, or just plain HTTP-style headers dumped into * a file. * If the name is an empty string, no cookies are loaded, but cookie * handling is still enabled. * | ** | *
| CURLOPT_COOKIEJAR | ** The name of a file to save all internal cookies to when the handle is closed, * e.g. after a call to curl_close. * | ** | *
| CURLOPT_CUSTOMREQUEST | ** A custom request method to use instead of * "GET" or "HEAD" when doing * a HTTP request. This is useful for doing * "DELETE" or other, more obscure HTTP requests. * Valid values are things like "GET", * "POST", "CONNECT" and so on; * i.e. Do not enter a whole HTTP request line here. For instance, * entering "GET /index.html HTTP/1.0\r\n\r\n" * would be incorrect. * * |
* * | *
| CURLOPT_EGDSOCKET | ** Like CURLOPT_RANDOM_FILE, except a filename * to an Entropy Gathering Daemon socket. * | ** | *
| CURLOPT_ENCODING | ** The contents of the "Accept-Encoding: " header. * This enables decoding of the response. Supported encodings are * "identity", "deflate", and * "gzip". If an empty string, "", * is set, a header containing all supported encoding types is sent. * | ** Added in cURL 7.10. * | *
| CURLOPT_FTPPORT | ** The value which will be used to get the IP address to use * for the FTP "PORT" instruction. The "PORT" instruction tells * the remote server to connect to our specified IP address. The * string may be a plain IP address, a hostname, a network * interface name (under Unix), or just a plain '-' to use the * systems default IP address. * | ** | *
| CURLOPT_INTERFACE | ** The name of the outgoing network interface to use. This can be an * interface name, an IP address or a host name. * | ** | *
| CURLOPT_KEYPASSWD | ** The password required to use the CURLOPT_SSLKEY * or CURLOPT_SSH_PRIVATE_KEYFILE private key. * | ** Added in cURL 7.16.1. * | *
| CURLOPT_KRB4LEVEL | ** The KRB4 (Kerberos 4) security level. Any of the following values * (in order from least to most powerful) are valid: * "clear", * "safe", * "confidential", * "private".. * If the string does not match one of these, * "private" is used. Setting this option to NULL * will disable KRB4 security. Currently KRB4 security only works * with FTP transactions. * | ** | *
| CURLOPT_POSTFIELDS | *
*
* The full data to post in a HTTP "POST" operation.
* To post a file, prepend a filename with @ and
* use the full path. The filetype can be explicitly specified by
* following the filename with the type in the format
* ';type=mimetype'. This parameter can either be
* passed as a urlencoded string like 'para1=val1¶2=val2&...'
* or as an array with the field name as key and field data as value.
* If value is an array, the
* Content-Type header will be set to
* multipart/form-data.
*
*
* As of PHP 5.2.0, value must be an array if
* files are passed to this option with the @ prefix.
*
*
* As of PHP 5.5.0, the @ prefix is deprecated and
* files can be sent using CURLFile. The
* @ prefix can be disabled for safe passing of
* values beginning with @ by setting the
* CURLOPT_SAFE_UPLOAD option to TRUE.
*
* |
* * | *
| CURLOPT_PROXY | ** The HTTP proxy to tunnel requests through. * | ** | *
| CURLOPT_PROXYUSERPWD | ** A username and password formatted as * "[username]:[password]" to use for the * connection to the proxy. * | ** | *
| CURLOPT_RANDOM_FILE | ** A filename to be used to seed the random number generator for SSL. * | ** | *
| CURLOPT_RANGE | ** Range(s) of data to retrieve in the format * "X-Y" where X or Y are optional. HTTP transfers * also support several intervals, separated with commas in the format * "X-Y,N-M". * | ** | *
| CURLOPT_REFERER | ** The contents of the "Referer: " header to be used * in a HTTP request. * | ** | *
| CURLOPT_SSH_HOST_PUBLIC_KEY_MD5 | ** A string containing 32 hexadecimal digits. The string should be the * MD5 checksum of the remote host's public key, and libcurl will reject * the connection to the host unless the md5sums match. * This option is only for SCP and SFTP transfers. * | ** Added in cURL 7.17.1. * | *
| CURLOPT_SSH_PUBLIC_KEYFILE | ** The file name for your public key. If not used, libcurl defaults to * $HOME/.ssh/id_dsa.pub if the HOME environment variable is set, * and just "id_dsa.pub" in the current directory if HOME is not set. * | ** Added in cURL 7.16.1. * | *
| CURLOPT_SSH_PRIVATE_KEYFILE | ** The file name for your private key. If not used, libcurl defaults to * $HOME/.ssh/id_dsa if the HOME environment variable is set, * and just "id_dsa" in the current directory if HOME is not set. * If the file is password-protected, set the password with * CURLOPT_KEYPASSWD. * | ** Added in cURL 7.16.1. * | *
| CURLOPT_SSL_CIPHER_LIST | ** A list of ciphers to use for SSL. For example, * RC4-SHA and TLSv1 are valid * cipher lists. * | ** | *
| CURLOPT_SSLCERT | ** The name of a file containing a PEM formatted certificate. * | ** | *
| CURLOPT_SSLCERTPASSWD | ** The password required to use the * CURLOPT_SSLCERT certificate. * | ** | *
| CURLOPT_SSLCERTTYPE | ** The format of the certificate. Supported formats are * "PEM" (default), "DER", * and "ENG". * | ** Added in cURL 7.9.3. * | *
| CURLOPT_SSLENGINE | ** The identifier for the crypto engine of the private SSL key * specified in CURLOPT_SSLKEY. * | ** | *
| CURLOPT_SSLENGINE_DEFAULT | ** The identifier for the crypto engine used for asymmetric crypto * operations. * | ** | *
| CURLOPT_SSLKEY | ** The name of a file containing a private SSL key. * | ** | *
| CURLOPT_SSLKEYPASSWD | ** The secret password needed to use the private SSL key specified in * CURLOPT_SSLKEY. * * |
* * | *
| CURLOPT_SSLKEYTYPE | ** The key type of the private SSL key specified in * CURLOPT_SSLKEY. Supported key types are * "PEM" (default), "DER", * and "ENG". * | ** | *
| CURLOPT_URL | ** The URL to fetch. This can also be set when initializing a * session with {@see curl_init()}. * | ** | *
| CURLOPT_USERAGENT | ** The contents of the "User-Agent: " header to be * used in a HTTP request. * | ** | *
| CURLOPT_USERPWD | ** A username and password formatted as * "[username]:[password]" to use for the * connection. * | ** | *
| Option | *Set value to |
* Notes | *
|---|---|---|
| CURLOPT_CAINFO | ** The name of a file holding one or more certificates to verify the * peer with. This only makes sense when used in combination with * CURLOPT_SSL_VERIFYPEER. * | ** Might require an absolute path. * | *
| CURLOPT_CAPATH | ** A directory that holds multiple CA certificates. Use this option * alongside CURLOPT_SSL_VERIFYPEER. * | ** | *
| CURLOPT_COOKIE | ** The contents of the "Cookie: " header to be * used in the HTTP request. * Note that multiple cookies are separated with a semicolon followed * by a space (e.g., "fruit=apple; colour=red") * | ** | *
| CURLOPT_COOKIEFILE | ** The name of the file containing the cookie data. The cookie file can * be in Netscape format, or just plain HTTP-style headers dumped into * a file. * If the name is an empty string, no cookies are loaded, but cookie * handling is still enabled. * | ** | *
| CURLOPT_COOKIEJAR | ** The name of a file to save all internal cookies to when the handle is closed, * e.g. after a call to curl_close. * | ** | *
| CURLOPT_CUSTOMREQUEST | ** A custom request method to use instead of * "GET" or "HEAD" when doing * a HTTP request. This is useful for doing * "DELETE" or other, more obscure HTTP requests. * Valid values are things like "GET", * "POST", "CONNECT" and so on; * i.e. Do not enter a whole HTTP request line here. For instance, * entering "GET /index.html HTTP/1.0\r\n\r\n" * would be incorrect. *
|