Thanks Willy, found the issue with curl -I and it was messed up header like you said. Thanx!
/* Joe Stein, 973-944-0094 http://www.medialets.com Twitter: @allthingshadoop */ On Jul 21, 2010, at 3:56 PM, Willy Tarreau <[email protected]> wrote: > Hi Joe, > > On Wed, Jul 21, 2010 at 11:38:21AM -0400, Joe Stein wrote: >> Hi, we have a new server that we are trying to fit behind our existing >> HAProxy implementation. For some reason it is giving us a 502 error (the >> server is a tomcat6 server with servlet) and we are trying to hunt down the >> cause. Any help to what this might be or how we can better interrogate >> haproxy to why it is giving this header (e.g. some header missing or such). >> We are running 1.3.23 in production but have the same issue also on the >> 1.4.8 release too. > > If you have enabled the stats socket in the global section, you can > dump the last fault request and response of each backend using "socat" : > > printf "show errors\n" | socat stdio unix-connect:/var/run/haproxy.stat > > You will get the rejected response and the exact location of the first > faulty character. Most likely you're having a forbidden character in a > header name, I've seen that once. > > Regards, > Willy >
