Update: Someone pointed out to me that the requests to haproxy are forced to HTTP/1.0, but the response is HTTP/1.1 w/ chunked encoding. So question is now, if haproxy will accept the chunked encoding to keep alive the frontend connection when there isn't a content-length header, and if it will still do that if the client request from the frontend is http/1.0 and the server response is http/1.1.
On Thu, Sep 17, 2015 at 4:43 PM, CJ Ess <[email protected]> wrote: > We've noticed that our front-end connections to haproxy are closing after > talking to a backend running php-fpm. The php-fpm backend is not sending a > content-length header, but is using chunked encoding which encodes lengths > of the chunks and should be enough to keep the connection alive for another > request. How does HAProxy handle this situation? > > > >
