Hi Willy,
I'm following up on a post I made a few weeks ago. I'm still having a
problem with certain HAproxy backends randomly (about once ever two
days) refusing to work with their assigned backend server. The only way
to bring them back to live is to restart HAproxy. At the same time,
On 2014-02-19 22:14, pechspilz wrote:
Could it be just a configuration error eventually? Am I not supposed
to use the hdr keyword this way in the backend?
Looks like I should have a look at the persist option :-)
Hi,
I'm seeing a very sporadic issue (every few days) in a TCP mode proxy
and I'm at loss what could be causing it.
After some time, haproxy is unable to establish a connection with the
backend server. 2 is the configured connect timeout. I can't see any
exhausted resources in haproxy
So I have this backend web application which sends a custom header:
X-Bonanza;: abcdefg
The semicolon is a programming error an obviously doesn't belong there.
While checking HTTP-conformance, haproxy discards the request with PH-- 502.
I was trying to rspdel the X-Bonanza header but it looks
Thanks a bunch for your help, Willy.
On Tue, Jul 16, 2013 at 9:20 PM, Willy Tarreau w...@1wt.eu wrote:
Hi,
On Tue, Jul 16, 2013 at 09:05:10PM +0200, pechspilz wrote:
So I have this backend web application which sends a custom header:
X-Bonanza;: abcdefg
The semicolon is a programming
Hi there,
Is the port part of a HTTP header hostname? It looks like, because
depending on the frontend port I have to do something like this:
if { hdr(host) -i haproxy-rulez.net:8181 }
...if the frontend is bound to :8181
I'd prefer to just write
if { hdr(host) -i haproxy-rulez.net }
...no
Hi,
Since upgrading from dev17 to dev18 I'm getting a segfault:
(gdb) run -f /etc/haproxy/haproxy.conf -p /var/run/haproxy.pid -db
Starting program: /usr/local/bin/haproxy -f /etc/haproxy/haproxy.conf -p
/var/run/haproxy.pid -db
Program received signal SIGSEGV, Segmentation fault.
7 matches
Mail list logo
