HTTP debugger CLI — tools.voiddo/httpwut vs HTTPie
Both make HTTP requests from the terminal. HTTPie has the most readable request syntax available. httpwut is focused on why requests fail: DNS/TCP/TLS timing, redirect chains, endpoint diffing, and 5xx retry.
tools.voiddo/httpwut
- DNS lookup + TCP handshake + TLS negotiation + TTFB timing
- Full redirect chain with per-hop timing display
- Endpoint diff: compare two URLs' responses structurally
- Retry on 5xx with configurable delay and max attempts
- Emit curl command for any request made
- JSON output mode for scripting and CI
- Zero deps, Node 14+, MIT licensed
HTTPie
- Human-friendly request syntax — the most readable HTTP CLI
- Colored, formatted JSON response display
- Session support, persistent headers and cookies
- Plugin ecosystem (OAuth, AWS signing, etc.)
- Large community; widely referenced in API docs
- No timing breakdown; no redirect chain detail; no endpoint diff
- Python-based or standalone binary
Feature comparison
| Feature | tools.voiddo/httpwut | HTTPie |
|---|---|---|
| GET / POST / PUT / DELETE requests | ✓ | ✓ |
| Colored JSON response display | ✓ | ✓ |
| Custom headers | ✓ | ✓ |
| Request body (JSON / form) | ✓ | ✓ |
| Follow redirects | ✓ | ✓ |
| Human-friendly request syntax | standard flags | ✓ key=value shorthand |
| Session / persistent cookies | — | ✓ |
| Plugin ecosystem | — | ✓ OAuth, AWS sig… |
| DNS lookup timing | ✓ | ✗ |
| TCP handshake timing | ✓ | ✗ |
| TLS negotiation timing | ✓ | ✗ |
| Time to first byte (TTFB) | ✓ | ✗ |
| Redirect chain with per-hop timing | ✓ | follows redirects only |
| Endpoint diff (two URLs) | ✓ | ✗ |
| Retry on 5xx | ✓ | ✗ |
| Emit curl command | ✓ | ✗ |
| JSON output for scripting | ✓ | partial |
| No Python required | ✓ Node only | Python 3.7+ or binary |
| Open source | ✓ MIT | ✓ BSD-3-Clause |
Comparison based on publicly observable behavior as of 2026-05. For interactive API exploration with a readable syntax and sessions, HTTPie remains the better tool. For diagnosing slow requests, redirect issues, or endpoint regressions, httpwut provides data HTTPie does not.
FAQ
What timing data does httpwut show that HTTPie does not?
httpwut shows a full per-phase breakdown: DNS lookup duration, TCP handshake duration, TLS negotiation duration (for HTTPS), time to first byte (TTFB), and total transfer time. This tells you immediately whether a slow response is caused by DNS, TLS, or server processing. HTTPie shows the response body and status code but no timing breakdown.
How does the endpoint diff command work?
Run
httpwut diff https://api.example.com/v1/endpoint https://api.example.com/v2/endpoint. httpwut makes both requests concurrently, parses the JSON responses, and outputs a structural diff — which keys are present in one but not the other, which values changed, which arrays grew or shrank. Useful for comparing API versions without manual inspection.Is HTTPie still the better choice for most use cases?
Yes, for interactive API exploration. HTTPie's shorthand syntax (
http POST api.example.com/login email=me@example.com password=secret Authorization:"Bearer $TOKEN") is far more readable than curl or httpwut flags. HTTPie also has session support, a plugin ecosystem, and a large community. Use HTTPie when you want to explore or test an API quickly.Can httpwut retry a request that returns 503?
Yes. Use
httpwut get https://api.example.com/data --retry 3 --retry-delay 2000. httpwut retries up to 3 times with a 2-second delay between attempts on any 5xx response, then returns the final result. HTTPie makes one request and returns immediately regardless of status code.Can httpwut output a curl command I can share with someone?
Yes. Add
--emit-curl to any httpwut command and it prints the equivalent curl command before making the request. Useful for sharing reproducible examples in Slack, GitHub issues, or runbooks where the recipient may not have Node.js installed.When would I still choose HTTPie over httpwut?
Use HTTPie when: (1) you want the most readable request syntax for interactive API testing; (2) you need session management with persistent cookies; (3) you use OAuth, AWS request signing, or other plugins from the HTTPie ecosystem; (4) you prefer Python-based tooling or the standalone binary without Node.js. httpwut complements HTTPie — it is best when you already know a request is working and want to understand why it is slow or inconsistent.
Try tools.voiddo/httpwut
Diagnose HTTP requests with DNS/TCP/TLS timing, redirect chain tracing, endpoint diff, and 5xx retry. Emits curl commands. Zero deps.
Competitor names and trademarks belong to their respective owners. This comparison reflects publicly observable tool behavior.