Hi!
I wonder how maxconn and weight (both in a server statement) exactly
interact. The docs in section 5 says about maxconn:
If the number of incoming concurrent requests goes higher than this value, they
will be queued, waiting for a connection to be released.
But know I wonder where the
I'm confused over the behaviour of the url criteria in layer 7 acls.
If I have a definition of the form:
acl xxx_host hdr(Host) -i xxx.example.com
then something like this works fine:
use_backend xxx if xxx_host
If I try something like this:
acl xxx_u
On Tue, Apr 27, 2010 at 05:07:12PM -0500, Graham Barr wrote:
> We are using 1.4.4 but whenever we access the stats via
> /admin?stats;norefresh we are unable to get the full page and end up with a
> page within a page.
what do you call "a page within a page" ? Could you please save what
you rece
On Tue, Apr 27, 2010 at 05:36:12PM -0700, Dustin Moskovitz wrote:
> Actually, I spoke too soon. When I create a config similar to Laurie's (see
> below), I find that I still don't see headers and my default backend is
> always utilized. I originally mistook this for working. Laurie, are you
> posit
Actually, I spoke too soon. When I create a config similar to Laurie's (see
below), I find that I still don't see headers and my default backend is
always utilized. I originally mistook this for working. Laurie, are you
positive you are actually routing traffic based on the hdr rule? This
implies t
Yea, this was due to a failure to clean between builds, sorry about that. I
think we've got what we need now, thanks!
On Tue, Apr 27, 2010 at 3:11 PM, Willy Tarreau wrote:
> On Tue, Apr 27, 2010 at 02:54:24PM -0700, Dustin Moskovitz wrote:
> > Yea, I should have thought of that - certainly we ar
On Tue, Apr 27, 2010 at 02:54:24PM -0700, Dustin Moskovitz wrote:
> Yea, I should have thought of that - certainly we are on the cutting edge
> :)
>
> Unfortunately, when I try to upgrade from 1.4.0, I am unable to get the
> proxy up and handling requests (forgetting the virtual hosts thing, just
We are using 1.4.4 but whenever we access the stats via /admin?stats;norefresh
we are unable to get the full page and end up with a page within a page.
On the 1.3 know bugs list at http://haproxy.1wt.eu/knownbugs-1.3.html there was
an item "stats output limited to 16 kB" but that page seems to i
Yea, I should have thought of that - certainly we are on the cutting edge
:)
Unfortunately, when I try to upgrade from 1.4.0, I am unable to get the
proxy up and handling requests (forgetting the virtual hosts thing, just
trying to use the config I already had working). The only thing I see in the
Hi Willy,
Thank you very much for your reply. I will wait for a stable release of this
new feature.
Best Regards,
---
Fernando Marcelo
www.consultorpc.com
ferna...@consultorpc.com
Em 27/04/2010, às 17:34, Willy Tarreau escreveu:
> Hi Fernando,
>
> On Tue, Apr 27, 2010 at 04:50:17PM -0300, Fe
Hi Fernando,
On Tue, Apr 27, 2010 at 04:50:17PM -0300, Fernando Morgenstern wrote:
> Hello,
>
> I'm using haproxy with httpchk health check.
>
> At a first moment, i was using a simple check.txt file but i found out that
> it was not enough as some of the server problems are not detected with t
Hello Damien,
On Tue, Apr 27, 2010 at 10:33:41AM +0200, Damien Hardy wrote:
> Hello all,
>
> haproxy docs are quite difficult to manipulate.
>
> I had begun a Greasemonkey
> (https://addons.mozilla.org/fr/firefox/addon/748) script to create a
> "clickable" ToC in the haproxy documentation ...
>
Hi Laurie, hi Dustin,
First, Dustin, you really need to get a very recent version of haproxy.
1.4.4 is fine. This is particularly important because handling of the
101-switching protocol is something new (and the WebSockets draft is
evolving quickly and the latest version is not anymore compatible
On Mon, Apr 26, 2010 at 11:00:36PM +0100, Matt wrote:
> The doc says that http-pretend-keepalive can be set in a backend only, but
> when haproxy is reloaded with this option set :-
>
> 'http-pretend-keepalive' ignored because backend has no frontend
> capability.
grrr... looks like a stupid
Hello,
I'm using haproxy with httpchk health check.
At a first moment, i was using a simple check.txt file but i found out that it
was not enough as some of the server problems are not detected with this.
I have another url that checks server status and return a header if eveything
is ok. Is i
Hi,
Le mardi 27 avril 2010 13:14:14, Kari Lavikka a écrit :
> Ok, I actually found something under thread "haproxy-1.4.3 and
> keep-alive status".
>
> By default, "tunneling" is used.
Exactly !
> The solution would be "option
> http-server-close" but Jetty doesn't play nicely. Well thanks any
On 2010-04-27 13:14, Kari Lavikka wrote:
> By default, "tunneling" is used. The solution would be "option
> http-server-close" but Jetty doesn't play nicely. Well thanks anyway :)
Hi Kari,
Jetty was one of the (broken) servers for which
option http-pretend-keepalive was introduced. You should try
Ok, I actually found something under thread "haproxy-1.4.3 and
keep-alive status".
By default, "tunneling" is used. The solution would be "option
http-server-close" but Jetty doesn't play nicely. Well thanks anyway :)
- Kari
Kari Lavikka kirjoitti:
Hi
I'm evaluating HAProxy and it looks ve
Hi
I'm evaluating HAProxy and it looks very promising. However, I noticed
odd behavior and didn't find any documentation regarding it.
I have the following configuration:
frontend irc-galleria
bind...
modehttp
use_backend chatserver if
Hi Dustin
We are doing something very similar. I have a sample of our config file
below. However this is not perfect. We are seeing a lot of dirty connections
for normal http traffic because of the long timeout,
and we are having some, as yet not-fully-diagnosed issues with incorrectly
terminated
Hello all,
haproxy docs are quite difficult to manipulate.
I had begun a Greasemonkey
(https://addons.mozilla.org/fr/firefox/addon/748) script to create a
"clickable" ToC in the haproxy documentation ...
You can DL it at http://userscripts.org/scripts/show/75315
Next step :
search the options,
21 matches
Mail list logo
