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.
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. Regards, Vivek On Sun, Oct 14, 2012 at 4:05 PM, Milan Babuskov <[email protected]>wrote: > On Fri, Oct 12, 2012 at 4:51 PM, Vivek Malik <[email protected]> > wrote: > > Yes, option http-server-close would make haproxy run acls for every > request. > > It will also enable keep-alive between client (or proxy) and haproxy. > > Thanks, this fixed to problem for Mikrotik users, but now I have > problems with Safari users who cannot establish websockets or > xhr-polling connections anymore :( > > So, I reverted to old config and have a new question. Is it possible > to activate http-server-close option only for Mikrotik users? I read > the docs, but appears I can only access http headers withing acls for > frontend selection? > > I would like to achieve something like: > > option http-server-close WHEN http headers CONTAIN Mikrotik > > Thanks, > > -- > Milan Babuskov > http://www.guacosoft.com >
