Vladimir Dubrovin

I will check if it's hard to implement name resolution for src address.

It's absolutely different, because in target name is taken from the request, e.g. if client does `CONNECT example.com HTTP/1.0` it matches `example.com` in destination ACL. If client does `CONNECT 93.184.216.34...

Config is reloaded only on signal or `monitor` event. Cache timeout is checked on name resolution. It means on every request (because request is the only event you actually have)...

How multiple IPs are expected to be used?

Do you mean `authcache` with `limit`?

How do you mean to use AF_UNIX, for listening socket?

Can you check if setting `parentretry 1` prior to starting socks workarounds the issue?

By default, 3proxy does not count traffic. It should not be hard to show something like current bandwidth usage for configured bandlimin/bandlimout/bandlimall counters, but this option is not currently implemented...

No, 3proxy requires explicit service to be allocated to port. It's possible and relatively easy to make an auto-detection, but can you explain your usecase somehow, because, at first look,...

I have added support for auto socks/http proxy selection with https://github.com/3proxy/3proxy/commit/fb56b7d307a7bce1f2109c73864bad7c71716f3b example auto -p1234 -e1.2.3.4