You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When reading a gzipped response body (via an *http2.gzipReader), closing the body doesn't necessarily cause subsequent reads to fail because gzipReader.Close only closes the underlying response body. Buffered data in the gzip.Reader can still be read.
This causes the existing test TestTransportGzip to fail when run in HTTP/2 mode.
The text was updated successfully, but these errors were encountered:
neild
added
the
NeedsFix
The path to resolution is known, but the work has not been done.
label
Oct 4, 2022
The existing implementation does not reset gz.zr. After Close,
gzipReader closes underlying response body but buffered data can still
be read.
gzipReader on Close sets the gz.zerr to fs.ErrClosed so next Read after
Close will return it immediately.
Fixesgolang/go#56020
Change-Id: I8a31e4c65656b9abc3023855b8e04342e1e77cbb
Reviewed-on: https://go-review.googlesource.com/c/net/+/440555
Reviewed-by: Damien Neil <dneil@google.com>
Run-TryBot: Damien Neil <dneil@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Than McIntosh <thanm@google.com>
When reading a gzipped response body (via an
*http2.gzipReader
), closing the body doesn't necessarily cause subsequent reads to fail becausegzipReader.Close
only closes the underlying response body. Buffered data in thegzip.Reader
can still be read.This causes the existing test
TestTransportGzip
to fail when run in HTTP/2 mode.The text was updated successfully, but these errors were encountered: