zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Phillips (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2250) Support client connections using a SOCKS proxy
Date Tue, 07 Feb 2017 16:20:41 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856269#comment-15856269

David Phillips commented on ZOOKEEPER-2250:

[~takeseem], that is correct, due to the nature of NIO, applications must add SOCKS support
themselves. The protocol itself is quite simple: after connecting, the client sends a few
bytes to the server indicating where to connect, then the server replies with a few bytes
indicating success or failure. See https://en.wikipedia.org/wiki/SOCKS

> Support client connections using a SOCKS proxy
> ----------------------------------------------
>                 Key: ZOOKEEPER-2250
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2250
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: java client
>            Reporter: David Phillips
> Connecting to ZooKeeper via a SOCKS proxy is often useful for debugging systems over
an SSH dynamic port forward.
> It is possible to do this today with some hacking by setting "zookeeper.clientCnxnSocket",
but that is difficult because ClientCnxnSocket is package-private and is quite low-level.

This message was sent by Atlassian JIRA

View raw message