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
However, this is cumbersome. Also. this configuration is provider specific, so adding another provider would make it worse.
Instead we should support the defacto standard *NIX user experience:
export http_proxy="proxy.acme.com:80"export https_proxy="proxy.acme.com:80"export no_proxy="localhost,127.0.0.1,*.acme.com"# every integrated outbound call is configured
java -jar myapp.jar
It could be done with JAVA_TOOL_OPTIONS, but that makes one more variable to change when switch on and off proxy.
Supporting the standard environment variables simplifies the user experience.
We should provide a generic mechanism in a common module to be used by any code that makes outbound calls (E.g. GoogleTokenProvider).
We could abstract io.helidon.webclient.Proxy to decouple it from WebClient and add the environment variable support.
The text was updated successfully, but these errors were encountered:
Environment Details
Problem Description
Add general support for the standard
http[s]_proxy
andno_proxy
environment variables:WebClient
E.g. Using
google-login
security provider, one has to do this:Yes, this can be overridden with environment variables like this:
However, this is cumbersome. Also. this configuration is provider specific, so adding another provider would make it worse.
Instead we should support the defacto standard *NIX user experience:
It could be done with
JAVA_TOOL_OPTIONS
, but that makes one more variable to change when switch on and off proxy.Supporting the standard environment variables simplifies the user experience.
We should provide a generic mechanism in a common module to be used by any code that makes outbound calls (E.g.
GoogleTokenProvider
).We could abstract
io.helidon.webclient.Proxy
to decouple it from WebClient and add the environment variable support.The text was updated successfully, but these errors were encountered: