Skip to content
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

Incorrect "http.nonProxyHosts" property name #1081

Closed
grassehh opened this issue Apr 29, 2024 · 1 comment · Fixed by #1083
Closed

Incorrect "http.nonProxyHosts" property name #1081

grassehh opened this issue Apr 29, 2024 · 1 comment · Fixed by #1083
Assignees
Labels
bug This issue is a bug.

Comments

@grassehh
Copy link

grassehh commented Apr 29, 2024

Describe the bug

Configuring the http.nonProxyHosts system property is not working.

Expected Behavior

As explained in the documentation the property http.nonProxyHosts should be used to determine non proxy hosts.

Current Behavior

Setting http.nonProxyHosts system property has no effect because http.noProxyHosts is used instead.

Steps to Reproduce

Simply configure a client using environment while having defined http.nonProxyHosts system property. For example:

S3Client.fromEnvironment {}

Then if you make a request to a host defined in the system property, the http client will still try to go through the proxy.

Possible Solution

Replace http.noProxyHosts with http.nonProxyHosts at this line : (

)

Context

We were trying to configure the proxy of an S3 client only by using the Java System properties.

Your Environment

  • Smithy Kotlin version used: 1.0.11
  • Platform (JVM/JS/Native): JVM (Java 21)
  • Operating System and version: Debian 12
@grassehh grassehh added the bug This issue is a bug. label Apr 29, 2024
@lauzadis
Copy link
Contributor

lauzadis commented Apr 29, 2024

Thanks for the bug report! You're right, we should be checking http.nonProxyHosts instead of http.noProxyHosts as the Java specification states.

To maintain backwards compatibility, we'll still need to support both system properties, but we will prioritize the new value http.nonProxyHosts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants