Additionally, when was "option accept-invalid-http-response" added to the configuration API. I am running 1.13.15.1 and the "-c" option tells me it doesn't know what it is.
Thanks again. -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/
