Hi, most 502 errors in haproxy responses come from "bad" backend responses. Could you try adding a "Content-Length: 0" header to the backend response? I don't know if RFC requires it in a 204 response.
btw. the expires date in your setcookie looks a bit strange. 0059, 1959 or 2059? Karsten Am Mittwoch, 28. Oktober 2009 schrieben Sie: > bash-3.2$ curl --verbose "http://cm01.example.com:8000/c"; > * About to connect() to cm01.example.com port 8000 (#0) > * Trying 22.33.44.55... connected > * Connected to cm01.example.com (22.33.44.55) port 8000 (#0) > > > > GET /c HTTP/1.1 > > > User-Agent: curl/7.19.6 (i386-apple-darwin9.8.0) libcurl/7.19.6 > > OpenSSL/0.9.8k zlib/1.2.3 > > > > Host: cm01.example.com:8000 > > > Accept: */* > > < HTTP/1.1 204 No Content > < Date: Wed, 28 Oct 2009 11:56:44 GMT > < Server: Jetty/5.1.11RC0 (Linux/2.6.21.7-2.fc8xen amd64 java/1.6.0_16 > < Expires: Thu, 01 Jan 1970 00:00:00 GMT > < Set-Cookie: pid=08f0b764185;Path=/;Domain=.example.com;Expires=Thu, > 16-Oct-59 11:56:44 GMT > < Connection: close > < > * Closing connection #0 >
