Repository navigation
--proxy flag and proxy: config #40
Description
Why
Only HTTP_PROXY/HTTPS_PROXY/NO_PROXY are honoured, through http.ProxyFromEnvironment (internal/runner/runner.go:787-792). Corporate networks, Burp/mitmproxy debugging and per-project proxies all want an explicit setting that beats the environment, and a way to switch it off for one run.
What
--proxy <url>(http, https, socks5) beats the environment;--no-proxyignores both for one run.apic.yamlproxy: http://proxy.internal:3128andnoProxy: [localhost, .internal].Proxy-Authorizationfrom a userinfo in the URL is masked in output likeAuthorization(internal/runner/redact.goalready lists it).apic curlmaps to--proxy;describeshows the proxy in effect;env --jsonreportsproxy.
Where
internal/runner/runner.go, internal/project/project.go, internal/cli/root.go, internal/curlexport/curl.go.
Docs
docs/cli.md (global flags, config), docs/faq.md.
Tests
An httptest proxy that records CONNECT/absolute-URI requests; precedence flag > config > env; --no-proxy.
Activity
runner: --proxy flag and proxy: config (#40)
dataGriff commentedon Sep 21, 2026
Shipped in #106 (merged as
8351e8b):--proxy(http, https, socks5 or a bare host:port) and--no-proxyon every command includingapic test,proxy:andnoProxy:inapic.yaml, the environment variables read by request scheme with a malformed one refused rather than bypassed, and the proxy in effect reported with its userinfo masked bydescribe,run -v,run --json,env --jsonandapic curl.Generated by Claude Code