Hello Kevin, On 06/04/2014 05:05 PM, Willy Tarreau wrote: > On Wed, Jun 04, 2014 at 04:49:53PM +0200, Kevin Maziere wrote: >>> Anyway, from the various reports we get, it seems like sending an empty >>> 408 message is enough to workaround this abnormal Chrome behaviour. For >>> this you can proceed like this : >>> >>> errorfile 408 /dev/null >>> >>> After days of tests it appears that 408 error page are still appening, but >> less frequently. >> I don't know how but I can see them on my logs and on my browser. > > In the logs it's perfectly normal as haproxy reports what has been done, > but in the browser, it's really not possible since the error message was > replaced with the contents of /dev/null. What might happen is either that > some requests go to another haproxy or another server which still emits > the error, or that such errors were abusively cached by the client which > reports them on closed connection. > > Regards, > Willy > >
Can you post your latest configuration? Regards, -- Nenad Merdanovic | PGP: 0x423edcb2 | Web: http://nimzo.info Linkedin: http://www.linkedin.com/in/nenadmerdanovic
