theupdateframework / theupdateframework/rust-tuf
HttpRepository can bail out early in some cases
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 198
- Forks
- 39
- Avg merge
- 9h 19m
- Merged PRs (30d)
- 2
Description
If a request for metadata or target contains a max length and the HTTP response contains a Content-Length greater than that value, it can error out the AsyncRead stream without having to read the entire payload over the network first.
Contributor guide
No contributing guide indexed for this repository
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
Locate the HttpRepository request handling and its existing tests, then trace how metadata or target responses become an AsyncRead stream. Verify the Content-Length and max-length interaction for oversized responses, and consider the work complete when the stream errors before reading the full payload over the network.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100