`http --allow-errors` doesn't work for timeouts
Open
Nobody has claimed this yet.
status:needs-triage
- Dominant language
- Rust
- Stars
- 40.5k
- Forks
- 2.3k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 85
Description
Bug report form
- I have done a basic search of the issue tracker to find any existing issues that are similar.
- I have checked that my version is at least the latest stable release available via my installation method.
Describe the bug
http --allow-errors doesn't work for timeouts
How to reproduce
http get --allow-errors https://timeout.com
error
Expected behavior
I would prefer my scripts not to panic when they get a timeout. Is there a way to catch timeouts with standard http command or i need to use curl for this?
Configuration
| key | value |
|---|---|
| version | 0.114.1 |
| major | 0 |
| minor | 114 |
| patch | 1 |
| branch | |
| commit_hash | |
| build_os | macos-aarch64 |
| build_target | aarch64-apple-darwin |
| rust_version | rustc 1.96.1 (31fca3adb 2026-06-26) (Homebrew) |
| cargo_version | cargo 1.96.1 (356927216 2026-06-26) (Homebrew) |
| build_time | 2026-07-11 15:27:28 +00:00 |
| build_rust_channel | release |
| allocator | standard |
| features | default, lsp, mcp, network, plugin, rustls-tls, sqlite, trash-support |
| installed_plugins | |
| experimental_options | example=false, dc-glob=false, reorder-cell-paths=true, pipefail=true, enforce-runtime-annotations=true, native-clip=false, cell-path-types=false |
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 http get --allow-errors https://timeout.com and trace how the command handles timeout errors. Confirm the expected behavior for scripts and verify that the command no longer reports an unhandled error when a request times out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100