hyper (via reqwest) reports "invalid HTTP header parsed"
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.3k
- Forks
- 1.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 14
Description
I'm trying to work with an API on an internal server, and hyper keeps blowing away the connection due to "invalid HTTP header parsed". There doesn't appear to be a specific error provided, however, which has so far made it impossible to troubleshoot. I've enabled RUST_LOG=trace and even tried switching off certificate and domain name checks and gzip, is there any way to get it to work or at least figure out what hyper thinks is wrong with the header?
Both curl and Postman appear to work fine, and testssl doesn't reveal any glaring issues.
Thanks.
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 reproducing the failure through reqwest against the internal server with RUST_LOG=trace enabled, then compare the response behavior with curl and Postman. Determine which HTTP header causes hyper's parsing failure and provide a specific diagnostic error or a confirmed compatibility fix; the issue does not name a source file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100