Hi Erik, On Thu, Mar 18, 2010 at 02:29:46PM +0100, Erik Gulliksson wrote: > Unfortunately I the "show errors" returned empty, so I guess it was > something else. The good news is that I gave haproxy 1.4.2 a try today > and the 502/PR error with PUT/TE:chunked requests have now vanished. > So thanks for solving this. I'm not sure which one of the bugs I was > hitting but it does not really matter since it now seems to be fixed.
OK so very likely it's the same problem I fixed yesterday using Bernhard's captures. > So now when I got a working haproxy 1.4, I continued to try out the > "option http-server-close" but I hit a problem with our stunnel > (patched with stunnel-4.22-xforwarded-for.diff) instances. It does not > support keep-alive, so only the first HTTP request in a > keepalive-session gets the X-Forwarded-For header added (insert Homer > "doh!" here :). When giving it some thought, I guess this is the > expected behaviour for what stunnel actually is supposed to do. yes indeed it's expected. Stunnel is not designed to manipulate application data, and the patch only adds the header to the first request of a connection. Maybe we should implement some XCLIENT-like protocol between stunnel and haproxy, to report address of the client of the TCP connection. > So, > for now I'll stick with "option httpclose" for a while longer... You may get better results with "option forceclose" now, as it will release the server connection earlier. Regards, Willy
