hyper::Error is not precise enough to support Proxy-Status well
Open
Nobody has claimed this yet.
A-error
- Dominant language
- Rust
- Stars
- 16.3k
- Forks
- 1.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 14
Description
This issue is a more general version of #2462, with the aim of supporting all possible errors defined in https://tools.ietf.org/html/draft-ietf-httpbis-proxy-status-04#section-2.3
hyper::Error should be equipped with new methods to distinguish between:
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 reading hyper::Error and the related issue #2462, then compare the existing error distinctions with the Proxy-Status section 2.3 definitions. Done means the seven listed response errors can be distinguished through new hyper::Error methods, with behavior aligned to the specification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100