Documentation: How to handle GOAWAY
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 382
- Avg merge
- 20h 23m
- Merged PRs (30d)
- 9
Description
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
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)?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read RFC 7540 §6.8 and inspect the h2::RecvStream.data() behavior referenced in the issue. Determine whether a received GOAWAY should terminate the stream or be ignored while processing continues, then document the agreed behavior and its implications for stream handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100