You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
http.proxyHost and http.proxyPort system properties are supported for hitting an http proxy, but https.proxyHost and https.proxyPort are not supported.
Current Behavior
https.proxyHost and https.proxyPort are not supported.
Possible Solution
Update ProxySystemSetting to have new enum values for https.proxyHost, https.proxyPort, and https.nonProxyHosts. Not sure if it makes sense to duplicate proxyUser and proxyPassword enums.
Update ProxyConfiguration to resolve host/port by checking for https proxy properties first, and if not set then check for http proxy properties, else no proxy. Update resolveScheme to set the scheme to 'http' or 'https' depending on which system properties are set (if any).
Context
I have an https proxy in one deployment environment, and no proxy in another environment.
Your Environment
AWS Java SDK version used: 2.5.44
JDK version used: 1.8.0_192
Operating System and version: Amazon Linux 4.14.72-73.55.amzn2.x86_64 (from uname)
The text was updated successfully, but these errors were encountered:
Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Expected Behavior
http.proxyHost and http.proxyPort system properties are supported for hitting an http proxy, but https.proxyHost and https.proxyPort are not supported.
Current Behavior
https.proxyHost and https.proxyPort are not supported.
Possible Solution
Update ProxySystemSetting to have new enum values for https.proxyHost, https.proxyPort, and https.nonProxyHosts. Not sure if it makes sense to duplicate proxyUser and proxyPassword enums.
Update ProxyConfiguration to resolve host/port by checking for https proxy properties first, and if not set then check for http proxy properties, else no proxy. Update resolveScheme to set the scheme to 'http' or 'https' depending on which system properties are set (if any).
Context
I have an https proxy in one deployment environment, and no proxy in another environment.
Your Environment
The text was updated successfully, but these errors were encountered: