rschmitt commented on PR #773: URL: https://github.com/apache/httpcomponents-client/pull/773#issuecomment-3801183185
> Speaking of the amazon sdk, they are the only java software I know that read the venerable curl environment variable env.http_proxy, env.https_proxy, and maybe they read user/password from them and run the code to register it to the jdk? This is interesting, because the AWS Java SDK v2 actually supports several HTTP backends: Apache 4, Apache 5, the AWS Common Runtime, Netty, and HttpsURLConnection (the JDK client). It has an abstraction layer for HTTP configuration that can read proxy configuration from both system properties and environment variables and thread them into each particular client. > So to me it really comes down to whether you want to challenge the jdk and java status quo on proxy basic auth. What I've realized from this discussion is that anything we do here will be best-effort. It's purely a question of what actually-existing users are trying to do and how far we can go to accommodate them. I'm not opposed in principle to supporting the Gradle system properties, the Curl environment variables, etc. But I suspect there's a reason why the JDK doesn't allow basic proxy auth to be configured in this way. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
