-
Couldn't load subscription status.
- Fork 33
Add SOCKS proxy support to the API #699
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
Conversation
Generate changelog in
|
63318ba to
21a51d0
Compare
| .hostAndPort("localhost:1234") | ||
| .build()) | ||
| .isInstanceOf(IllegalArgumentException.class) | ||
| .hasMessage("credentials only valid for HTTP proxies"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, can't socks proxies have credentials? Or is this a matter of just restricting the API for now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seemingly they can but it seems a little scary with passwords sent in cleartext: https://www.rfc-editor.org/rfc/rfc1929
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is very difficult to test, so I opted to limit the scope to the minimal feature set we need.
|
👍 |
|
Released 2.22.0 |
==COMMIT_MSG==
Add SOCKS proxy support to the API
==COMMIT_MSG==
Possible downsides?
more proxies, socks is very hard to unit test