net/http: race between operations on maxClientStreamID and inGoAway. #51309
Labels
FrozenDueToAge
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yeah, maybe. I haven't reproduced it yet.
Just found this issue based on code.
race may happen on such a flow:
The server may have already processed the new request while the client got the old stream id in the GoAway frame,
and the client will retry the new request again.
Yeah, the race is very very small, but I think it indeed exists in theory.
eg. these three things happen at the same time:
Or, do I misunderstand the code?
Thanks!
The text was updated successfully, but these errors were encountered: