Willy, Thanks for the response. I am getting nothing with "show errors" however "show stat" is giving showing me the eresp count as I would expect from the logs. Additionally the logs are showing "SD" on the 412 errors which seems odd considering the backend server shouldn't be having any connection issues. So I am still trying to nail down what the issue is, it seems that that either the http client lib or the backend server may be doing something funny.
By the way, is there any performance hit to leaving that socket open? Is there a list of commands somewhere in the docs? Thanks. -Joe On Thu, 20 Aug 2009 22:05:18 +0200 Willy Tarreau <[email protected]> wrote: > On Thu, Aug 20, 2009 at 10:14:39AM -0700, Joe Williams wrote: > > > > I seem to be seeing 412 error codes from my backend in my haproxy > > logs and from what I can tell haproxy is producing 502 errors when > > this happens. In my case the 412 is expected and I would like to > > pass it along to the client. Is there an option to do this? > > haproxy has no reason to block a 412 response. However, it is very > likely that a header in the response is invalid, making the response > itself invalid. > > You can check this by enabling "option accept-invalid-http-response" > and seeing if it doesn't do that anymore. If so, I suggest that you > fix your application for the invalid header, otherwise there will > always be one part of the net who will have trouble accessing your > site. > > In order to figure out what header is wrong, I suggest that you enable > the global stats socket and connect to it using "socat", then issue > the "show errors" command. It will report a capture of last invalid > request and response for each frontend/backend, with the exact > location of the first anomaly found. > > It is very helpful to web developers how encounter trouble pushing > their apps in production. > > Regards, > Willy > > -- Name: Joseph A. Williams Email: [email protected] Blog: http://www.joeandmotorboat.com/
