On Mon, Oct 15, 2012 at 10:28:04AM +0200, Milan Babuskov wrote: > On Mon, Oct 15, 2012 at 7:47 AM, Willy Tarreau <[email protected]> wrote: > > However it's better to figure what is causing the issue, even if this > > means that we should develop a workaround. > > The issue is the following: > > a) if I use http-server-close then websocket connections are broken > for Safari users because Safari uses the old websocket spec. However, > I cannot switch to tcp mode because I have multiple node.js servers > running one the same machine, with users sharded accross (i.e. a > particular user needs to go to a specific server). I need http to be > able to do L7 routing to correct server.
Which "old spec" is it using ? There have been something like 76 different versions. Even many old versions were already HTTP-compatible. I think it was draft-75 which was totally broken. Willy
