In case of SOCKS5 failures, do not explicitly log the server's response
authorFabian Keil <fk@fabiankeil.de>
Sat, 10 Mar 2012 11:06:09 +0000 (11:06 +0000)
committerFabian Keil <fk@fabiankeil.de>
Sat, 10 Mar 2012 11:06:09 +0000 (11:06 +0000)
commit430b87b899c9294875101eee7faca82880a111e1
tree36e205291b349ca02af3f829a218a97e6ef55615
parent386312854d05ad4001662efd29f6f044a18b542d
In case of SOCKS5 failures, do not explicitly log the server's response

It hasn't helped so far and the response can already
be logged by enabling "debug 32768" anyway.

This reverts v1.81 and the follow-up bug fix v1.84.
gateway.c