Capture and inspect HTTP/HTTPS
HTTPeep captures HTTP/1.1, HTTP/2, and HTTPS traffic in real time. Filter by domain, method, status, and path. Export sessions as JSON, HAR, or PCAP.
HTTPeep acts as a local proxy between your application and the internet, intercepting every request and response as it passes through. As soon as you start the proxy, traffic from your browser, terminal, Docker containers, or mobile devices flows through HTTPeep and appears in the session list in real time — no instrumentation or code changes required.
Supported protocols
HTTPeep captures traffic across all modern HTTP transports:
HTTP/1.1
Full request and response capture, including chunked transfer encoding.
HTTP/2
Multiplexed streams captured and displayed per logical request.
HTTPS (MITM)
SSL/TLS traffic decrypted using HTTPeep's built-in root CA. Install the certificate once; all HTTPS sessions are readable from that point on.
To decrypt HTTPS traffic, you must install and trust HTTPeep's root CA certificate. Go to Settings → Certificate and follow the one-click installation for your platform.
The session list
Every captured request appears as a row in the session list. Each row shows:
- Method — GET, POST, PUT, DELETE, and so on
- URL — full request URL including protocol, host, path, and query string
- Status code — HTTP response status (or a connection error indicator)
- Duration — total elapsed time from request sent to response received
- Size — response body size
Click any row to open the detail panel, where you can inspect request and response headers, the full body, and HTTP timing data.
Filtering sessions
When a session list grows long, filtering narrows it down quickly. You can filter across multiple dimensions simultaneously:
| Filter dimension | Examples |
|---|---|
| Domain | api.example.com, *.example.com |
| HTTP method | GET, POST, PUT |
| Status code | 200, 4xx, >=500 |
| Path | /api/users, /checkout |
Filters are applied instantly as you type and can be combined freely.
TCP connection grouping
HTTPeep groups sessions by their underlying TCP connection. This lets you see which requests share a persistent connection, identify connection reuse patterns, and diagnose issues caused by premature connection teardown.
HTTP timing visualization
The detail panel includes an HTTP timing breakdown for each session:
Time spent resolving the hostname.
Time to establish the TCP connection (including TLS handshake for HTTPS).
Time from the request being sent to receiving the first byte of the response.
Time to receive the full response body.
Supported clients
HTTPeep works with any HTTP client that respects proxy settings. Common setups:
Exporting sessions
You can export captured sessions for sharing, archiving, or analysis in other tools.
Exports the full session data in a structured JSON format. Suitable for programmatic processing or loading into custom tooling.
HTTP Archive format. Widely supported by browser DevTools, performance analysis tools, and CI pipelines. Use this when you need to share a session with a colleague or import into another proxy tool.
Raw packet capture format. Open in Wireshark or any PCAP-compatible analyzer for deep network-level inspection.
To export, select one or more sessions in the list, right-click, and choose Export. You can also export all sessions from the File menu.
Use HAR export to reproduce a captured session in a CI environment or to file a detailed bug report that includes exact request/response data.