Allow for debug verification of content-length to be disabled
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.3k
- Forks
- 1.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 14
Description
To test the ability of some code to handle responses with invalid content-length, I want to provide a false value for this header and serve that in my test code. Unfortunately, hyper has this debug assertion which fails when trying to serve a request where the content-length header has been manually overridden to an incorrect value.
It would be nice if there was some way to disable this check, or a workaround for this use case.
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 at the debug assertion in src/proto/h1/role.rs around line 687 and trace the server-side response handling used by the test code. Determine how this check could be disabled or bypassed for intentionally incorrect content-length values, then verify that such responses can be served without the assertion failing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100