2024-03-16 02:55:33 +00:00
|
|
|
.\" generated by cd2nroff 0.1 from CURLOPT_SSL_SESSIONID_CACHE.md
|
2024-06-01 20:49:19 +00:00
|
|
|
.TH CURLOPT_SSL_SESSIONID_CACHE 3 "2024-06-01" libcurl
|
2024-03-16 02:55:33 +00:00
|
|
|
.SH NAME
|
|
|
|
CURLOPT_SSL_SESSIONID_CACHE \- use the SSL session\-ID cache
|
|
|
|
.SH SYNOPSIS
|
|
|
|
.nf
|
|
|
|
#include <curl/curl.h>
|
|
|
|
|
|
|
|
CURLcode curl_easy_setopt(CURL *handle, CURLOPT_SSL_SESSIONID_CACHE,
|
|
|
|
long enabled);
|
|
|
|
.fi
|
|
|
|
.SH DESCRIPTION
|
|
|
|
Pass a long set to 0 to disable libcurl\(aqs use of SSL session\-ID caching. Set
|
|
|
|
this to 1 to enable it. By default all transfers are done using the cache
|
|
|
|
enabled. While nothing ever should get hurt by attempting to reuse SSL
|
|
|
|
session\-IDs, there seem to be or have been broken SSL implementations in the
|
|
|
|
wild that may require you to disable this in order for you to succeed.
|
|
|
|
.SH DEFAULT
|
|
|
|
1
|
|
|
|
.SH PROTOCOLS
|
2024-03-30 18:28:04 +00:00
|
|
|
All TLS based protocols: HTTPS, FTPS, IMAPS, POP3S, SMTPS etc.
|
|
|
|
|
|
|
|
All TLS backends support this option.
|
2024-03-16 02:55:33 +00:00
|
|
|
.SH EXAMPLE
|
|
|
|
.nf
|
|
|
|
int main(void)
|
|
|
|
{
|
|
|
|
CURL *curl = curl_easy_init();
|
|
|
|
if(curl) {
|
|
|
|
CURLcode res;
|
|
|
|
curl_easy_setopt(curl, CURLOPT_URL, "https://example.com/");
|
|
|
|
/* switch off session-id use! */
|
|
|
|
curl_easy_setopt(curl, CURLOPT_SSL_SESSIONID_CACHE, 0L);
|
|
|
|
res = curl_easy_perform(curl);
|
|
|
|
curl_easy_cleanup(curl);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
.fi
|
|
|
|
.SH AVAILABILITY
|
|
|
|
Added in 7.16.0
|
|
|
|
.SH RETURN VALUE
|
|
|
|
Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not.
|
|
|
|
.SH SEE ALSO
|
|
|
|
.BR CURLOPT_DNS_CACHE_TIMEOUT (3),
|
|
|
|
.BR CURLOPT_MAXAGE_CONN (3),
|
|
|
|
.BR CURLOPT_MAXLIFETIME_CONN (3),
|
|
|
|
.BR CURLOPT_SSLVERSION (3)
|