Terminal

Debug Rust HTTP Traffic

Capture and inspect HTTP/HTTPS requests from Rust applications. Works with reqwest, hyper, ureq, and any client that supports system proxy settings.

HTTPS Decryption
Request & Response Inspection
Works with Rust HTTP Clients
API Mock & Rewrite
Terminal
$hp shell
$cargo run
# Traffic captured → open HTTPeep to inspect

Features

HTTPS Decryption

Automatically intercept and decrypt HTTPS traffic from your terminal commands. Inspect request and response bodies in plain text.

MITMSSLCertificate

Request & Response Inspection

View full HTTP headers, body content, cookies, and timing information for every request made by your scripts and CLI tools.

HeadersBodyTiming

Works with Rust HTTP Clients

Compatible with reqwest, hyper, ureq, surf, and isahc. Most Rust HTTP clients support proxy via environment variables.

reqwesthyperureq

API Mock & Rewrite

Mock API responses or rewrite request/response data without changing your source code. Perfect for testing edge cases.

MockMap LocalRewrite

Breakpoint Debugging

Pause requests matching specific rules, edit headers or body on the fly, then continue or abort. Like a debugger for HTTP.

BreakpointEditIntercept

Debug API Integrations

Inspect outgoing API calls from your Rust backend, CLI tool, or microservice. Trace request chains and identify issues.

BackendCLIMicroservice

Setup Guide

Rust

1

Start hp shell

Run hp shell in your terminal. HTTPeep automatically sets HTTP_PROXY and HTTPS_PROXY environment variables for the current session.

$ hp shell
2

Run your Rust application

Execute your compiled Rust binary. HTTP traffic is automatically routed through HTTPeep.

$ cargo run
3

Inspect captured traffic

Open the HTTPeep desktop app to browse sessions, filter by domain, and inspect request/response details.

4

Set up rules (optional)

Create rules to mock APIs, rewrite responses, set breakpoints, or override DNS for your debugging workflow.

FAQ

Rust

Does reqwest support proxy environment variables?

Yes. reqwest respects HTTP_PROXY and HTTPS_PROXY environment variables by default when using the system proxy feature. hp shell sets these automatically.

Can I debug HTTPS traffic from Rust clients?

Yes. After trusting the HTTPeep root CA certificate, HTTPS traffic from Rust HTTP clients is fully decrypted and visible in HTTPeep.

Does it work with async Rust runtimes (tokio, async-std)?

Yes. HTTPeep handles concurrent connections from async runtimes without issues. The proxy is runtime-agnostic.

Start debugging Rust HTTP traffic

Free to use. Capture, mock, and debug Rust API calls with hp shell.