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.
55 Commits 31 Branches 14 Tags 682 KiB
Go 88.2%
Shell 10.6%
Dockerfile 1.2%
274725b5c5
Go to file
Anders Pitman 274725b5c5 Add HTTP>HTTPS redirection 
Required switching to TLS for LetsEncrypt, so I could disable
the HTTP ACME handler. Pretty sure there's a way to keep them
both enabled but this is fine for now.
2020-10-07 10:44:37 -06:00
webui Implement add/delete tunnels from UI 2020-09-29 23:10:06 -06:00
api.go Add X-Forwarded-Host header to upstream requests 2020-10-07 09:18:04 -06:00
auth.go Move sessions and tunnels into database 2020-10-05 23:25:36 -06:00
boring_proxy_admin.go Reuse httpClient 2020-10-06 10:22:03 -06:00
boringproxy.go Add HTTP>HTTPS redirection 2020-10-07 10:44:37 -06:00
client.go Reuse httpClient 2020-10-06 10:22:03 -06:00
database.go Move sessions and tunnels into database 2020-10-05 23:25:36 -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 Move sessions and tunnels into database 2020-10-05 23:25:36 -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 Reuse httpClient 2020-10-06 10:22:03 -06:00
tunnel.sh Restrict file permissions before writing key 2020-10-07 09:04:01 -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.