Anders Pitman bab13efdbf Strip connection headers
When going from HTTP/1.1 to HTTP/2
2021-02-22 23:04:43 -07:00
2021-01-23 11:16:50 -07:00
2021-02-07 07:57:03 -05:00
2020-11-04 09:28:10 -07:00
2021-02-15 12:24:12 -07:00
2021-02-16 18:37:31 -07:00
2021-02-16 18:37:31 -07:00
2020-12-07 21:41:45 -07:00
2021-02-17 10:56:29 -07:00
2020-12-07 21:50:33 -07:00
2020-12-07 21:41:45 -07:00
2020-10-31 09:52:14 -06:00
2021-02-22 23:04:43 -07:00
2020-11-04 07:55:43 -07:00
2020-10-21 09:50:12 -06:00
2020-10-22 10:08:20 -06:00
2020-10-26 11:11:14 -06:00
2020-11-25 18:42:40 -07:00
2020-12-07 21:41:45 -07:00
2020-11-24 19:21:59 -07:00
2020-12-07 21:50:33 -07:00
2021-02-22 23:04:43 -07:00

What is it?

If you have a webserver running on one computer (say your development laptop), and you want to expose it securely (ie HTTPS) via a public URL, boringproxy allows you to easily do that.

NOTE: For information on downloading and running boringproxy, it's best to start on the website, boringproxy.io. The information in this README is just for building from source.

Building

git clone https://github.com/boringproxy/boringproxy
cd boringproxy

If you don't already have golang installed:

./install_go.sh
source $HOME/.bashrc
go build

To embed the web UI into the executable:

go get github.com/GeertJohan/go.rice/rice
rice embed-go
go build

Running

Server

boringproxy server -admin-domain bpdemo.brng.pro

Client

boringproxy client -server bpdemo.brng.pro -token fKFIjefKDFLEFijKDFJKELJF -client-name demo-client -user demo-user
Description
Simple tunneling reverse proxy with a fast web UI and auto HTTPS. Designed for self-hosters.
Readme 640 KiB
Languages
Go 88.2%
Shell 10.6%
Dockerfile 1.2%