We're trying to filter out HTTP HEAD requests using haproxy,
to make the proxy behave like shoutcast servers, ref:
http://comments.gmane.org/gmane.comp.web.haproxy/2961
We're using haproxy-1.4.8-1.el6.x86_64 (EPEL) and have configured:
reqdeny ^HEAD
errorfile 403
We have 2 loadbalancers in failover configuration, using
mod_proxy_balancer for web and haproxy for pop/imap. I
want to move to using haproxy also for the web-part, but
am a bit uncertain how to most smoothly accomplish this.
The mod_proxy_balancer is balancing over 5 backend hosts,
using a
On Fri, Mar 27, 2009 at 08:41:53AM +0100, Willy Tarreau wrote:
Thanks for your work on this. I have no way to test that the specfiles
work, and I only update a few fields in them at each release. So it's
really a good thing that someone like you checks them and proposes
fixes.
Would you
e26b5d930781b78ed9aa7524498536007f89e720 Mon Sep 17 00:00:00 2001
From: Jan-Frode Myklebust janfr...@tanso.net
Date: Thu, 26 Mar 2009 12:54:53 +0100
Subject: [PATCH]- Update specfile to build for v2.6 kernel.
- Fix date in changelog.
- Stop using deprecated REGEX=pcre, and start using USE_PCRE=1
instead
Please also apply the attached patch to avoid lots of unneccassary
RPM dependencies.
-jf
From ce1abdcf48be27255647865130702b0305c8c63b Mon Sep 17 00:00:00 2001
From: Jan-Frode Myklebust janfr...@tanso.net
Date: Thu, 26 Mar 2009 13:56:43 +0100
Subject: [PATCH] The examples/check perl script
We're currently using apache mod_proxy_balancer and cookies
to make sessions sticky to backend hosts. Unfortunately
mod_proxy_balancer doesn't seem to have any way of draining
backend nodes. i.e. when we need to take one node out of
service, we'd want to schedule that a few days in advanced.
On 2009-03-26, Joseph Hardeman jharde...@colocube.com wrote:
Yes it can, there is an haproxy.conf file which contains the hosts that
you are proxying the traffic for. To remove a host, you would edit this
file, put a # in front of the server(s) you want taken off line and then
run the
On Thu, Mar 19, 2009 at 08:38:36AM +0100, Willy Tarreau wrote:
believe it or not, I've never experimented at all with selinux.
Yea, I wouldn't have guessed it, but you're doing a fine job developing
haproxy. I'm really impressed by it! So please keep your focus there :-)
However,
reading
On 2009-03-17, Joseph Hardeman jharde...@colocube.com wrote:
John is right, the way to do this is to use either heartbeat or
keepalive and fail over a VIP to a secondary machine in case the first
has issues. Make sure your haproxy files are identical and then test
the failover.
I would
On 2009-03-17, John Lauro john.la...@covenanteyes.com wrote:
You need to explain a little more, as I am not understating something.
Perhaps what you mean by VIP?
Virtual IP address. With heartbeat, one normally has one staticly defined
ip-address on the frontend interface on each server, and
10 matches
Mail list logo
