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. b) if I do not use http-server-close, then users behind Mikrotik routers have problem, because Mikrotik decides to reuse the same http connection for the same IP address even when a different hostname is used. The only thing HAProxy could do here is to read headers on each data exchange and if it detects hostname change which would trigger different ACL then HAProxy would switch connection to other backend. I don't know how hard would be to implement this, but I assume it messes with core functionality. Regards, -- Milan Babuskov http://www.guacosoft.com
