Repository navigation
Netty client: support SOCKS proxies #1573
Description
Problem
The Netty client connector only supports HTTP proxies (absolute-form forwarding and CONNECT tunnels). Some environments only provide a SOCKS proxy, for example SSH dynamic port forwarding (ssh -D) or certain corporate setups.
Proposed feature
- Add a
proxyTypeconnector parameter (HTTPby default,SOCKS5, maybeSOCKS4), and fall back to thesocksProxyHost/socksProxyPortsystem properties. - For SOCKS, add Netty's
Socks5ProxyHandler(optionally with username/password) at the head of the pipeline for both HTTP and HTTPS. Requests then use origin-form request lines (no absolute-form forwarding), and the proxy resolves the host names. - Netty's
netty-handler-proxyis already a dependency, so this needs no new library. - Add tests with a minimal SOCKS5 test proxy.
Activity
feat: support SOCKS5 proxies in the HTTP client
feat: support SOCKS5 proxies in the HTTP client
feat: support SOCKS5 proxies in the HTTP client
feat: support SOCKS5 proxies in the HTTP client
jlouvel commentedon Nov 5, 2026
Fixed by #1579: SOCKS5 proxies via the
socksProxyHost/socksProxyPort/socksProxyUsername/socksProxyPasswordparameters, falling back to thesocksProxyHost,socksProxyPort,java.net.socks.usernameandjava.net.socks.passwordsystem properties, rather than aproxyTypeparameter. Netty'sSocks5ProxyHandlerheads the pipeline for HTTP and HTTPS, andSocksProxyTestCaseuses a test SOCKS5 proxy.🤖 Generated with Claude Code