You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I'm using latest beta release of fucksocks in JUnit test and starting/stopping the server for each test. I'm configuring the proxy using Java system properties, however this prevents the socks proxy from working, since it attempts to connect to itself when making connection to destination server (Socks5Handler.doConnect(..)).
I have been able to workaround this by providing my own implementation of Socks5Handler which turns off proxy usage in doConnect:
socket = new Socket(Proxy.NO_PROXY);
socket.connect(new InetSocketAddress(commandMessage.getInetAddress(), commandMessage.getPort()));
I saw that in latest code there is an option to specify a socks proxy when making connection to destination server, but it does not look like it is possible to turn off proxy usage, do you think that adding such support makes sense?
By the way, are there any plans to release a new sockslib version anytime soon.
Thanks,
Detelin
The text was updated successfully, but these errors were encountered:
Hi,
I'm using latest beta release of fucksocks in JUnit test and starting/stopping the server for each test. I'm configuring the proxy using Java system properties, however this prevents the socks proxy from working, since it attempts to connect to itself when making connection to destination server (Socks5Handler.doConnect(..)).
I have been able to workaround this by providing my own implementation of Socks5Handler which turns off proxy usage in doConnect:
I saw that in latest code there is an option to specify a socks proxy when making connection to destination server, but it does not look like it is possible to turn off proxy usage, do you think that adding such support makes sense?
By the way, are there any plans to release a new sockslib version anytime soon.
Thanks,
Detelin
The text was updated successfully, but these errors were encountered: