Supporting OPTIONS requests
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 382
- Avg merge
- 20h 23m
- Merged PRs (30d)
- 9
Description
Making OPTIONS requests has turned out to be problematic.
OPTIONS requests can include a "path" component of *. These requests must include a :scheme as well as optionally include a :pseudo header (spec).
Now, the problem is that there isn't a great way to represent these possibilities using the Uri type provided by http.
This also relates to https://github.com/hyperium/http/issues/176.
This is a continuation of this discussion.
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 reviewing the RFC 7540 section linked in the issue, the related hyperium/http issue #176, and the referenced h2 pull-request discussion. Trace how the http crate's Uri represents request paths and determine the requirements for OPTIONS requests with a * path, a required :scheme, and an optional :pseudo header. Done means the representation and handling support these cases consistently.
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