Join GitHub today
x/net/http2: certain HTTP2 requests sends a "END_STREAM" prematurely #28206
Our organization is using a Go backend in order to send POST API requests to various HTTPS end points.
The example below is for a service called Iterable (api.iterable.com:443), but we see similar problems with others hosts, so we believe there is a problem with the Go HTTP2 stack, somehow. But we are unsure what to look at in order to understand what the causes our failed requests on our environment.
We have noticed that every once and a while, a request just breaks and we get back from Amazon Web Service a
In order to figure out why, I have enabled
I see a pattern where a failing requests does a
However, we can send two requests after each other, same code, same payload and one succeeds and the other might fail.
We have not yet figured out why.
What version of Go are you using (
changed the title
x/net/http2: Trying to figure out why certain HTTP2 requests sends a "END_STREAM" prematurely (got HTTP2 dump)
Oct 15, 2018
I wish I could.
The problem is not deterministic, it happens sporadically. I am not even unable to recreate this locally on my developer Mac computer using the same code. I have only been able to debug this directly in production where we have deployed our app on GCP Kubernetes.
I don't know why.
Just a quick update regarding this issue;
We've been doing tests by changing the client implementations, and we have noticed when using ..