custom SETTINGS settings
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 382
- Avg merge
- 20h 23m
- Merged PRs (30d)
- 9
Description
I'd like to use settings that aren't supported by this library. Experimenting locally it seems fairly trivial to track custom settings in a (u16, u32) map. I'd be happy to contribute the change. One thing I wonder is whether you should have to specify settings IDs that you will accept, so that a misbehaved remote cannot fill up your local settings with 65k entries.
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 locating the HTTP/2 SETTINGS handling and its tests in the h2 repository, then trace how setting IDs and values are currently validated and stored. Clarify whether unknown settings are accepted and how storage is bounded; done should include an agreed behavior, implementation coverage, and tests for custom settings and the limit.
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
- 30/100