hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HTTPCLIENT-1691) Wouldn't it be better if the Fluent Executor set useSystemProperties on its HttpClient?
Date Thu, 04 May 2017 09:45:04 GMT

     [ https://issues.apache.org/jira/browse/HTTPCLIENT-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Oleg Kalnichevski resolved HTTPCLIENT-1691.
-------------------------------------------
    Resolution: Fixed

Implemented in SVN trunk.

Oleg

> Wouldn't it be better if the Fluent Executor set useSystemProperties on its HttpClient?
> ---------------------------------------------------------------------------------------
>
>                 Key: HTTPCLIENT-1691
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1691
>             Project: HttpComponents HttpClient
>          Issue Type: Wish
>          Components: Fluent HC
>    Affects Versions: 4.5
>            Reporter: Andrew Garrett
>            Priority: Minor
>             Fix For: 5.0 Alpha2
>
>
> Is the fact that the Fluent Executor does not call useSystemProperties when building
its HttpClient a design decision? This is quite painful as it requires us to fork a library
we are using, which in turn uses the Fluent client, in order to get it to accept proxy settings
by manually adding the proxy. Every other library that our application uses respects http.proxyHost
and http.proxyPort, so this is pretty unfortunate. If not using the system properties was
not a design decision, can we change the Fluent Executor to use them?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message