From 65bc6825240175ee4140e0fe8bb2daaf2ebd68e8 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 6 Nov 2020 09:28:49 +0100 Subject: [PATCH] FAQ: remove "Why is there a HTTP/1.1 in my HTTP/2 request?" This hasn't been the case for a while now, remove. --- docs/FAQ | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/docs/FAQ b/docs/FAQ index d2da12e64..e17fee319 100644 --- a/docs/FAQ +++ b/docs/FAQ @@ -78,7 +78,6 @@ FAQ 4.18 file:// URLs containing drive letters (Windows, NetWare) 4.19 Why doesn't curl return an error when the network cable is unplugged? 4.20 curl doesn't return error for HTTP non-200 responses! - 4.21 Why is there a HTTP/1.1 in my HTTP/2 request? 5. libcurl Issues 5.1 Is libcurl thread-safe? @@ -1091,17 +1090,6 @@ FAQ You can also use the -w option and the variable %{response_code} to extract the exact response code that was returned in the response. - 4.21 Why is there a HTTP/1.1 in my HTTP/2 request? - - If you use verbose to see the HTTP request when you send off a HTTP/2 - request, it will still say 1.1. - - The reason for this is that we first generate the request to send using the - old 1.1 style and show that request in the verbose output, and then we - convert it over to the binary header-compressed HTTP/2 style. The actual - "1.1" part from that request is then not actually used in the transfer. - The binary HTTP/2 headers are not human readable. - 5. libcurl Issues 5.1 Is libcurl thread-safe?