[ ijbswa-Feature Requests-3603913 ] socks5 message / error passthrough

Feature Requests item #3603913, was opened at 2013-02-08 22:10
Message generated for change (Comment added) made by fabiankeil
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=361118&aid=3603913&group_id=11118

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: grarpamp (grarpamp)
>Assigned to: Fabian Keil (fabiankeil)
Summary: socks5 message / error passthrough

Initial Comment:
Privoxy 3.0.19 on FreeBSD 8.3 i386
 
With polipo I'd see helpful diagnostic messages from Tor's socks5 implementation
passed through polipo and eventually reaching wget's log file. Though I'm not sure
if it was the exact socks5 error code number, the text was still useful. Example...
 
1300 504 Connect to onion failed: SOCKS error: host unreachable.
    80 504 Connect to onion failed: SOCKS error: TTL expired.
    30 504 Connect to onion failed: SOCKS connection not allowed.
    15 504 Connect to onion failed: General SOCKS server failure.
    10 504 Connect to onion failed: SOCKS error: connection refused.
 
With Privoxy, I get vague 500 level messages that don't really tell me anything
about the far end. (I don't have relative counts for this example right now).
 
ERROR 500: Internal Privoxy Error.
ERROR 500: Internal Server Error.
ERROR 502: Server or forwarder response invalid.
ERROR 503: Service unavailable.
ERROR 504: Gateway Time-out.
Proxy tunneling failed: Internal Privoxy ErrorUnable to establish SSL connection.
 
So I'm hereby suggesting that...
1) more detailed messages be passed through wherever available from the far end.
2) these 'internal' errors receive more verbose or coded treatment as to what function
is kicking them out. (that's probably the bug-ish part of this feature-ish report).
 
Thx.


----------------------------------------------------------------------

>Comment By: Fabian Keil (fabiankeil)
Date: 2013-02-09 03:28

Message:
Adding the socks error description to the response line seems useful to me.
Thanks for the suggestion.

Note that Privoxy already provides the details as part of the response body
and properly logs them when configured to do so.

Internal Privoxy Errors usually aren't bugs but configuration problems and
I don't think discarding the problem description in the body and only
looking at the response line is a reasonable debugging strategy, even when
doing it from the "far end".

BTW, at least some of your example error messages don't actually come from
Privoxy and checking Privoxy's log would make their origin more obvious.
Unfortunately correlation socks errors to Tor circuits currently isn't
trivial.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=361118&aid=3603913&group_id=11118

------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb