What does this mean for existing application stacks? Will they break because they try to use some default proxy?
What exactly does this mean for existing call sites? Ty, Gary On Mon, Nov 24, 2025, 08:23 Jon Harper <[email protected]> wrote: > Hi, > in > https://issues.apache.org/jira/projects/HTTPCLIENT/issues/HTTPCLIENT-2381 > I was suggested to "Let’s have the original reporter kick off a > [DISCUSS] on dev@" > > In summary, I think the current API ( HttpClients.createDefault() ) > invites developers to write code that can't work for users in filtered > corporate networks with mandatory http proxies to access external. > Said developers test their code in unrestricted network and release > their software or libraries. Later a user tries to use the software or > library and is just in a dead end. > > What do you think of flipping this around, make the simple code that > most developers actually write work with proxies by default, and have > developers go the extra mile to prevent their users from activating > proxies if that's the requirement ? > > There are more details and discussions in the jira issue: > - should this runtime proxy activation come from java system > properties (-DproxyHost and friends) > - should this runtime proxy activation come from environment > variables ($http_proxy and friends) > - is it always safe to read this runtime configuration "This could > literally get [the process] killed" > > Cheers, > Jon > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
