[
https://issues.apache.org/jira/browse/HTTPCLIENT-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17995788#comment-17995788
]
Oleg Kalnichevski commented on HTTPCLIENT-2381:
-----------------------------------------------
[~jonenst] Let me tell you a story
Long, long time ago, when the trees were tall, HttpClient was still in version
3, people used to be convinced they would be always deploying their
applications as cute bundles called EAR and all they applications would always
be running inside those massive and powerful application servers called WebFear
or WebTerror or some such. The applications servers were powerful and mighty
and did not quite like when little apps tried to read system properties they
were not supposed to see. This could literally get one killed (not as a person
but as an app process).
So, the decision had to made to not read any system properties. {_}Ever{_}.
Thou shalt not read system properties. To protect all those little cute apps.
If you do not want your wish to always be just a wish (I wish I was young again
and had scalp hair), do this: subscribe to the dev list, post a message there
and say the current policy no longer make any sense, see how people react and
if enough people say yay, provide a patch against master. This will grant your
wish. Otherwise I wish I was young again.
Oleg
> 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: Major
>
> 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: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
