Whether I have the rules in the backend or the front does not seem to make a
difference - I tried some rules in front and back and neither worked.
Maybe I am missing something obvious.
Thanks.
Example with config:
[haproxy]# wget -S -O - http://10.1.1.251:82/blank.gif
--2011-09-08 19:00:59--
On Don 08.09.2011 07:51, Willy Tarreau wrote:
Hi Aleks,
On Thu, Sep 08, 2011 at 12:52:20AM +0200, Aleksandar Lazic wrote:
Hi Willy,
I have take a look about the last test on
http://haproxy.1wt.eu/10g.html
and thought it would be nice to see a test with the brand new 1.5
version.
What do yo
On Thu, Sep 08, 2011 at 02:22:29PM +0200, Brane F. Gra??nar wrote:
> On Thursday 08 of September 2011 11:21:34 Finn Arne Gangstad wrote:
> > On Thu, Sep 08, 2011 at 07:43:46AM +0200, Willy Tarreau wrote:
> > > Hi again,
> > >
> > > This morning I had an better idea : pass the "config directory" pa
Heh. Too many different versions of this now, so faulty version was
sent. Stripping delimiters at the end of the pattern was broken.
The following needs to be applied on top:
diff --git a/src/acl.c b/src/acl.c
index cb49b43..1e8468e 100644
--- a/src/acl.c
+++ b/src/acl.c
@@ -591,7 +591,7 @@ stati
By the way, haproxy could be configured with default max size at 1024 and if
we want to increase it by config it may be available (as long as we are not
using a real syslog server).
My concern is about network device with UDP frame bigger than 1024 if
anybody is aware of potential probleme that c
Hi Graeme,
You are rigth so maybe it could be great that haproxy could log the full
entry by other way than syslog
Using the Unix socket allready existing could be tailed by any external
program I suppose, and shouldn't be limited by a 1024 string maybe.
Regards,
--
Damien
2011/9/8 Graeme Dona
Hi Everyone!
We move from nginx to haproxy for load balancing and all have been
great! All we do with nginx (as balancer) we have been able to do it
using haproxy, except for reprocessing a request on http error 5* from
upstream servers as we did with nginx using option
proxy_next_upstream. Is the
Hi Damien
I may be wrong, but as far as I can gather the 1024-byte limitation is
imposed by the syslog protocol RFC (http://www.faqs.org/rfcs/rfc3164.html)
and not HAproxy itself.
Regards,
Graeme.
On 8 September 2011 16:09, Damien Hardy wrote:
> Hello there.
>
> We are working on our realtime
Hello there.
We are working on our realtime statistics of consultation platform based on
haproxy logs.
Our probleme is that logs can capture HTTP headers but are limited to a 1024
length string witch is very short if Host: Referer: and User-Agent: are
captured as we are doing.
Is it planned to se
Yes ...
Is it possible to improve my config?
Le 08/09/11 15:50, « Baptiste » a écrit :
>I can't see anything weird here.
>are the backend status "OK" on the haproxy http stat page?
>
>cheers
>
>On Thu, Sep 8, 2011 at 2:28 PM, Christophe Rahier
> wrote:
>> Hi,
>>
>> Here's my config. Webserver
I can't see anything weird here.
are the backend status "OK" on the haproxy http stat page?
cheers
On Thu, Sep 8, 2011 at 2:28 PM, Christophe Rahier
wrote:
> Hi,
>
> Here's my config. Webservers are IIS.
>
> global
> log 192.168.0.2 local0
> log 127.0.0.1 local1 notice
> maxconn 10240
> defa
Please click here if the e-mail below is not displayed correctly.
Follow us:
Free Two-Day Shipping with › Amazon Prime
Your Amazon.com
Today's Deals
See All Depar
does hdr_cnt not work or am I just completely unable to get an example that
works? I can't imagine it doesn't work but I have tried _many_ - some examples
and nothing seems to work (maybe it is 40+ hrs):
acl hdrcnttest hdr_cnt gt 0
reqadd x-has-host:\ YES if hdrcnttest
acl hdrcnttest hdr_cnt
Hi,
Here's my config. Webservers are IIS.
global
log 192.168.0.2 local0
log 127.0.0.1 local1 notice
maxconn 10240
defaults
logglobal
option dontlognull
retries2
clitimeout 5
srvtimeout 5
contimeout 5
timeout server 60s
listen WebPlayer-Farm 192.168.0.2:80
mode http
opt
On Thursday 08 of September 2011 11:21:34 Finn Arne Gangstad wrote:
> On Thu, Sep 08, 2011 at 07:43:46AM +0200, Willy Tarreau wrote:
> > Hi again,
> >
> > This morning I had an better idea : pass the "config directory" parameter
> > on the command line and have haproxy chdir() to it. That way, eve
Hello,
you server might be very slow or your server timeout in your conf
might be too low.
If you can copy/paste your conf and tell us which version you're using
and the underlying OS.
cheers
On Thu, Sep 8, 2011 at 1:35 PM, Christophe Rahier
wrote:
> Hi,
> I've a question about this error :
>
Hi,
I've a question about this error :
504 Gateway Time-out
The server didn't respond in time.
What could I check in my config ? I created 2 LB with a virtual IP and all
request are coming from the firewall to this IP.
I think it's possible, if needed, I can copy my configuration file.
Thanks
*_dom is mostly used for matching Host headers, and host headers may
include port numbers. To avoid having to create multiple rules with
and without : in hdr_dom rules, change the *_dom
matching functions to also handle : as a delimiter.
Typically there are rules like this in haproxy.cfg:
acl i
I was wondering if acls that I create in the frontend should be available in
backends, too? I was getting errors when I tried but the error disappeared
when I either moved the reqadd/rspadd to the frontend or if I used a
predefined acl like LOCALHOST.
Thanks.
On Thu, Sep 08, 2011 at 07:43:46AM +0200, Willy Tarreau wrote:
> Hi again,
>
> This morning I had an better idea : pass the "config directory" parameter
> on the command line and have haproxy chdir() to it. That way, everything
> specified after it is relative to this dir, and you don't need a ful
20 matches
Mail list logo
