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
A request sent by this client fails with 407 when the proxy requires preemptive authentication.
It works fine when the proxy does not.
Regression Issue
Select this option if this issue appears to be a regression.
Expected Behavior
A request passes the proxy.
Current Behavior
software.amazon.awssdk.services.sns.model.SnsException: null (Service: Sns, Status Code: 407, Request ID: null)
at software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handleErrorResponse(CombinedResponseHandler.java:125)
at software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handleResponse(CombinedResponseHandler.java:82)
at software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handle(CombinedResponseHandler.java:60)
at software.amazon.awssdk.core.internal.http.CombinedResponseHandler.handle(CombinedResponseHandler.java:41)
at software.amazon.awssdk.core.internal.http.pipeline.stages.HandleResponseStage.execute(HandleResponseStage.java:50)
at software.amazon.awssdk.core.internal.http.pipeline.stages.HandleResponseStage.execute(HandleResponseStage.java:38)
Describe the bug
Proxy Authentification fails with Status 407 when Proxy requires preemptive authentication.
My code:
A request sent by this client fails with 407 when the proxy requires preemptive authentication.
It works fine when the proxy does not.
Regression Issue
Expected Behavior
A request passes the proxy.
Current Behavior
Reproduction Steps
Possible Solution
I found a possible reason in software.amazon.awssdk.http.apache.internal.utils.ApacheUtils.
The method
addPreemptiveAuthenticationProxy
contains:I added a challenge and now it works:
Additional Information/Context
No response
AWS Java SDK version used
2.30.17
JDK version used
openjdk version "21.0.4" 2024-07-16 LTS
Operating System and version
Linux rodeoarch 6.12.4-arch1-1
The text was updated successfully, but these errors were encountered: