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

fix when proxy tunneling failed (IOException is hidden) JDK-8173 #901

Merged
merged 2 commits into from Jun 26, 2019

Conversation

PearSlice
Copy link
Contributor

@PearSlice PearSlice commented Jun 11, 2019

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

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@marci4
Copy link
Collaborator

marci4 commented Jun 11, 2019

Hello @PearSlice,

could you please open a normal issue as well where you can describe the problem a bit more into detail (and maybe some steps to repeat etc etc) so other people understand the context.

Thank you!

Best regards,
Marcel

@PearSlice
Copy link
Contributor Author

Hi,

I created the issue #905 and updated the pull request accordingly.

Best Regards,

Pascal

@marci4 marci4 requested a review from PhilipRoman June 12, 2019 20:16
@marci4
Copy link
Collaborator

marci4 commented Jun 12, 2019

@PhilipRoman if you have the time, could you maybe do a review please? Thanks

@PhilipRoman PhilipRoman requested review from PhilipRoman and removed request for PhilipRoman June 13, 2019 14:28
@marci4 marci4 added the Client label Jun 14, 2019
@marci4 marci4 added this to the Release 1.4.1 milestone Jun 14, 2019
@marci4 marci4 added the Bug label Jun 14, 2019
@marci4
Copy link
Collaborator

marci4 commented Jun 26, 2019

@PhilipRoman you're happy with the PR? (I'm sorry to bother you again)

@PhilipRoman
Copy link
Collaborator

Yes, seems like a harmless fix. I couldn't test it though.

@marci4 marci4 changed the title fix when proxy tunneling failed (IOException is hidden) JDK-8173620 fix when proxy tunneling failed (IOException is hidden) JDK-8173… Jun 26, 2019
@marci4 marci4 merged commit f580296 into TooTallNate:master Jun 26, 2019
@marci4 marci4 changed the title fix when proxy tunneling failed (IOException is hidden) JDK-8173… fix when proxy tunneling failed (IOException is hidden) JDK-8173 Mar 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

IOException wrapped in InternalError not handled properly
3 participants