From: Daniel Stenberg <daniel@haxx.se>
Date: Fri, 3 Apr 2020 22:01:35 +0000 (+0200)
Subject: KNOWN_BUGS: Store TLS context per transfer instead of per connection
X-Git-Tag: curl-7_70_0~143
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0c511b44ffd9fa93a791d6e16fc9a0076091f5b2;p=thirdparty%2Fcurl.git

KNOWN_BUGS: Store TLS context per transfer instead of per connection

Closes #5102
---

diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index 6613aafe05..9b7be5fa95 100644
--- 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