-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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: Client doesn't send body until ExpectContinueTimeout expires #49677
Comments
cc @neild |
Change https://golang.org/cl/363914 mentions this issue: |
@gopherbot Please open backport issues for 1.16 and 1.17. This is a regression. |
Backport issue(s) opened: #49904 (for 1.16), #49905 (for 1.17). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://golang.org/wiki/MinorReleases. |
Change https://golang.org/cl/368474 mentions this issue: |
Change https://golang.org/cl/368475 mentions this issue: |
…tinue Recent refactoring in the http2 package broke handling of ExpectContinueTimeout, where the client was always waiting for the timeout to pass before sending the body. For golang/go#49677 Fixes golang/go#49904 Change-Id: I565299e48313bb905b2655bd52084ea49ab742f3 GitHub-Last-Rev: 587b484 GitHub-Pull-Request: #118 Reviewed-on: https://go-review.googlesource.com/c/net/+/363914 Reviewed-by: Damien Neil <dneil@google.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Trust: Damien Neil <dneil@google.com> Run-TryBot: Damien Neil <dneil@google.com> (cherry picked from commit 0a0e4e1) Reviewed-on: https://go-review.googlesource.com/c/net/+/368474 TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Michael Knyszek <mknyszek@google.com>
…tinue Recent refactoring in the http2 package broke handling of ExpectContinueTimeout, where the client was always waiting for the timeout to pass before sending the body. For golang/go#49677 Fixes golang/go#49905 Change-Id: I565299e48313bb905b2655bd52084ea49ab742f3 GitHub-Last-Rev: 587b484 GitHub-Pull-Request: #118 Reviewed-on: https://go-review.googlesource.com/c/net/+/363914 Reviewed-by: Damien Neil <dneil@google.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Trust: Damien Neil <dneil@google.com> Run-TryBot: Damien Neil <dneil@google.com> (cherry picked from commit 0a0e4e1) Reviewed-on: https://go-review.googlesource.com/c/net/+/368475 Reviewed-by: Michael Knyszek <mknyszek@google.com> Run-TryBot: Michael Knyszek <mknyszek@google.com> TryBot-Result: Go Bot <gobot@golang.org>
Recent refactoring in the http2 package broke handling of ExpectContinueTimeout, where the client was always waiting for the timeout to pass before sending the body. Fixes: golang/go#49677 Change-Id: I565299e48313bb905b2655bd52084ea49ab742f3 GitHub-Last-Rev: 587b48407932d44b26399b6c0b4ac228e6889ac8 GitHub-Pull-Request: golang/net#118 Reviewed-on: https://go-review.googlesource.com/c/net/+/363914 Reviewed-by: Damien Neil <dneil@google.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Trust: Damien Neil <dneil@google.com> Run-TryBot: Damien Neil <dneil@google.com>
…tinue Recent refactoring in the http2 package broke handling of ExpectContinueTimeout, where the client was always waiting for the timeout to pass before sending the body. For golang/go#49677 Fixes golang/go#49905 Change-Id: I565299e48313bb905b2655bd52084ea49ab742f3 GitHub-Last-Rev: 587b48407932d44b26399b6c0b4ac228e6889ac8 GitHub-Pull-Request: golang/net#118 Reviewed-on: https://go-review.googlesource.com/c/net/+/363914 Reviewed-by: Damien Neil <dneil@google.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Trust: Damien Neil <dneil@google.com> Run-TryBot: Damien Neil <dneil@google.com> (cherry picked from commit 0a0e4e1bb54c236434124a1fa7b0a400de92f2cc) Reviewed-on: https://go-review.googlesource.com/c/net/+/368475 Reviewed-by: Michael Knyszek <mknyszek@google.com> Run-TryBot: Michael Knyszek <mknyszek@google.com> TryBot-Result: Go Bot <gobot@golang.org>
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
This is a problem with x/net master
What did you do?
Set a non-zero timeout for ExpectContinueTimeout on http.Transport and sent a POST request with
Expect: 100-continue
over h2.What did you expect to see?
The request uploads the data and finishes.
What did you see instead?
The data doesn't start uploading until after the specified timeout expires, adding extra latency.
The text was updated successfully, but these errors were encountered: