KNOWN_BUGS: Deflate error after all content was received

Closes #2719
This commit is contained in:
Daniel Stenberg 2019-02-14 10:46:18 +01:00
parent 28177def43
commit 917b1bb192
No known key found for this signature in database
GPG Key ID: 5CC908FDB71E12C2
1 changed files with 10 additions and 0 deletions

View File

@ -18,6 +18,7 @@ problems may have been fixed or changed somewhat since this was written!
1.4 multipart formposts file name encoding 1.4 multipart formposts file name encoding
1.5 Expect-100 meets 417 1.5 Expect-100 meets 417
1.6 Unnecessary close when 401 received waiting for 100 1.6 Unnecessary close when 401 received waiting for 100
1.7 Deflate error after all content was received
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 CURLOPT_SEEKFUNCTION not called with CURLFORM_STREAM 1.11 CURLOPT_SEEKFUNCTION not called with CURLFORM_STREAM
@ -154,6 +155,15 @@ problems may have been fixed or changed somewhat since this was written!
waiting for the the 100-continue response. waiting for the the 100-continue response.
https://curl.haxx.se/mail/lib-2008-08/0462.html https://curl.haxx.se/mail/lib-2008-08/0462.html
1.7 Deflate error after all content was received
There's a situation where we can get an error in a HTTP response that is
compressed, when that error is detected after all the actual body contents
have been received and delivered to the appliction. This is tricky, but is
ultimately a broken server.
See https://github.com/curl/curl/issues/2719
1.9 HTTP/2 frames while in the connection pool kill reuse 1.9 HTTP/2 frames while in the connection pool kill reuse
If the server sends HTTP/2 frames (like for example an HTTP/2 PING frame) to If the server sends HTTP/2 frames (like for example an HTTP/2 PING frame) to