You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GOAWAY allows an
endpoint to gracefully stop accepting new streams while still
finishing processing of previously established streams
So say when h2::RecvStream.data() gets an GOAWAY error, should we terminate the stream with an error or should we ignore this error (and continue processing)?
The text was updated successfully, but these errors were encountered:
My question is how the APIs of this crate is designed regarding GOAWAY. For example if I get GOAWAY with NO_ERROR (graceful shutdown) when reading, should I just ignore it continue processing my request?
If that is true, what is the point of returning the such errors to streams, just FYI?
The problem: it is not clear what a stream should do when receiving a GOAWAY h2 error.
Per https://datatracker.ietf.org/doc/html/rfc7540#section-6.8
So say when h2::RecvStream.data() gets an GOAWAY error, should we terminate the stream with an error or should we ignore this error (and continue processing)?
The text was updated successfully, but these errors were encountered: