xh
A fast HTTPie-style command-line client for JSON, forms, uploads, authentication, sessions, downloads, redirects and TLS settings.
Friendly HTTP requests with explicit effects
xh uses HTTPie-style request items for JSON, forms, multipart uploads, headers, authentication, sessions, downloads and redirects. Offline mode lets you inspect the request shape before sending traffic.
Treat credentials and methods as data
GET, POST, PUT, PATCH and DELETE have different effects on a service. Keep tokens out of shell history, verbose output, session files and screenshots, and use a small test endpoint before writing to a real system.
TLS and redirects need review
Certificate verification protects the server identity. Fix hostnames, trust chains or a controlled CA rather than making an unverified mode a permanent setting. Limit redirects and inspect the final host before sending credentials.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave xh to this cloud drive
Baidu Netdisk
Save xh to this cloud drive
xh HTTP requests, authentication and TLS workflow
Start with a read-only request to a local or dedicated test API, preview it offline, then add JSON, headers and authentication step by step.
Before you start
- Prepare a local or dedicated API you are allowed to test and non-sensitive sample data.
- Understand the side effects, idempotency and rate limits of each HTTP method.
- Store tokens, sessions and private keys in a restricted location outside shared scripts.
Installation steps
- 01
Extract and inspect the build
Verify xh 0.26.2 and Windows x64, then review version, help and request-item syntax.
- 02
Construct a request offline
Preview URL, method, headers, body, query parameters and file paths before sending network traffic.
- 03
Establish a test output directory
Keep sandbox addresses and non-production credentials in the current session, and save responses to an isolated directory.
Quick start
- 01
Send a read-only GET
Request a permitted test endpoint, inspect status, headers and body, set a reasonable timeout and retain only a redacted diagnostic.
- 02
Send test JSON
Use a small POST in the sandbox, distinguish strings from native JSON types and confirm the service-side result.
- 03
Add authentication and download
Read a token from a protected source, avoid verbose secrets and verify filename, content type, size and checksum after a download.
Usage tips
- Write methods may create, change or remove data; production calls need idempotency and a separate review.
- Session files may contain cookies and auth headers, so restrict permissions and clean or encrypt them after use.
- Redirect following and disabled verification both change the trust boundary; cap redirects and check the final host.
Troubleshooting and uninstall
Why does a browser request work while xh fails?
Compare proxy, DNS, cookies, auth, headers, TLS trust and redirects, then reproduce with offline mode and the smallest request.
Why does the service receive the wrong JSON type?
Check the request-item syntax for strings versus native JSON values, print a redacted request and compare it with the API contract.
- Remove the client and sensitive artifactsCheck scripts and PATH entries, then remove the program directory and review session files, downloads, logs and temporary credentials.
Frequently asked questions
How is xh different from curl or HTTPie?
It combines HTTPie-style request items and formatted output with a native binary focused on quick command-line execution.
How should API tokens be kept out of history?
Read them from a protected source or credential mechanism and review verbose output, sessions, logs and screenshots for leaks.
Should an unverified TLS mode be used permanently?
No. Repair the hostname, trust chain, system time or controlled CA and keep certificate verification enabled for normal requests.
What does offline mode help with?
It previews method, URL, headers and body without sending the request, making it useful for checking side effects before execution.