Comment by runjake 1 month ago Presumably this would be port-based fractional and 443/tcp would cost a premium. 2 comments runjake Reply almosthere 1 month ago I was thinking it was more of a "more than 50%" ownership controls the routing tables. Love the chaos. RiverCrochet 1 month ago It's already possible to "split" a frontend HTTP server on a given IP and port to arbitrary backend IPs and ports via the Host header and reverse proxies.
almosthere 1 month ago I was thinking it was more of a "more than 50%" ownership controls the routing tables. Love the chaos.
RiverCrochet 1 month ago It's already possible to "split" a frontend HTTP server on a given IP and port to arbitrary backend IPs and ports via the Host header and reverse proxies.
I was thinking it was more of a "more than 50%" ownership controls the routing tables. Love the chaos.
It's already possible to "split" a frontend HTTP server on a given IP and port to arbitrary backend IPs and ports via the Host header and reverse proxies.