Skip to content

Latest commit

 

History

History
118 lines (79 loc) · 4.25 KB

README.md

File metadata and controls

118 lines (79 loc) · 4.25 KB
Raw

mproxy

Build Status Appveyor Build status

中文使用帮助

mproxy is a multi mode http/https proxy.

  1. as a normal HTTP/HTTPS proxy

  2. as a SOCKS5 proxy to HTTP proxy converter

  3. as a shadowsocks HTTP client

3proxy can work as mode 1 and mode 2, but his threaded model cannot scale well.

When possible, use splice to speed up HTTP CONNECT socket relay under mode 1,2.

Based on a modified libevhtp library, the original version have some bugs when as HTTP client library.

Why HTTP proxy instead of SOCKSs proxy? Because some client only support HTTP proxy, for example IE9 only support SOCKS4/HTTP proxy, and some version control system like subversion mercurial only support HTTP proxy. Currently HTTPS proxy is only supported by a few clients, eg. Chrome, Firefox 31+, curl 7.52.0+.

Installation

Install required development components

libevent 2.0.12+ (except libevent 2.0.22 stable), OpenSSL 1.1.0+ or mbed TLS (optional)

Win32 require VC++ 2013/2015 or MinGW-w64 and MSYS .

Linux require cmake or scons.

Compile

Win32

  • MinGW

make -f Makefile.mingw

  • VC++ 2013/2015/2017 open the proxy.vcxproj directly, set your libevent and openssl directories then compile

Linux

  • CMake, enable all protocol

cmake . -DENABLE_HTTPS_PROXY:STRING=ON -DENABLE_SS:STRING=ON -DCMAKE_BUILD_TYPE=Release && make

  • CMake, disable shadowsocks protocol

cmake . -DENABLE_SS:STRING=OFF && make

Usage

Multi Mode HTTP proxy
Usage:
  mproxy [options]
Options:
  -l <local_port>       proxy listen port, default 8081
  -b <local_address>    local address to bind, default 0.0.0.0; IPv6 address 
                        must starts with "ipv6:"
  -p <server_port>      socks5/shadowsocks server port
  -s <server_address>   socks5/shadowsocks server address
  -m <encrypt_method>   encrypt method of remote shadowsocks server
  -k <password>         password of remote shadowsocks server
  --pac <pac_file>      pac file
  --dns <ip[:port]>     name server, default port 53
  --user <user[:group]> set user and group
  --pid-file <path>     pid file
  --ssl_certificate <fullchain.pem>   set ssl certificate
  --ssl_certificate_key <privkey.pem> set ssl private key
  -V                    show version number and quit
  -h                    show help
Supported encryption methods for shadowsocks:
  Stream Cipher:
    table, rc4, rc4-md5, aes-128-cfb, aes-192-cfb, aes-256-cfb, 
    bf-cfb, camellia-128-cfb, camellia-192-cfb, camellia-256-cfb, 
    cast5-cfb, des-cfb, idea-cfb, rc2-cfb, seed-cfb, aes-128-ofb, 
    aes-192-ofb, aes-256-ofb, aes-128-ctr, aes-192-ctr, aes-256-ctr, 
    aes-128-cfb8, aes-192-cfb8, aes-256-cfb8, aes-128-cfb1, 
    aes-192-cfb1, aes-256-cfb1
  AEAD Cipher:
    chacha20-ietf-poly1305, aes-128-gcm, aes-192-gcm, aes-256-gcm,
    aes-128-ocb, aes-192-ocb, aes-256-ocb

Examples

simple HTTP proxy, listen 127.0.0.1:8081

./mproxy -b 127.0.0.1 -l8081

or ./mproxy -b ipv4:127.0.0.1 -l8081

simple HTTP proxy, listen IPv6 [::1]:8081

./mproxy -b ipv6:::1 -l8081

HTTPS proxy, use certificate issued by Let's Encrypt, listen IPv6 [::1]:8081

./mproxy -b ipv6:::1 -l8081 --ssl_certificate /etc/letsencrypt/live/your.domain/fullchain.pem --ssl_certificate_key /etc/letsencrypt/live/your.domain/privkey.pem

convert local machine's SOCKS5 proxy at 127.0.0.1:1080 to HTTP proxy at 127.0.0.1:8087

./mproxy -b127.0.0.1 -l8087 -s 127.0.0.1 -p 1080

worked as shadowsocks client, shadowsocks server address 9.9.9.9:9999, encrypt method aes-256-cfb, password mysspassword

./mproxy -b127.0.0.1 -l8087 -s 9.9.9.9 -p 9999 -k mysspassword -m aes-256-cfb

worked as shadowsocks client, encrypt method rc4-md5, password mysspassword, and serve local PAC file

./mproxy -b127.0.0.1 -l8087 -s 9.9.9.9 -p 9999 -k mysspassword -m rc4-md5 --pac /path/to/pac/file

TODO

DNS cache

LRU with multi thread