Hi Cory,
On Thu, Mar 24, 2011 at 01:10:49PM -0400, Cory Forsyth wrote:
> I'm not sure if this is a bug in HAProxy, or if upgrading HAProxy to 1.4 has
> uncovered a bug in my application.
>
> I am developing a web app that uses long polling. I'm proxying its requests
> through haproxy. I've noticed that when reload the page in the browser
> (which presumably severs the connection that the javascript is holding open
> to the server through haproxy), I get an http status 502 error logged by
> haproxy. It looks something like this:
>
> Mar 23 12:43:45 localhost haproxy-1.5v4[5969]:
> 96.246.63.146:61899[23/Mar/2011:12:43:25.276] http_proxy
> backend1/backendserver1 6/0/0/-1/20014
> 502 204 - - SH-- 0/0/0/0/0 0/0
> {proxy.myserver|65|http://proxy.myserver|Mozilla/5.0
> (Macinto} {|} "POST / HTTP/1.1"
>
> This happens in Haproxy version 1.5-dev3 and 1.5-dev4, but it does not
> happen in haproxy version 1.4.13. Is there some additional investigation I
> can do to determine if it's a bug in 1.5x or just something that my web app
> shouldn't have been doing anyway that is now (correctly) being logged as an
> error by 1.5x?
What I understand from the logs is that the server suddenly closed
after exactly 20 seconds. Maybe this is not what happened, but we
have to find why it was logged like this. Could you please post your
config ?
Thanks,
Willy
