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).