On Mon, May 26, 2014 at 05:52:15PM +0200, Arnall wrote: > Le 26/05/2014 16:13, Willy Tarreau a écrit : > >Hi Arnall, > > > >On Mon, May 26, 2014 at 11:56:52AM +0200, Arnall wrote: > >>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 > >> > >><html><body><h1>408 Request Time-out</h1> > >>Your browser didn't send a complete request in time. > >></body></html> > >> > >>Timing : Blocking 2ms / Receiving : 1ms > >Where are you measuring this ? I suspect on the browser, right ? In > >this case it confirms the malfunction of the preconnect. You should > >take a network capture which will be usable as a reliable basis for > >debugging. I'm pretty sure that what you'll see in fact is the following > >sequence : > > > > browser haproxy > > ------- connect ----------> > > ... long pause ... > > <-------- 408 + FIN ------- > > ... long pause ... > > ------- send request -----> > > <-------- RST ------------- > > > >And you see the error in the browser immediately. The issue is then > >caused by the browser not respecting this specific rule : > > > > > Yes it was measured on the browser (Chrome network monitor) > I 've made a network capture for you.(in attachment)
Thank you. If you looked at the connection from port 62691, it's exactly the sequence I described above. So that clearly explains what Chrome is the only one affected! Best regards, Willy
