devRant is the ultimate backend to test my proxy server with since it's random responses. When your proxy server can handle devRant scenario's, it's robust. Making a proxy server that is actually robust and don't let it flaws itself with slow connections / servers is quite a challenge. Depends also what you're writing it with. In python was way simpler than in C. In Python some things magically just worked. If you think that python sockets are native, you're wrong kiddo, they did al sort of shits under the hood. Had to do a whole rewrite of my original proxy server to allow pipelining. Pipelining is req>req>req>resp>resp>resp instead of the traditional req>resp>req>resp>req>resp. It's keep-alive on steroids. Most server don't support it out of self preservation but I just want to. Caddy is a huge pipeliner. What most servers do is, they close the connection the moment the second request is sent / marking the second request invalid. Clients support that behavior and will do the second call under the hood.

My new proxy server has exactly the same dashboard as the previous one but the many statistics that it has have zero performance impact. It persists every second a quick snapshot to database, every 60 seconds a big one. The statistics are persistent for when the server reboots.

What an adventure.