fix when proxy tunneling failed (IOException is hidden) JDK-8173 #901
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Handle IOException when proxy auth fails
Description
When using an authenticated proxy to connect to a Websocket and providing wrong credentials the error is hidden.
This fix allows to have a better view on the root exception.
Related Issue
Fixes #905
Motivation and Context
This allows to see exception
Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Auth Required"
instead of having
java.lang.InternalError: Should not reach here
masking it.How Has This Been Tested?
By providing wrong/no credentials to our squid proxy in prod env
By providing wrong/no credentials to a local cntlm proxy in dev env
Types of changes
Checklist: