feat(proxy): route outbound through upstream SOCKS5/HTTP CONNECT proxy#182
Merged
Conversation
Honor the standard HTTP_PROXY/HTTPS_PROXY/NO_PROXY env vars and an optional proxy.upstream_proxy config block on the forward data path and in the broker's credential-refresh client. Env vars override config per-field. Covers the HTTP/HTTPS forward path (incl. CONNECT in mitm mode) and broker token refresh. Raw TCP tunnels (sni-only passthrough, WebSocket) still dial directly. Closes #166
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
iron-proxy now routes its own outbound connections through an upstream SOCKS5/HTTP CONNECT proxy, honoring the standard
HTTP_PROXY/HTTPS_PROXY/NO_PROXYenv vars plus an optionalproxy.upstream_proxyconfig block. Env vars override the matching config field per-field, so deployments that already export the standard vars work without editing YAML.This covers the HTTP/HTTPS forward data path (including CONNECT in mitm mode) and the broker's credential-refresh client. Raw TCP tunnels (sni-only passthrough, WebSocket) still dial directly and are out of scope here.
Note: when an upstream proxy is in use,
upstream_deny_cidrsis enforced against the proxy's address rather than the final target, since the proxy resolves and connects on iron-proxy's behalf. This tradeoff is documented in the example config.Closes #166