2014-05-26 12:05 GMT+02:00 Olivier <[email protected]>:

> 2014-05-26 11:56 GMT+02:00 Arnall <[email protected]>:
> > Hi Willy,
> >
> > same problem here with Chrome version 35.0.1916.114 m and :
> > HA-Proxy version 1.4.22 2012/08/09 (Debian 6) Kernel 3.8.13-OVH
> > HA-Proxy version 1.5-dev24-8860dcd 2014/04/26 (Debian GNU/Linux 7.5)
> Kernel
> > 3.10.13-OVH
>
> Hello,
>
> Just to say that I experience the same issue. Customers reported 408
> errors with Chrome, and this error was delivered instantly. No bug
> with another browser. There were no error a few weeks ago with exactly
> the same config / same HAProxy binary, that's why I'm pretty sure
> Chrome changed its behaviour for pre-connect.
>
> My timeout parameters are as follow :
>
>     timeout connect 5s
>     timeout http-keep-alive 5s
>     timeout http-request 10s
>
> HAProxy version is 1.5-dev18.
> I've increased the http-request timeout to 60 seconds and it seems to
> fix the issue, but it is not a good fix
>
>
> >> Some people suggest closing without ever emitting the 408. You can do
> that
> >> this way :
> >>
> >>      errorfile 408 /dev/null
>
> I'll try this today.
>
> I continu to see 408 in logs but no more in browser with this errorfile
set to /dev/null... for the moment it fix the problem for me.



>  Olivier
>
>

Reply via email to