mitmproxy-based HTTP capture & OpenAPI validation service
homeStart the Electron capture app first. It signs you in, assigns a stable per-user local port, and uploads your captures to S3 for the cloud UI and validation pipeline.
& "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" `
--user-data-dir="$env:LOCALAPPDATA\EdgeProxyProfile" `
--proxy-server="127.0.0.1:" `
--proxy-bypass-list="<-loopback>;*.youbora.com;youbora.com;*.npaw.com;*.lcdn.claro.net.co"
--user-data-dir points inside a OneDrive-synced folder (OneDrive locks/syncs profile files while Edge is trying to write to them). Check with echo $env:LOCALAPPDATA - if that path contains OneDrive, create a plain local folder instead, e.g. New-Item -ItemType Directory -Path "C:\EdgeProxyProfile" -Force, then use --user-data-dir="C:\EdgeProxyProfile" in the command above.
HTTP_PROXY=http://127.0.0.1: and HTTPS_PROXY=http://127.0.0.1:.
To capture HTTPS traffic the proxy needs to intercept TLS. Visit http://mitm.it with your proxy configured to download the CA certificate in any format (.pem, .cer, .p12, etc.).
http://mitm.it in your browser while the proxy is active. mitmproxy will serve platform-specific certificates (.pem for Linux/Docker, .cer for Windows, .p12 for Android/Fire TV builds, etc.).
https:// site — if the connection succeeds without a warning, the cert is trusted.networkSecurityConfig set to trust user CAs.