KNOWN_BUGS: Excessive HTTP/2 packets with TCP_NODELAY

Reported-by: Alex Xu
Closes #6363

diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index 90a88bc39962924aae5bf138789cf2c87b054a28..16d979d58bff54682fa96323ff687a206eca69f3 100644 (file)
--- a/docs/KNOWN_BUGS
+++ b/docs/KNOWN_BUGS
@@ -12,6 +12,7 @@ check the changelog of the current development status, as one or more of these
 problems may have been fixed or changed somewhat since this was written!
 
  1. HTTP
+ 1.1 Excessive HTTP/2 packets with TCP_NODELAY
  1.2 Multiple methods in a single WWW-Authenticate: header
  1.3 STARTTRANSFER time is wrong for HTTP POSTs
  1.4 multipart formposts file name encoding
@@ -146,6 +147,16 @@ problems may have been fixed or changed somewhat since this was written!
 
 1. HTTP
 
+1.1 Excessive HTTP/2 packets with TCP_NODELAY
+
+ Because of how curl sets TCP_NODELAY by default, HTTP/2 requests are issued
+ using more separate TCP packets than it would otherwise need to use. This
+ means spending more bytes than it has to. Just disabling TCP_NODELAY for
+ HTTP/2 is also not the correct fix because that then makes the outgoing
+ packets to get delayed.
+
+ See https://github.com/curl/curl/issues/6363
+
 1.2 Multiple methods in a single WWW-Authenticate: header
 
  The HTTP responses headers WWW-Authenticate: can provide information about