Hi [Sorry for top-posting]
2014-05-23 16:08 GMT+02:00 Willy Tarreau <[email protected]>: > Hi Kevin, > > [guys, please could you stop top-posting, it's a total mess to try to > respond to this thread, I cannot easily take out the useless parts, > thanks]. > > On Fri, May 23, 2014 at 02:35:21PM +0200, Kevin Maziere wrote: > > 2014-05-23 14:34 GMT+02:00 Baptiste <[email protected]>: > > > > > Kevin, > > > > > > Do you (still) see 408 errors printed in the browser??? > > > > > > Baptiste > > > > > > On Fri, May 23, 2014 at 2:17 PM, Kevin Maziere < > [email protected]> > > > wrote: > > > > Hi > > > > > > > > I've just applied the first patch, here are the debug log : > > > > > > > > In the logs : > > > > 2014-05-23T12:03:20+00:00 images-access haproxy[13409]: > 127.0.0.1:56596 > > > > [23/May/2014:12:03:17.972] ipv4-yyy-443~ ipv4-yyy-443/<NOSRV> > > > > -1/-1/-1/-1/2041 408 212 - - cR-- 9/3/0/0/0 0/0 "<BADREQ>" > > Well, here I'm seeing a standard 408 after 2 seconds which should match > a timeout http-request of 2 seconds. Can you check if you don't have one ? > Also, this observation from the logs doesn't seem consistent with your > first > claim that the 408 is immediate, here it's only after 2 seconds. Or again > we > are facing this bogus preconnect feature of Chrome. People complain all the > time that not only it connects before you want to go to the site, but above > all it displays the error that it receives without checking that it got an > error prior to using the connection :-( > You can see the 408 displaying immediatly by browsing on http://shoppingadventure.fr with chrome. The probleme occured on haproxy 1.4 also, not only on 1.5dev. > > > > In the debug log, correspond lines: > > > > 2014-05-23T12:03:20+00:00 servername haproxy[13409]: Timeout > detected: > > > > fe=ipv4-yyy-443 s->flags=00000080 txn->flags=00000000 > req->flags=00c88000 > > > > msg->flags=00000000 now_ms=687261517 req->analyse_exp=687261515 (-2) > > At least that's good, it's the first request of the connection and nothing > except the regular request timeout occurred. > > There was an interesting thread here about the nasty behaviour of chrome : > > https://code.google.com/p/chromium/issues/detail?id=85229#c33 > > Thansk for this link. I'm testing a big value for timeout client so that chrome will expired before haproxy close the socket. > Some people suggest closing without ever emitting the 408. You can do that > this way : > > errorfile 408 /dev/null > > Note that this fantastic browser breaks HTTP by preventing any server from > using the well-defined HTTP status code indicating a timeout occurred. > > The problem happens recently, I used to browse with Chrome without seeing it before I do agree with you. > Kévin, I think the reason why you have the issue only on one OS is not > related > to the OS but to your browsing history on that system. The browser doesn't > pre-connect there and you don't have the trouble. > Yes it is. I flush my history and after few click I have the 408 error, and the error in immediat, Chrome is not loading and then showing 408 page. > Regards, > Willy > > Thanks Willy for the help.
