Loading docs/KNOWN_BUGS +8 −0 Original line number Original line Diff line number Diff line Loading @@ -22,6 +22,7 @@ problems may have been fixed or changed somewhat since this was written! 1.8 DNS timing is wrong for HTTP redirects 1.8 DNS timing is wrong for HTTP redirects 1.9 HTTP/2 frames while in the connection pool kill reuse 1.9 HTTP/2 frames while in the connection pool kill reuse 1.10 Strips trailing dot from host name 1.10 Strips trailing dot from host name 1.11 transfer-encoding: chunked in HTTP/2 2. TLS 2. TLS 2.1 Hangs with PolarSSL 2.1 Hangs with PolarSSL Loading Loading @@ -193,6 +194,13 @@ problems may have been fixed or changed somewhat since this was written! See https://github.com/curl/curl/issues/716 for the discussion. See https://github.com/curl/curl/issues/716 for the discussion. 1.11 transfer-encoding: chunked in HTTP/2 For HTTP/1, when -H transfer-encoding:chunked option is given, curl encodes the request using chunked encoding. But when HTTP/2 is being used, the command wrongly sends a request with both content-length and transfer-encoding: chunked headers being set (and the request body is not chunked-encoded). See https://github.com/curl/curl/issues/662 2. TLS 2. TLS Loading Loading
docs/KNOWN_BUGS +8 −0 Original line number Original line Diff line number Diff line Loading @@ -22,6 +22,7 @@ problems may have been fixed or changed somewhat since this was written! 1.8 DNS timing is wrong for HTTP redirects 1.8 DNS timing is wrong for HTTP redirects 1.9 HTTP/2 frames while in the connection pool kill reuse 1.9 HTTP/2 frames while in the connection pool kill reuse 1.10 Strips trailing dot from host name 1.10 Strips trailing dot from host name 1.11 transfer-encoding: chunked in HTTP/2 2. TLS 2. TLS 2.1 Hangs with PolarSSL 2.1 Hangs with PolarSSL Loading Loading @@ -193,6 +194,13 @@ problems may have been fixed or changed somewhat since this was written! See https://github.com/curl/curl/issues/716 for the discussion. See https://github.com/curl/curl/issues/716 for the discussion. 1.11 transfer-encoding: chunked in HTTP/2 For HTTP/1, when -H transfer-encoding:chunked option is given, curl encodes the request using chunked encoding. But when HTTP/2 is being used, the command wrongly sends a request with both content-length and transfer-encoding: chunked headers being set (and the request body is not chunked-encoded). See https://github.com/curl/curl/issues/662 2. TLS 2. TLS Loading