-
Notifications
You must be signed in to change notification settings - Fork 864
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proxy configurations for different SDK http clients doesn't have feature parity. #2321
Comments
Thank you for reaching out @kra3, this is a reasonable feature request. |
@debora-ito Since it's tagged with hacktoberfest, do you mind I jump in and contribute to it? |
@erin889 go for it! And thank you for your interest! |
Resolved via #2771. |
|
…0a9201a4c Pull request: release <- staging/c5afe014-be8a-4aa0-94e0-c730a9201a4c
Netty and Amazon CRT Http client's proxy configurations are not aware of system proxy settings. Such as those passed in via JDK properties (eg:
http.proxyHost
,http.proxyPort
). However Apache proxy configuration is aware of those properties.Also, there are other issues to make
ProxyConfigurations
to feature parity with older aws-sdk-java's Proxy configuration (eg: #1793)The text was updated successfully, but these errors were encountered: