On Fri, Feb 15, 2013 at 2:31 PM, Adrian C. <[email protected]> wrote: > On Fri, 15 Feb 2013, Baptiste wrote: > >> 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. > > Hi I know, it's a missunderstanding, it was just an example of > errorfiles. We do have an errofile 408 as well (and every other status > supported by haproxy). > > > Will haproxy send the errorfile 408 with this response to an incomplete > or empty request? > >> [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>" > > I can't reconcile the number of 408 responses in error logs (excluding > BADREQ) and those in analytics leading me to suspect these responses > also generate a ping.
haproxy will use the 408 errorfile if the client doesn't sent a request. This can cause a lot of pain for some browsers, so we ended up with the following in our config files: errorfile 408 /dev/null This causes the least amount of grief with all the speculative conncetions the browsers perform - a closed connection with no data at all seems to be the only action on a speculative conncetion that will not cause display issues. - Finn Arne
