IntenseWebs/boringproxy
3
0
Fork 0
mirror of https://github.com/boringproxy/boringproxy.git synced 2025-02-25 18:55:29 -06:00
Code Issues Packages Projects Releases Wiki Activity
Simple tunneling reverse proxy with a fast web UI and auto HTTPS. Designed for self-hosters.
47 Commits 31 Branches 14 Tags 682 KiB
Go 88.2%
Shell 10.6%
Dockerfile 1.2%
2c4b97c0e2
Go to file
Anders Pitman 2c4b97c0e2 Switch from TLS to HTTP proxying 
Allows a few things:

* Can terminate HTTP/2 without the upstream needing to implement
  it
* Allows modification of headers in both directions
* Allows logging at the proxy
2020-10-05 18:12:31 -06:00
webui Implement add/delete tunnels from UI 2020-09-29 23:10:06 -06:00
api.go Get username and home dir from system 2020-10-03 20:40:14 -06:00
auth.go Run go fmt 2020-10-02 17:09:14 -06:00
boring_proxy_admin.go Move admin page stuff into separate file 2020-10-05 16:13:01 -06:00
boringproxy.go Switch from TLS to HTTP proxying 2020-10-05 18:12:31 -06:00
client.go Get username and home dir from system 2020-10-03 20:40:14 -06:00
go.mod Start implementing custom client 2020-09-30 23:49:03 -06:00
go.sum Start implementing custom client 2020-09-30 23:49:03 -06:00
main.go Switch from TLS to HTTP proxying 2020-10-05 18:12:31 -06:00
README.md Remove SirTunnel stuff from readme 2020-09-29 15:53:10 -06:00
todo.md Start implementing custom client 2020-09-30 23:49:03 -06:00
tunnel_manager.go Get username and home dir from system 2020-10-03 20:40:14 -06:00
utils.go Run go fmt 2020-09-29 20:12:54 -06:00

README.md

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.