On Fri, Nov 15, 2013 at 10:58:46AM -0700, Shaun Kruger wrote: > It is of course only after sending a help request that you realize your > mistake. A careful reevaluation of the packet capture indicated a detail I > misread the first time. The client opens a connection, does nothing with it > for 5 seconds, then sends a FIN. HAproxy then sends a 400 (quite > appropriately) with its own FIN flag set followed by a tcp reset. > > Now that I see that the client was initiating the disconnect it is irrelevant > to the problem I'm resolving that HA sent a 400 in response. The 6s timeout > http-request was the right answer for me and I can now consider my issue > resolved.
You can add "option dontlognull" if you want to get rid of these ones. It will result in not logging connections from which nothing was received. Regards, Willy
