diff options
author | Daniel Stenberg <daniel@haxx.se> | 2020-08-11 15:43:42 +0200 |
---|---|---|
committer | Daniel Stenberg <daniel@haxx.se> | 2020-08-12 07:55:45 +0200 |
commit | cb8cf9d70f6c4768c793bbfe18c27606689583cd (patch) | |
tree | ec86342a415c34a289ec7d2ac27ca7f7145d1898 /docs/libcurl | |
parent | c46339eca10cdc4b9c83bd371835ed987086fb08 (diff) | |
download | curl-cb8cf9d70f6c4768c793bbfe18c27606689583cd.tar.gz |
KNOWN_BUGS: A shared connection cache is not thread-safe
Closes #4915
Closes #5802
Diffstat (limited to 'docs/libcurl')
-rw-r--r-- | docs/libcurl/curl_share_setopt.3 | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/libcurl/curl_share_setopt.3 b/docs/libcurl/curl_share_setopt.3 index 0291d93c2..7a3e2388c 100644 --- a/docs/libcurl/curl_share_setopt.3 +++ b/docs/libcurl/curl_share_setopt.3 @@ -74,10 +74,10 @@ by default. Note this symbol was added in 7.10.3 but was not implemented until 7.23.0. .IP CURL_LOCK_DATA_CONNECT Put the connection cache in the share object and make all easy handles using -this share object share the connection cache. Using this, you can for example -do multi-threaded libcurl use with one handle in each thread, and yet have a -shared pool of unused connections and this way get way better connection -re-use than if you use one separate pool in each thread. +this share object share the connection cache. + +Note that due to a known bug, it is not safe to share connections this way +between multiple concurrent threads. Connections that are used for HTTP/1.1 Pipelining or HTTP/2 multiplexing only get additional transfers added to them if the existing connection is held by |