Client bug: Send request, then send reset before original HEADERS are flushed
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 382
- Avg merge
- 20h 23m
- Merged PRs (30d)
- 9
Description
It looks like this will cause the original HEADERS frame to be dropped and a RST_STREAM frame sent for that ID, which would be a connection level error.
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
Trace the Rust client handling for sending a request and then resetting its stream before the original HEADERS are flushed. Reproduce or inspect the resulting HTTP/2 frame sequence; done means the original HEADERS is not dropped and the reset does not become an invalid connection-level error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100