goflyway v2 - a local port forwarder built on HTTP
master is the active develop branch and containing v2 code, for the stable v1 release (though it was once called v2.0), please refer to v1.0 branch.
goflyway v2 is a special tool to forward local ports to a remote server securly, just like
goflyway uses pure HTTP POST requests to relay TCP connections. There is no CONNECT involved nor needed because goflyway is designed mainly for those people who are behind a CONNECT-less HTTP proxy or want to accelerate connections through static CDNs.
However pure HTTP requesting is definitely a waste of bandwidth if you already have a better network environment, so use
-w to turn on WebSocket relay, or
-K to turn on KCP relay if possible.
Server: ./goflyway :80 Client: ./goflyway -L 1080::1080 server:80 -p password
server:80 using WebSocket
Server: ./goflyway :80 Client: ./goflyway -w -L 1080:server2:1080 server:80 -p password
Server: ./goflyway :80 Client: ./goflyway -D 1080 server:80 -p password
HTTP reverse proxy or static file server on the same port:
./goflyway :80 -P http://127.0.0.1:8080 ./goflyway :80 -P /var/www/html
In HTTP mode when server received some data it can't just send them to the client directly because HTTP is not bi-directional, instead the server must wait until the client requests them, which means these data will be stored in memory for some time.
You can use
-W bytes to limit the maximum bytes a server can buffer (for each connection), by default it is 1048576 (1M). If the buffer reaches the limit, the following bytes will be blocked until the buffer has free space for them.