Capture Requests in Terminal

This document verifies that "non-browser traffic" is correctly routed into HTTPeep. It applies to curl, scripts, backend service local debugging, and similar scenarios.

1. Confirm the Proxy Service Is Running

In HTTPeep, click Start and confirm the system proxy is enabled.

2. Send Your First Request with curl

Run the following command in your terminal:

curl -v https://httpbin.org/get

Then return to HTTPeep and check whether httpbin.org appears in the session list.

3. Explicitly Set Terminal Proxies (Recommended)

The easiest scoped setup is:

hp shell

This opens a child shell with HTTPeep proxy variables and runtime hooks already loaded. Commands launched from that shell, including curl, package managers, Node.js, Python, Ruby, and JVM tools, inherit the capture environment.

To make script behavior predictable, we recommend explicitly setting the proxy environment variables:

export HTTP_PROXY=http://127.0.0.1:8080
export HTTPS_PROXY=http://127.0.0.1:8080
export NO_PROXY=localhost,127.0.0.1

Then run again:

curl -v https://example.com

You should now reliably see this session in HTTPeep.

4. Handling HTTPS Request Failures

If you encounter TLS/certificate-related errors, troubleshoot in this order:

1. Confirm the HTTPeep Root CA is trusted on your system.
2. Close and reopen Terminal so the new certificate/proxy settings take effect.
3. Use curl -v to inspect handshake logs and identify the failure stage.

For temporary diagnostics, you can skip certificate verification with -k:

curl -vk https://example.com

5. Quick Self-Checklist

• HTTPeep is in the Start state
• Terminal has correct HTTP_PROXY / HTTPS_PROXY set
• Target domain is not excluded by NO_PROXY
• Root CA is installed and trusted
• Request is actually sent (verify with curl -v first)

Next Steps