From ba041b04a15cfb1aa29be2407b475f68d8c2e2dc Mon Sep 17 00:00:00 2001 From: jayvenn21 Date: Mon, 9 Feb 2026 10:33:25 -0500 Subject: [PATCH] docs: narrow CURLOPT_CLOSESOCKETFUNCTION to defined guarantees --- docs/libcurl/opts/CURLOPT_CLOSESOCKETFUNCTION.md | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/docs/libcurl/opts/CURLOPT_CLOSESOCKETFUNCTION.md b/docs/libcurl/opts/CURLOPT_CLOSESOCKETFUNCTION.md index 66a66e6f28..6ad9a5050f 100644 --- a/docs/libcurl/opts/CURLOPT_CLOSESOCKETFUNCTION.md +++ b/docs/libcurl/opts/CURLOPT_CLOSESOCKETFUNCTION.md @@ -50,14 +50,11 @@ than the transfer itself in the multi/share handle's connection cache. # NOTES ON IDLE CONNECTIONS -The close socket callback is invoked when libcurl closes a socket it owns. -The callback and CURLOPT_CLOSESOCKETDATA(3) are copied from the *first* easy -handle that creates the connection; changing this option on a subsequent -easy handle that reuses the same connection has no effect for that -connection. The callback is not guaranteed to be called for every socket -that leaves use, for example when connections are kept alive in the -connection cache and reused. Applications must not assume the callback is -called for every socket lifecycle. +When using the multi interface, the close socket callback is invoked when +libcurl closes a socket it owns. The callback and CURLOPT_CLOSESOCKETDATA(3) +are copied from the *first* easy handle that creates the connection; +changing this option on a subsequent easy handle that reuses the same +connection has no effect for that connection. # DEFAULT