Glen De Cauwsemaecker
Glen De Cauwsemaecker
We could always turn these into a specific kind of error (new variant for the `SocksError`) such that it can still be seen as an error for those who want...
Demoting things to warn I am not a fan of personally. Sometimes I might see it a bit too black and white, but I do prefer to either have something...
Seems these errors are avoided if I switch around the streams in my bi-directional call
Never mind. Sometimes I get the read/written bytes count, but most of the times not. I believe it is however a shortcoming in Tokio's functionality of bidirectional copy. That or...
For now I forked for my project the 2 util files from Tokio's copy bidirectional code. With minor modifications I can make it work by catching those 2 error kinds...
There was a request to also support this feature in socks4 client, but don't think it has a config. So going to leave that request without further action.
Found how I can do it myself, here is how I did it: ```rust async fn handle_socket(socket: Socks5Socket, _request_timeout: u64) where T: AsyncRead + AsyncWrite + Unpin, { // upgrade...
This code was only put in a function at the end of my struggles, so I was still logging everywhere instead of handling these errors more neatly as a single...
My example won't work. This is related to #21 I believe. Within the upgrade_to_socks5 logic we already request and process it. As such the first actual usage of the proxy...
New attempt is made to have this shown in an example: https://github.com/dizda/fast-socks5/pull/24