Best I can tell this is specifically due to having http-server-close enabled in my defaults section. Commenting that out seems to fix this issue. I assume the connection gets killed just after the upgrade is completed and then the client is left hanging.
-Joe -- Name: Joseph A. Williams Email: williams....@gmail.com On Saturday, August 4, 2012 at 10:45 AM, joseph williams wrote: > > On Aug 3, 2012, at 9:33 PM, Willy Tarreau <w...@1wt.eu (mailto:w...@1wt.eu)> > wrote: > > > Hi Joe, > > > > On Fri, Aug 03, 2012 at 03:54:35PM -0700, Joe Williams wrote: > > > List, > > > > > > I am attempting to setup stud, haproxy (1.5-dev7) and a backend web > > > sockets > > > server using proxy protocol to communicate between stud and haproxy. It > > > seems > > > like my requests are making it to the backend server but the client never > > > receives anything. > > > > > > This is the only thing I ever see in the logs: > > > > > > Aug 3 22:14:36 10.178.2.72 haproxy[13312]: IP:49494 > > > [03/Aug/2012:22:14:36.608] http-proxy websocket/host 94/0/0/2/96 101 148 > > > - - ---- 12/12/0/0/0 0/0 "GET /streaming/handshake HTTP/1.1" > > > > 148 bytes for a handshake response seem very short (though possible). > > I see nothing abnormal in your config. Could you take a capture of the > > response handshake ? > > > > When you say that not passing via haproxy works, does this mean that > > you're forwarding from stud to the server directly ? > > > > > I did some playing around and was able to make a couple different working > configurations using haproxy by itself. At this point I think I have narrowed > it down to stud and/or using proxy protocol. I'll do some more testing and > reply back with results soon. > > -Joe
