Proxy through connection pool raised an error

[ozjongwon]

(def +conn-pool+
  (http/connection-pool {:connection-options {;;:http-versions [:http2 :http1]
                                              :proxy-options {:host "127.0.0.1"
                                                              :port 9050
                                                              :protocol :socks5
                                                              :connection-timeout (* 5 1000)}}
                         ;;:total-connections 1024
                         }))

@(http/get "https://check.torproject.org" {:pool +conn-pool+})

=>
1. Unhandled io.netty.handler.proxy.ProxyConnectException
   socks5, none, /127.0.0.1:9050 => null, unexpected authMethod: UNACCEPTED(255)

   Socks5ProxyHandler.java:  140  io.netty.handler.proxy.Socks5ProxyHandler/handleResponse
         ProxyHandler.java:  260  io.netty.handler.proxy.ProxyHandler/channelRead
AbstractChannelHandlerContext.java:  442  io.netty.channel.AbstractChannelHandlerContext/invokeChannelRead
AbstractChannelHandlerContext.java:  420  io.netty.channel.AbstractChannelHandlerContext/invokeChannelRead
AbstractChannelHandlerContext.java:  412  io.netty.channel.AbstractChannelHandlerContext/fireChannelRead
 ByteToMessageDecoder.java:  346  io.netty.handler.codec.ByteToMessageDecoder/fireChannelRead
 ByteToMessageDecoder.java:  333  io.netty.handler.codec.ByteToMessageDecoder/fireChannelRead
     ReplayingDecoder.java:  349  io.netty.handler.codec.ReplayingDecoder/callDecode
 ByteToMessageDecoder.java:  290  io.netty.handler.codec.ByteToMessageDecoder/channelRead
AbstractChannelHandlerContext.java:  444  io.netty.channel.AbstractChannelHandlerContext/invokeChannelRead
AbstractChannelHandlerContext.java:  420  io.netty.channel.AbstractChannelHandlerContext/invokeChannelRead

(Equivalent?) curl command works.

curl --verbose --proxy socks5://127.0.0.1:9050 https://check.torproject.org
Can anyone point why it happens and how to fix?

Thanks!

[arnaudgeiser]

While the root-cause remains unclear, this is where the error is pointing at on the Netty's code base [1].
This could be give you a pointer to start with.

[1] : https://github.com/netty/netty/blob/dc999c4b87d5023bfcf9ec73a8d7481e7bf5bdbf/handler-proxy/src/main/java/io/netty/handler/proxy/Socks5ProxyHandler.java#L138-L141

[arnaudgeiser]

And the response means the same authentification methods are not used between Netty and curl.
What are you receiving back as an HTTP response from the CURL command?

[1] : https://github.com/netty/netty/blob/4.1/codec-socks/src/main/java/io/netty/handler/codec/socksx/v5/Socks5AuthMethod.java#L30-L33

[ozjongwon]

There is no auth config in the proxy. So curl spat out the correct HTML response. I am not sure if the 'proxy' path of the connection pool is in working state or not. Also it seems not to support noop for DNS lookup for Socks5h requests(when I looked it, I didn't find one)

Thanks

[DerGuteMoritz]

@ozjongwon Could you try again with Aleph 0.8.3? That version includes a fix for the HTTP client's proxy support. While we've so far only tested this with HTTP proxies, it could just as well apply to SOCKS proxies (there was a pipeline handler ordering issue).