microproxy alternatives and similar software solutions
Based on the "Proxy" category.
Alternatively, view microproxy alternatives based on common mentions on social networks and blogs.
8.2 8.5 microproxy VS imgproxyFast and secure standalone server for resizing and converting remote images
7.7 7.8 L3 microproxy VS Tinyproxytinyproxy - a light-weight HTTP/HTTPS proxy daemon for POSIX operating systems
1.7 0.0 microproxy VS PoundThe Pound program is a reverse proxy, load balancer and HTTPS front-end for Web server(s).
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of microproxy or a related project?
microproxy is a lightweight non-caching HTTP/HTTPS proxy server.
- Single executable with no external dependencies.
- Single simple configuration file in TOML format.
- Basic and Digest access authentication methods.
- IP-based black and white access lists.
- Ability to log all requests.
- Ability to tweak X-Forwarded-For header.
- Ability to specify IP address for outgoing connections.
- Ability to forward requests to upstream proxy.
- Reasonable memory usage.
This project is written in the Go programming language and to build it you need to install Go compiler and set some enviroment variables. Here is instructions on how to do it. After you've done it, run the following command in your shell:
$ go get github.com/thekvs/microproxy
and this will build the binary in
go build -mod=vendor for local build.
Configuration file options
microproxy uses TOML format for configuration file. Below is a list of supported configuration options.
listen="ip:port"-- ip address and port where to listen for incoming proxy request. Default:
access_log="path"-- path to a file where to write requested through proxy urls.
activity_log="path"-- path to a file where to write debug and auxiliary information.
allowed_connect_ports=[port1, port2, ...]-- list of allowed port to CONNECT to. Default:
auth_file="path"-- path to a file with users' passwords. If you use
digestauth. scheme this file has to be in the format used by Apache's htdigest utility, for
basicscheme it has to be in the format used by Apache's htpasswd utility with -p option, i.e. created as
$ htpasswd -c -p auth.txt username.
auth_type="type"-- authentication scheme type. Available options are:
"basic"-- use Basic authentication scheme.
"digest"-- use Digest authentication scheme.
auth_realm="realmstring"-- realm name which is to be reported to the client for the proxy authentication scheme.
forwarded_for_header="action"-- specifies how to handle
X-Forwarded-ForHTTP protocol header. Available options are:
X-Forwarded-Forheader with client's IP address, this is a default choice.
"off"-- do nothing, i.e. leave headear as is.
X-Forwarded-Forheader, this turns on stealth mode.
"truncate"-- delete all old
X-Forwarded-Forheaders and insert a new one with client's IP address.
via_header="action"-- specifies how to handle
ViaHTTP protocol header. Available options are:
Viaheader, this is a default choice.
"off"-- do nothing with
via_proxy_name="name"-- this value will be used as the host name in the
Viaheader, by default the server's host name will be used.
allowed_networks=["net1", ...]-- list of whitelisted networks in CIDR format.
disallowed_networks=["net1", ...]-- list of blacklisted networks in CIDR format.
bind_ip="ip"-- specify which IP will be used for outgoing connections.
add_headers=[["header1", value1"], ["header2", "value2"]...]-- adds specified headers to outgoing HTTP requests, this option will not work for HTTPS connections.
forward_proxy_url="http://user:[email protected]:port"-- specify proxy to forward requests to. Uses basic auth type for the forward proxy.
$ ./microproxy --config microproxy.toml
To enable debug mode, add
-v switch. To only test configuration file correctness add
$ ./microproxy --config microproxy.toml -t
USR1 signal microproxy reopens access and activity log files.
All source code included in this distribution is covered by the MIT License found in the LICENSE file.
*Note that all licence references and agreements mentioned in the microproxy README section above are relevant to that project's source code only.