I’ve done some more testing. After changing the frontend ngnix to use ‘’’ proxy_http_version 1.1’’’ The errors stopped occurring. I wonder if it has to do with how haproxy handles http/1.0 request?
Our current configuration was Nginx (http/1.0)-> haproxy -> backend server Working configuration Nginx (http/1.1)-> haproxy -> backend server On 6/2/17, 5:01 AM, "Willy Tarreau" <[email protected]> wrote: On Fri, Jun 02, 2017 at 09:46:34AM +0200, Pavlos Parissis wrote: > In the network capture, I didn't see the HTTP response header Content-Length, which could confuse > haproxy and mark the connection as terminated from server side during data transfer as haproxy > didn't know the actual size of response. I am assuming here that, haproxy reads the value of > Content-Length and it will mark a request with SD if the server closes the connection, either by > sending a FIN/ACK or RST, before haproxy has received the amount of data announced in Content-Length. It *should not* do this (and didn't do it in the past) but it could be an explanation if we have a bug somewhere. This one should not be too hard to reproduce though. Willy
