HTTP2 GoAway frames don't seem to be handled gracefully in keepalive connections #1041
Unanswered
Tugzrida
asked this question in
Potential Issue
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Using the below minimal example targeting an Nginx server configured with
keepalive_time 30s;, the fourth request through the loop throws aRemoteProtocolErrorafter Nginx sends a GoAway frame.Looking at #733, I've narrowed this down to the fact that this seems to be occurring when
stream_idandlast_stream_idare equal, indeed if I patch that line to bestream_id >= last_stream_id, requests gracefully retry on a new connection.I'm not very familiar with the internals of HTTP2 so I don't know if this is an appropriate fix for all situations, but it would be great if this could work as seamlessly as it does in HTTP/1.
Beta Was this translation helpful? Give feedback.
All reactions