Proxy & HTTPS / certificates

DevPeek runs a local proxy; point clients at your machine’s proxy port to aggregate traffic. Reading HTTPS requires SSL MITM and trusting the exported/on-device CA.

Recording

Under the Proxy menu, start recording (or equivalent). You can pause refresh per single client tab. Decrypted headers/bodies appear only for hosts on the SSL allowlist with a trusted cert; raw CONNECT tunnels may stay opaque.

System proxy

The same menu can set DevPeek as the system proxy (or clear it). Mobile devices usually need manual Wi‑Fi proxy settings with your computer’s IP and port.

Enable SSL proxy

Turn on SSL proxy in the menu, then edit rules in the SSL proxy configuration dialog: only matching hosts are decrypted; * means all; you can use *.example.com or keyword patterns like *api*. Non-matching connections stay as passthrough tunnels.

Certificate manager

The Certificate manager dialog installs/trusts the CA on desktop, exports files, or shares LAN QR / download link on the same Wi‑Fi. Keep the QR window open until clients finish downloading the cert.

• On desktop, prefer the guided or one-click install flow.
• On iOS/Android, trust the CA in system settings (steps vary by OS version).

Throttling

Toggle throttling in the menu; edit RTT (ms, split across request/response) and up/down bandwidth (kbps, 0 = unlimited) in Throttling configuration. Applies to proxied HTTP/HTTPS; debug preview can reuse the same presets.

Only decrypt where you are authorized; installing a custom CA is risky—use dedicated test devices.