summaryrefslogtreecommitdiff
path: root/docs/FAQ
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2015-03-04 18:24:46 +0100
committerDaniel Stenberg <daniel@haxx.se>2015-03-04 18:24:46 +0100
commitae8235571ffd2f6c79631a2dd9cf90c519abe3a6 (patch)
tree13b07b2f8a1d246f4df1ac4baa90d466f4d0f580 /docs/FAQ
parentac4d08b5e275109bbc7327c94ae714acfa2ff9a7 (diff)
downloadcurl-ae8235571ffd2f6c79631a2dd9cf90c519abe3a6.tar.gz
FAQ: 4.21 Why is there a HTTP/1.1 in my HTTP/2 request?
Diffstat (limited to 'docs/FAQ')
-rw-r--r--docs/FAQ11
1 files changed, 11 insertions, 0 deletions
diff --git a/docs/FAQ b/docs/FAQ
index 0e6496cc4..a2443efbd 100644
--- a/docs/FAQ
+++ b/docs/FAQ
@@ -81,6 +81,7 @@ 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?
@@ -1116,6 +1117,16 @@ FAQ
You can also use the -w option and the variable %{response_code} to extract
the exact response code that was return 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