Hi Adrian, You reported a 408 error, which means the client did not send a complete request before the "option timeout http-request" (which seems to be setup to 10s in your case).
No link with your 503 errorfile. Baptiste On Fri, Feb 15, 2013 at 2:34 AM, Adrian C. <[email protected]> wrote: > Hello we use custom error pages for our site, a friendly maintanance > notice is less scary. > > ... > errorfile 503 /etc/haproxy/errors/503.http > > To get the most out of an unwanted state, and a better handle on the > webapp, we used a small javascript ping in each separate page going to > an analytics service so we can generate stats. > > The most common error response logged so far is a 408 and I'm trying to > understand it better. Most of all I'm conflicted on empty or incomplete > requests which could be a result of browser pipelining or other speed > tricks modern browsers use. > > If haproxy sends the errofile with this response I'm not sure if the > client browser would interpret it generating a ping to analytics. > > [15/Feb/2013:19:10:50.975] foobar foobar/<NOSRV> -1/-1/-1/-1/10000 408 212 - > - cR-- 49/49/0/0/0 0/0 "<BADREQ>" > > Thanks. > > -- > Adrian C. (anrxc) | anrxc..sysphere.org | PGP ID: D20A0618 > PGP FP: 02A5 628A D8EE 2A93 996E 929F D5CB 31B7 D20A 0618 >
