Re: disable backend through socket

2013-12-22 Thread Jonathan Matthews
On 22 Dec 2013 20:32, Patrick Hemmer hapr...@stormcloud9.net wrote: That disables a server. I want to disable a backend. No, you want to disable all the servers in a backend. I'm not sure there's a shortcut that's better than just doing them one by one. Others may be able to advise about

Re: disable backend through socket

2013-12-22 Thread Patrick Hemmer
No. As I said, I want to disable the backend. http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#4.2-disabled -Patrick *From: *Jonathan Matthews cont...@jpluscplusm.com *Sent: * 2013-12-22 16:23:18 E *To:

SSL and keep-alive

2013-12-22 Thread Jean-Baptiste Quenot
Hi there, Thanks for the great SSL support in 1.5, keep up the good work! My exact version is 1.5~dev19. I'm using SSL a lot for corporate use, and notice some performance issues with an ajax-intensive application. I checked in Chrome's developer console that keep alive headers are properly

Re: disable backend through socket

2013-12-22 Thread Willy Tarreau
On Sun, Dec 22, 2013 at 05:05:16PM -0500, Patrick Hemmer wrote: No. As I said, I want to disable the backend. http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#4.2-disabled That doesn't really work for backends since they don't decide to get traffic. At least if a config accepts to

It seems HTTP header string exact match failed

2013-12-22 Thread Delta Yeh
In my test of 1.5dev21, I found the following acl failed: acl my_host req.hdr(host) -m str www.mytest.com use_backend www if my_host and result in an 503 error(because there is no default backend). I tried : 1. my_host req.hdr(host) -m beg www.mytest.com 2. my_host req.hdr(host) -m