-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/net/http2: http.Server.WriteTimeout does not fire if the http2 stream's window is out of space. [1.17 backport] #49921
Comments
Change https://golang.org/cl/375719 mentions this issue: |
…n random write scheduler The http2 random write scheduler should not queue RST_STREAM frames with the DATA frames, and instead treat them as control frames. There can be deadlock situations if data frames block the queue, because if the sender wants to close the stream it sends an RST frame, but if the client is not draining the queue, the RST frame is stuck and the sender is not able to finish. For golang/go#49741 Updates golang/go#49921 Change-Id: I0940a76d1aad95f1c4d3856e4d79cf5ce2a78ff2 Reviewed-on: https://go-review.googlesource.com/c/net/+/367154 Trust: Dave Cheney <[email protected]> Reviewed-by: Damien Neil <[email protected]> Trust: Damien Neil <[email protected]> Run-TryBot: Damien Neil <[email protected]> TryBot-Result: Gopher Robot <[email protected]> (cherry picked from commit 04296fa) Reviewed-on: https://go-review.googlesource.com/c/net/+/375719 Run-TryBot: Carlos Amedee <[email protected]> Trust: Dmitri Shuralyov <[email protected]>
Change https://golang.org/cl/375814 mentions this issue: |
This backport has been approved as it is a serious issue without a workaround. |
Pull in approved backports to golang.org/x/net/http2: 21a9c9c http2: prioritize RST_STREAM frames in random write scheduler By doing: $ go get -d golang.org/x/[email protected] $ go mod tidy $ go mod vendor $ go generate -run=bundle std Fixes #49921 Change-Id: I04739a30d84a8ae449374eca8bb11c7d2d215ad9 Reviewed-on: https://go-review.googlesource.com/c/go/+/375814 Run-TryBot: Carlos Amedee <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Trust: Carlos Amedee <[email protected]>
Closed by merging dbdf055 to release-branch.go1.17. |
…n random write scheduler The http2 random write scheduler should not queue RST_STREAM frames with the DATA frames, and instead treat them as control frames. There can be deadlock situations if data frames block the queue, because if the sender wants to close the stream it sends an RST frame, but if the client is not draining the queue, the RST frame is stuck and the sender is not able to finish. For golang/go#49741 Updates golang/go#49921 Change-Id: I0940a76d1aad95f1c4d3856e4d79cf5ce2a78ff2 Reviewed-on: https://go-review.googlesource.com/c/net/+/367154 Trust: Dave Cheney <[email protected]> Reviewed-by: Damien Neil <[email protected]> Trust: Damien Neil <[email protected]> Run-TryBot: Damien Neil <[email protected]> TryBot-Result: Gopher Robot <[email protected]> (cherry picked from commit 04296fa82e83b85317bd93ad50dd00460d6d7940) Reviewed-on: https://go-review.googlesource.com/c/net/+/375719 Run-TryBot: Carlos Amedee <[email protected]> Trust: Dmitri Shuralyov <[email protected]>
@mknyszek requested issue #49741 to be considered for backport to the next 1.17 minor release.
The text was updated successfully, but these errors were encountered: