On Sun, Oct 14, 2012 at 07:46:10PM -0400, Vivek Malik wrote: > I am not sure of how mikrokit could be having problems with > http-server-close. http-server-close only affects the haproxy <-> backend > connection, so it hidden from any front end.
Maybe the server responds differently, breaking the client. It could be nice to also try "option http-pretend-keep-alive" in the backend, it basically does not tell the server it will close. > Having said that, I can think of one way to do http-server-close for > specific conditions. It might not be the best method, but here it is. > > option http-server-close can be specified in backend. So, you can have a > normal backend with http-server-close enabled and a mikrotik backend with > http-server-close disabled. You can then use acl to choose the backend > depending on http headers. Yes this is a clean method :-) However it's better to figure what is causing the issue, even if this means that we should develop a workaround. We've already noticed that some clients do not strictly comply with the websocket spec, causing some interoperability issues. Once we can identify most of the bugs, we can try to be even more transparent. Willy
