Closed yushni closed 2 years ago
Are you able to share a small reproducer program to help us understand the issue?
As it stands, it's hard to say what's going wrong here.
CC @neild via https://dev.golang.org/owners
Is there a possibility that you make too much request (or too frequently) so you are blocked by the server?
I've meet this problem when using http 1.1, and adding a http keep alive header solved my problem.
@MakDon, yes I do a huge amount of requests. As far as I know, http2 doesn't support the keep-alive header.
Anyway, I set up the EnableKeepAlive
on the server-side and set IdleConnTimeout
to 0 (unlimited) client-side.
@mknyszek it is complicated, I don't have steps on how it is possible to reproduce locally. It happens only in one working environment
Timed out in state WaitingForInfo. Closing.
(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)
What version of Go are you using (
go version
)?1.16.4
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?linux, amd64
go env
OutputWhat did you do?
Do many calls to the server, and in one of the messages i receive 200 OK status, read some part of body and then get a GOAWAY or read: reset by peer error.
What did you expect to see?
I expected to get an error
What did you see instead?
I see status 200, start read the body and only then see error