From: Daniel Stenberg <daniel@haxx.se>
Date: Thu, 7 Sep 2023 16:08:57 +0000 (+0200)
Subject: curl_multi_remove_handle.3: clarify what happens with connection
X-Git-Tag: curl-8_3_0~20
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=28f8440c0b83be1b617142642dae5cee3ba2a2e5;p=thirdparty%2Fcurl.git

curl_multi_remove_handle.3: clarify what happens with connection

Closes #11817
---

diff --git a/docs/libcurl/curl_multi_remove_handle.3 b/docs/libcurl/curl_multi_remove_handle.3
index c9205479af..7e129ce017 100644
--- a/docs/libcurl/curl_multi_remove_handle.3
+++ b/docs/libcurl/curl_multi_remove_handle.3
@@ -43,6 +43,13 @@ handles and transfers remain unaffected.
 
 It is fine to remove a handle at any time during a transfer, just not from
 within any libcurl callback function.
+
+Removing an easy handle from the multi handle before the corresponding
+transfer is complete might cause libcurl to close the connection - if the
+state of it and the internal protocol handler deem it necessary. Otherwise
+libcurl keeps the connection alive in the connection pool associated with the
+multi handle, ready to get reused for a future transfer using this multi
+handle.
 .SH EXAMPLE
 .nf
 /* when an easy handle has completed, remove it */