-
Notifications
You must be signed in to change notification settings - Fork 120
Capability to forward traffic to a socks5 proxy #1242
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
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Comments
To support this, we'd need to let callers configure the HTTP Transport and the socket to use a socks5 proxy. Do-able, but requires investigation as Java doesn't support this as easily as Go. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Feature Description
In scenarios (e.g. transitive vpc problem) that require the java sql connector to forward traffic to a socks5 proxy, it would great if this capability could be added to the java sql connector. Similar to the way the sql auth proxy can forward traffic to a socsk5 proxy by setting the ALL_PROXY environment variable, ideally the java sql connector would behave in the same manner.
Sample code
No response
Alternatives Considered
The workaround is to install the sql auth proxy locally with the application, so the sql auth proxy could forward traffic to the socks5 proxy. This is not ideal because the. sql auth proxy would need to be installed, configured, and started on every developer's computer.
Additional Details
No response
The text was updated successfully, but these errors were encountered: