Home
last modified time | relevance | path

Searched refs:persistent (Results 1 – 14 of 14) sorted by relevance

/curl/tests/data/
H A Dtest1466 persistent connection
23 persistent FTP with different paths
H A Dtest1837 persistent connection
28 HTTP GET two URLs over a single proxy with persistent connection
H A Dtest109835 FTP RETR twice over proxy confirming persistent connection
H A Dtest15426 persistent connection
/curl/docs/libcurl/opts/
H A DCURLINFO_NUM_CONNECTS.md34 persistent connections to save time.
H A DCURLOPT_MAXCONNECTS.md35 that support persistent connections.
/curl/docs/examples/
H A D.gitignore75 persistent
H A DMakefile.inc94 persistent \
/curl/docs/libcurl/
H A Dlibcurl-easy.md52 curl_easy_cleanup(3). If you want persistent connections, you do not cleanup
H A Dlibcurl.md140 libcurl always attempts to use persistent connections. Whenever you use
146 To allow libcurl to take full advantage of persistent connections, you should
H A Dlibcurl-tutorial.md1428 better allow persistent connections and connection reuse is also shared. If
/curl/tests/server/
H A Drtspd.c773 bool persistent = TRUE; in send_doc() local
912 persistent = FALSE; in send_doc()
1042 req->open = persistent; in send_doc()
H A Dsws.c1017 bool persistent = TRUE; in send_doc() local
1149 persistent = FALSE; in send_doc()
1275 req->open = use_gopher ? FALSE : persistent; in send_doc()
/curl/docs/
H A DFAQ89 5.6 What about Keep-Alive or persistent connections?
1175 will enable libcurl to use persistent connections.
1191 5.6 What about Keep-Alive or persistent connections?
1193 curl and libcurl have excellent support for persistent connections when

Completed in 44 milliseconds