A Reverse Proxy with Pingora
A Reverse Proxy with Pingora
I've been playing with Pingora to create a reverse proxy that connects backend HTTP or HTTPs service to a single HTTPs frontend (similar to what is generally done with Nginx) serving distinct SSL certificates (using SNI and the host header) for each backend service. In this example, if you connect to https://127.0.0.1:4430 : * with an SNI and Host header of somedomain.com, you will be served an SSL certificate to somedomain.com and a proxied connection to http://127.0.0.1:4000 . * with an SNI and Host header of one.one.one.one, you will be served an SSL certificate to one.one.one.one and a proxied connection to https://one.one.one.one . Note: Pingora is a network services crate that Cloudflare recently opensourced, see https://news.ycombinator.com/item?id=39535969 https://news.ycombinator.com/item?id=39551115
Share cardActual performance
Launch Intel predictions
Analyze your own launch →Incorrect prediction on native model
Similar products
Skipr – StreamingKit Reverse Proxy
An experimental AntiBot, AntiCrawl reverse proxy for the web
Go's built-in reverse proxy
Traefik – a modern reverse proxy
Privytar, a privacy and caching reverse proxy for Gravatar
DeLorean – Super Performant IPv4->IPv6 Reverse Proxy in Golang
Lightweight SSL/TLS Reverse Proxy with Autogen Certs (LetsEncrypt)
Finch – a fingerprint-aware TLS reverse proxy
A reverse web proxy for developers
Reverse Proxy for HTTP and STDIO