Love this project! Any chance of updating the version of HAProxy?

When using Privoxy for HTTP and trying to add auth header, I am getting the following error:
Invalid header received from client

Newer Tor versions support HTTPTunnelPort , making Privoxy unneeded.
Can just pass --HTTPTunnelPort and connect HAProxy directly to Tor.

Network Problem

Hello there.
At first, i must appreciate the work you have done here, it is amazing.
Second, i just wanted to know, putting aside the HAproxy solution, is it possible to extend your scenario on windows machine as well? btw: the privoxy idea is really brilliant because it opens a layer of interception for the developer, nice work.
thanks in advance.

Is it possible to set a password for a proxy connect?

Is it possible to specify the exit node country?

I am unable to build latest, command:

docker build -t zeta0/alpine-tor:latest .

error:

ERROR: While executing gem ... (OptionParser::InvalidOption) invalid option: --no-ri Did you mean? no-force The command '/bin/sh -c apk --update add --virtual build-dependencies ruby-bundler ruby-dev && apk add ruby-nokogiri --update-cache --repository http://dl-4.alpi nelinux.org/alpine/v3.3/main/ && gem install --no-ri --no-rdoc socksify && apk del build-dependencies && rm -rf /var/cache/apk/*' returned a non-zero code: 1

When Privoxy enabled sometimes this error appears as a response:

500 Internal Privoxy Error

Privoxy encountered an error while processing your request:

Could not load template file no-server-data or one of its included components.

Please contact your proxy administrator.

If you are the proxy administrator, please put the required file(s)in the (confdir)/templates directory. The location of the (confdir) directory is specified in the main Privoxy config file. (It's typically the Privoxy install directory, or /etc/privoxy/).

Steps to reproduce:

1. docker run -d -p 8118:8118 -p 2090:2090 -e tors=25 -e privoxy=1 zeta0/alpine-tor
2. Make a request with HTTP proxy
3. Get error

How about adding explicit ExitPolicy to tor start command? At present running this containers makes you a Tor exit node which is undesired by most. I suggest it should be configurable with default set to reject, i.e. --ExitPolicy "reject *:*" in command line.

The current docker container does not seem to work with TOR v3 Hidden Service URLs; e.g.: http://dlegal66uj5u2dvcbrev7vv6fjtwnd4moqu7j6jnd42rmbypv3coigyd.onion/.

cURL:

~ ❯❯❯ curl --socks5 localhost:32779 http://dlegal66uj5u2dvcbrev7vv6fjtwnd4moqu7j6jnd42rmbypv3coigyd.onion
curl: (6) Could not resolve host: dlegal66uj5u2dvcbrev7vv6fjtwnd4moqu7j6jnd42rmbypv3coigyd.onion

Possible fix: update the tor package from 0.3.0.8 to 0.3.4.9 using apk or alpine:latest?

/ # which tor
/usr/bin/tor
/ # tor --version
Tor version 0.3.0.8 (git-802d30d9b71a6d54).

If anyone has had luck with v3 Hidden Service URLs, please let me know.