Figure out what to do about informational status codes
Open
Nobody has claimed this yet.
question
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 382
- Avg merge
- 20h 23m
- Merged PRs (30d)
- 9
Description
An HTTP/2.0 stream can begin with an arbitrary number of header frames with a 1xx status code.
The current API does not support this. My best guess would be doing something like this:
client
ResponseFuture is modified to be a future of (naming TBD):
enum Head {
Informational(ResponseFuture),
Response(Response<RecvBody>),
}
server
Respond gets a new fn: send_informational(response: Response<()>).
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 the client ResponseFuture and the server Respond API mentioned in the issue. Determine how arbitrary 1xx header frames should be represented on the client and sent on the server; done means both APIs support informational responses while preserving the final response and body flow.
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
- Mostly clear
- Newbie friendliness
- 25/100