On 25/09/2019 11:56, Daniel Fuchs wrote:
..
This is a problematic area, I think Daniel Fuchs looked into it
recently to see what should be changed.
When we where in the process of standardizing the HTTP client I did some
investigation to see if we could make the HTTP client more user friendly
for Docker applications. Namely I wanted whatever was defined in the
http_proxy env variables to be used by default, if no system property
was defined to override them. That's when I discovered that the
launcher on mac was explicitly setting system properties as a means
to enable the default system proxy - so there was no way to distinguish
whether those had been set by the user or not, and whether the env
variables should take precedence or not. I stopped my investigation
there.
Yeah, what we want is for the ( standard? ) environment variables,
http_proxy, https_proxy, and ftp_proxy, to be recognized and used by the
networking implementation, by default. Daniel's previous investigation
has shown us that doing so is possible, but a larger effort than we
initially thought.
As Volker pointed out, the ( not enabled by default ) support for system
proxies was greatly improved in JDK 9, see 8170868 [1]. This was a
really nice contribution, which allows integration with the system
configured proxies on more platforms. Especially the update to the newer
GNOME version, so that system proxies work on relatively recent versions
of Ubuntu.
It's a sad state of affairs that we still don't support system proxies
out-of-the-box by default, but maybe supporting the above three
environment variables, by default, is a more attractive route at this
point in time.
-Chris.
[1] https://bugs.openjdk.java.net/browse/JDK-8170868
