We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The check to see if a ClientConn is at its stream limit has an off-by-one error (< instead of <=), limiting a conn to one fewer stream than the server-provided limit: https://go.googlesource.com/net/+/refs/heads/master/http2/transport.go#797
<
<=
There are actually two checks against this limit; the other one is correct: https://go.googlesource.com/net/+/refs/heads/master/http2/transport.go#1203
The text was updated successfully, but these errors were encountered:
Change https://golang.org/cl/349490 mentions this issue: http2: fix off-by-one error in client check for max concurrent streams
http2: fix off-by-one error in client check for max concurrent streams
Sorry, something went wrong.
golang/net@943fd67
7295347
Fixes golang/go#48358. Change-Id: Ib4eb93702b32ae7d03cad17ca0b997d5e6a58ad7 Reviewed-on: https://go-review.googlesource.com/c/net/+/349490 Trust: Damien Neil <dneil@google.com> Run-TryBot: Damien Neil <dneil@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
No branches or pull requests
The check to see if a ClientConn is at its stream limit has an off-by-one error (
<
instead of<=
), limiting a conn to one fewer stream than the server-provided limit:https://go.googlesource.com/net/+/refs/heads/master/http2/transport.go#797
There are actually two checks against this limit; the other one is correct:
https://go.googlesource.com/net/+/refs/heads/master/http2/transport.go#1203
The text was updated successfully, but these errors were encountered: