[
https://issues.apache.org/jira/browse/HTTPCLIENT-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18009329#comment-18009329
]
Arturo Bernal commented on HTTPCLIENT-2381:
-------------------------------------------
[~jonenst]
when you have a chance could you give the latest patch a spin? The proxy-lookup
has been moved entirely into {{{}SystemDefaultRoutePlanner{}}}: if the active
{{ProxySelector}} says “direct”, the planner now consults the usual environment
variables—{{{}HTTP_PROXY{}}}, {{{}HTTPS_PROXY{}}}, and {{{}NO_PROXY{}}}—and
builds the route from them. Nothing touches JVM system properties, so the
traditional {{useSystemProperties()}} path still works as before while an app
that relies only on env-vars should now connect through its corporate proxy out
of the box.
Let us know whether this matches what you were hoping for or if anything is
still missing.
> Allow environment proxy settings by default or strongly document this decision
> ------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-2381
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2381
> Project: HttpComponents HttpClient
> Issue Type: Wish
> Reporter: Jon Harper
> Priority: Minor
> Labels: volunteers-wanted
> Fix For: Stuck
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Hi,
> projects keep getting burned by the fact that is it impossible to set runtime
> environment variables to use http proxies. My personal latest frustration is
> with central-publishing-maven-plugin which is unusable in many companies
> where using a corporate proxy is mandatory (no direct internet access). This
> has happened times and times again, for example.
> https://github.com/spring-cloud/spring-cloud-vault/issues/75
> https://github.com/spring-projects/spring-boot/issues/35815
> It seems like every time this happen, people then just add the required code
> to be able to set an environment variable or a system property, after the
> initial pain of beeing blocked by this problem.
> Should this project be changed so that by default without code you can use
> system properties to configure the proxy ? That is have systemProperties=true
> everywhere and replace useSystemProperties() by disableSystemProperties().
> Using the same system properties as the jdk clients is the simplest, but if
> needed it would still provide benefit if it were entirely new system
> properties (so no backwards compatibilty as these properties would never have
> been set), at least people would be to use proxies without changing some code
> or worse changing some third party library.
> An alternative would be to add a prominent note in the docs to warn that
> unless specific code is added, using a proxy is impossible and makes the
> client unusable in many corporate contexts. Maybe also document why this
> design decision was made, what are the advantages of doing this so that users
> at least understand what they gain in exchange for their suffering.
> Thanks in advance,
> Jon
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
