Show HN: Oproxy – inspect and modify network traffic from the browser
Key takeaways
- It is for developers testing browsers, CLIs, mobile apps, API clients, services, and test suites on their own machine or in a local Docker container.
- Capture HTTP traffic and HTTPS traffic after trusting the local oproxy CA.
- Docker Compose docker compose up --build The included Compose file uses host networking, persists /app/certs and /app/storage, and sets OPROXY_BIND_HOST=0.0.0.0.
It is for developers testing browsers, CLIs, mobile apps, API clients, services, and test suites on their own machine or in a local Docker container.
Capture HTTP traffic and HTTPS traffic after trusting the local oproxy CA. View requests, responses, headers, bodies, status, timing, tags, notes, and selected inspector data. Replay captured requests and open them in Compose. Build manual requests with headers, query params, auth, raw bodies, variables, collections, and cURL export. Export captures as HAR or generated cURL, Fetch, and Python snippets. Modify traffic with rule sets, map-remote, map-local, access rules, throttling, breakpoints, mock responses, DNS overrides, capture filters, Lua scripts, and upstream proxy chaining. Use the authenticated Assistant to inspect state and prepare confirmed proxy changes through an OpenAI-compatible chat model. Run from source or Docker with persistent volumes for CA material and local state. Demo Short demo video
Docker docker run --rm \ --name oproxy \ -p 127.0.0.1:8080:8080 \ -p 127.0.0.1:1080:1080 \ -e OPROXY_BIND_HOST=0.0.0.0 \ -e OPROXY_MITM_ENABLED=true \ -v oproxy-certs:/app/certs \ -v oproxy-storage:/app/storage \ ghcr.io/sauravrao637/oproxy:latest Open http://127.0.0.1:8080.