Skip to content
An encrypted HTTP server
Go Python
Branch: master
Clone or download
Latest commit 59cbff5 Jan 9, 2020
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.misc
cmd Fix string Jan 9, 2020
fd Clean dir && add traffic stat Jul 26, 2019
toh Fix #170 #161 Oct 28, 2019
v
.gitignore Update flags Sep 3, 2019
LICENSE Shoco lib, better compression, license Aug 25, 2017
client.go
io.go Change v functions Sep 2, 2019
readme.md Clean dir Sep 2, 2019
server.go Clean dir Sep 2, 2019
ssvpn_interop.go Clean dir && add traffic stat Jul 26, 2019
ssvpn_windows.go Fix #170 #161 Oct 28, 2019
util.go Clean dir Sep 2, 2019

readme.md

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 ssh -L.

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.

Usage

Forward localhost:1080 to server:1080 through server:80

    Server: ./goflyway :80
    Client: ./goflyway -L 1080::1080 server:80 -p password

Forward localhost:1080 to server2:1080 through server:80 using WebSocket

    Server: ./goflyway :80
    Client: ./goflyway -w -L 1080:server2:1080 server:80 -p password

Dynamically forward localhost:1080 to server:80

    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

Write Buffer

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.

You can’t perform that action at this time.