access to SETTINGS frame as received from client for HTTP/2 connection
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.3k
- Forks
- 1.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem? Please describe.
I can currently not get access (AFAIK) to the settings as received in the SETTINGS frame by the HTTP/2 client.
https://httpwg.org/specs/rfc7540.html#rfc.section.6.5.2
Describe the solution you'd like
Ability to listen for these somehow such that this information is known and can be acted upon.
Describe alternatives you've considered
I do not see alternatives, I need this information,
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
Start by tracing how hyper receives and processes the client's HTTP/2 SETTINGS frame. Determine where an API could expose these settings and how callers would receive them, then define tests that verify the client-provided values are observable and actionable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100