On Sat, Jun 03, 2017 at 00:19:19 +0000, Willy Tarreau wrote: > On Fri, Jun 02, 2017 at 06:17:38PM +0000, Bernard McCormack wrote: > > 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?
> no because there is no fundamental difference between the two. However I > suspect that when you force nginx to 1.0 and it doesn't know the response, > it only uses close mode which triggers what looks like an haproxy bug. But > when you enable 1.1, it uses chunked encoding and there's no such issue > anymore. > > I'll have a look. > > Cheers, > Willy We are seeing this as well on 1.7.5. The problem seems to be intermittent--it doesn't happen very often when I hit a system with almost no load, but is happening very frequently on a high load system. I don't believe it is causing any issues other than the log message.
