-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[BUG] Outdated proxy's IP address #19497
Comments
After digging into the library, I believe the root cause is the fact that the proxy's host is resolved per initialization instead of per HTTP requests. According to Java doc, |
Thank you for filing this issue @willtn. I'll investigate better handling for validating the socket address per request rather than initialization. For a little more clarification on the issue, the proxy has a DNS name such as |
@alzimmermsft thank you for resolving this issue. When can we expect the releases of |
Hi @willtn, a release containing this fix will be shipped before the end of the week (2021/04/02), I'll update this issue once shipped. |
Hello @alzimmermsft , may I get an update on this please? Thanks. |
Thanks for the reminder @willtn, the fix for this shipped in the latest releases of Azure Core Changelog |
Describe the bug
A clear and concise description of what the bug is.
Our service use
com.azure.security.keyvault.keys.cryptography.CryptographyClient
to send requests to Azure Key Vault through our proxy, configured via JAVA_OPTS. Whenever we change the IP address of our proxy, our service becomes unable to connect to Azure key vault via a proxy.Exception or Stack Trace
To Reproduce
-Dhttp.proxyHost=proxy.domain.name -Dhttp.proxyPort=1000 -Djava.net.useSystemProxies=true
CryptographyClient.sign
. This will succeed.proxy.domain.name
in the DNS server.CryptographyClient.sign
again. This will fail.Code Snippet
Expected behavior
The CryptographyClient should connect to the key vault properly through the configured proxy.
Setup (please complete the following information):
Information Checklist
The text was updated successfully, but these errors were encountered: