KNOWN_BUGS: Store TLS context per transfer instead of per connection

Closes #5102

diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index 6613aafe05399fb6dfb024cc83d630efa20d30d5..9b7be5fa958b771fe260e77b28519b79a40efda9 100644 (file)
--- a/docs/KNOWN_BUGS
+++ b/docs/KNOWN_BUGS
@@ -32,6 +32,7 @@ problems may have been fixed or changed somewhat since this was written!
  2.7 Client cert (MTLS) issues with Schannel
  2.8 Schannel disable CURLOPT_SSL_VERIFYPEER and verify hostname
  2.9 TLS session cache doesn't work with TFO
+ 2.10 Store TLS context per transfer instead of per connection
 
  3. Email protocols
  3.1 IMAP SEARCH ALL truncated response
@@ -270,6 +271,16 @@ problems may have been fixed or changed somewhat since this was written!
 
  See https://github.com/curl/curl/issues/4301
 
+2.10 Store TLS context per transfer instead of per connection
+
+ The GnuTLS `backend->cred` and the OpenSSL `backend->ctx` data and their
+ proxy versions (and possibly other TLS backends), could be better moved to be
+ stored in the Curl_easy handle instead of in per connection so that a single
+ transfer that makes multiple connections can reuse the context and reduce
+ memory consumption.
+
+ https://github.com/curl/curl/issues/5102
+
 3. Email protocols
 
 3.1 IMAP SEARCH ALL truncated response