Searched refs:sessions (Results 1 – 8 of 8) sorted by relevance
82 struct Curl_llist sessions; member177 Curl_llist_destroy(&peer->sessions, NULL); in cf_ssl_scache_clear_peer()245 DEBUGASSERT(Curl_node_llist(&s->list) == &peer->sessions); in cf_scache_session_remove()304 Curl_llist_init(&scache->peers[i].sessions, in Curl_ssl_scache_create()650 !Curl_llist_count(&scache->peers[i].sessions)) { in cf_ssl_add_peer()721 Curl_llist_destroy(&peer->sessions, NULL); in cf_scache_peer_add_session()722 Curl_llist_append(&peer->sessions, s, &s->list); in cf_scache_peer_add_session()728 Curl_llist_append(&peer->sessions, s, &s->list); in cf_scache_peer_add_session()730 Curl_node_remove(Curl_llist_head(&peer->sessions)); in cf_scache_peer_add_session()743 Curl_llist_count(&peer->sessions)); in cf_scache_peer_add_session()[all …]
23 HTTP/2 to negotiate HTTP/2 support with the server during https sessions.
26 HTTP/2 to negotiate HTTP/2 support with the server during https sessions.
41 SSL sessions and no cookies. It also does not inherit any share object states
82 WebSocket is designed to allow long-lived sessions and in order to keep the
1165 update them. Server use cookies to "track" users and to keep "sessions".
34 CURLMOPT_MAX_HOST_CONNECTIONS(3). When the limit is reached, new sessions are
60 It is not supported to share SSL sessions between multiple concurrent threads.
Completed in 16 milliseconds