You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Netty client: honor https.proxyHost / https.proxyPort system properties for HTTPS requests #1570
NettyClientHelper.getProxyHost() / getProxyPort() fall back only to the http.proxyHost / http.proxyPort system properties, for both HTTP and HTTPS requests. The JDK convention (see Networking Properties) uses https.proxyHost / https.proxyPort for HTTPS. Users with only the https.* properties set get no proxy, and users with only the http.* properties set send HTTPS through a proxy they may not have meant for it.
Proposed fix
Choose the system properties by scheme: https.proxyHost / https.proxyPort (default 443 per the JDK, or keep 3128) for HTTPS, http.* for HTTP.
Keep the proxyHost / proxyPort connector parameters for both schemes, and possibly add httpsProxyHost / httpsProxyPort parameters.
Make the pool and target computation (forwardProxy in create(), acquire()) use the proxy for the request's scheme.
Fixed by #1575: HTTPS requests use the https.proxyHost / https.proxyPort system properties, HTTP requests the http.* ones; the proxyHost / proxyPort parameters still apply to both. No separate httpsProxyHost parameter was added. #1577 also honors nonProxyHosts.
Activity
fix: use the https.proxyHost and https.proxyPort properties for HTTPS
fix: use the https.proxyHost and https.proxyPort properties for HTTPS
fix: use the https.proxyHost and https.proxyPort properties for HTTPS
fix: use the https.proxyHost and https.proxyPort properties for HTTPS
jlouvel commentedon Nov 5, 2026
Fixed by #1575: HTTPS requests use the
https.proxyHost/https.proxyPortsystem properties, HTTP requests thehttp.*ones; theproxyHost/proxyPortparameters still apply to both. No separatehttpsProxyHostparameter was added. #1577 also honorsnonProxyHosts.🤖 Generated with Claude Code