Request Inspector — browse and replay tunnel traffic on localhost:4040

​

Open the inspector

rustunnel http 3000

Inspect http://127.0.0.1:4040

​

What you can do

• Request list — live-updating table with method, path, status, and duration. Filter by method, path, or status.
• Detail view
  • Summary — request and response bodies
  • Headers — full request and response headers
  • Raw — reconstructed HTTP messages
• Replay — re-issue any captured request against your local service. Ideal for webhook development: trigger once from Stripe/GitHub/etc., then iterate against the same payload. Replayed rows are marked replay in the list (and ↻ in the terminal UI).

​

Scope and limits

• Captures HTTP tunnels only. TCP and UDP tunnels are raw byte streams; they contribute connection and traffic counters in the terminal UI but no request entries here.
• Keeps the last 500 requests in memory, per process. Nothing is written to disk and nothing survives a restart.
• Bodies are captured up to 64 KB each; larger ones are marked truncated (the reported size is still exact). A truncated request body cannot be replayed byte-for-byte.
• WebSocket and other upgraded connections are recorded as their handshake (101); frames afterwards are not parsed.

​

Configuration

# Prefer port 9090 for the inspector
rustunnel http 3000 --inspect-port 9090

# Disable capture on a shared machine
rustunnel http 3000 --no-inspect

• Terminal UI header (Inspect http://127.0.0.1:…)
• Line under the startup box in line mode
• inspector_ready NDJSON event in --json mode

{"event":"inspector_ready","url":"http://127.0.0.1:4040"}
{"event":"tunnel_ready","protocol":"http","public_url":"https://myapp.eu.edge.rustunnel.com","local_port":3000,"local_host":"localhost"}

​

Security

​

Related