From: Daniel Stenberg <daniel@haxx.se>
Date: Mon, 13 Nov 2023 11:48:41 +0000 (+0100)
Subject: curl_easy_duphandle.3: clarify how HSTS and alt-svc are duped
X-Git-Tag: curl-8_5_0~106
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=5b686e34fbd96497e02ac6932fd4a6c4e39577cd;p=thirdparty%2Fcurl.git

curl_easy_duphandle.3: clarify how HSTS and alt-svc are duped

Closes #12315
---

diff --git a/docs/libcurl/curl_easy_duphandle.3 b/docs/libcurl/curl_easy_duphandle.3
index f66c1dffb4..007efa57e7 100644
--- a/docs/libcurl/curl_easy_duphandle.3
+++ b/docs/libcurl/curl_easy_duphandle.3
@@ -45,6 +45,9 @@ The new handle does \fBnot\fP inherit any state information, no connections,
 no SSL sessions and no cookies. It also does not inherit any share object
 states or options (created as if \fICURLOPT_SHARE(3)\fP was set to NULL).
 
+If the source handle has HSTS or alt-svc enabled, the duplicate gets data read
+data from the main file name to populate the cache.
+
 In multi-threaded programs, this function must be called in a synchronous way,
 the input handle may not be in use when cloned.
 .SH EXAMPLE