I'm wondering how this works for real world situations in which the HTTP server must slowly trickle responses back to the client. In the past I've seen major speed ups by using a store and forward proxy.
Since this server always prints hello world it would stand to reason that Ngnix should be caching the result.
Since this server always prints hello world it would stand to reason that Ngnix should be caching the result.