-
Notifications
You must be signed in to change notification settings - Fork 566
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add automatic support in WebClient for JVM http.proxyHost
and related properties
#7218
Comments
"Java Networking and Proxies" has some general conventions described, which most Java developers be habituated to expect OOTB. Currently, devs have to fall in line by wiring these standard variables into WebClient configuration via ${http.proxyHost} tokens. So why not make this behavior default, and let devs customize/override it via configuration source precedence patterns? |
We should support environment variables too (E.g. |
We should already be supporting this through |
Tomas, I think the request is that the |
Created #7274 for Helidon 4.x |
It was merged already |
Environment Details
Problem Description
The standard Java system properties
http.proxyHost
,http.proxyPort
, andhttp.nonProxyHosts
(and thehttps
counterparts) govern proxy behavior generally, but not in Helidon's web client.The request is for Helidon to "intelligently" use those settings automatically, if they exist, in preparing web clients. Presumably, if the developer explicitly sets proxy behavior (via code or configuration) for a web client then, for that client, Helidon would ignore the JVM system property settings.
The text was updated successfully, but these errors were encountered: