I have to interface with a seriously old software package that provides an http 1.0 server. Naturally, that server does not support keep-alive, and every connection from the client requires a new socket. I don't wish to pay socket setup for every single request, so I'd like to have a separate software which provides http 1.1, and reverse-proxies to the back-end legacy http 1.0 software.

I haven't found any simple configuration for this with popular webservers like apache or nginx. Maybe I'm missing the config or module.

Apache doesn't seem to be able to do this at all.

The two default workers have a fixed configuration and will be used if no other worker matches the request. They do not use HTTP Keep-Alive or connection pooling. The TCP connections to the origin server will instead be opened and closed for each request. https://publib.boulder.ibm.com/httpserv/manual24/mod/mod_proxy.html#workers

Nginx doesn't keep the client connection open when the upstream server finalizes the connection, which is the case in my scenario https://stackoverflow.com/questions/46771389/why-does-nginx-proxy-pass-close-my-connection


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.