Hi all,
The ability to extend the option httpchk argument string to dummy
up a Host header is described as a 'trick' in the configuration
documentation. I have found that the 'trick' can be extended to add
User-Agent (HAProxy) and Accept (*/*) headers to keep ModSecurity quiet when
checking an Ap
I wasn't able to find it in the documentation, what does the "sL"
termination flag stand for?
Thanks.
-Joe
--
Name: Joseph A. Williams
Email: j...@joetify.com
Blog: http://www.joeandmotorboat.com/
On Fri, Feb 26, 2010 at 01:39:48PM -0800, Sriram Chavali wrote:
> Thanks for your reply,
>
> The redirect location is actually on a different server that is behind the
> firewall. What is best way to configure for this?
Then you'd better create a specific backend for it and force rewrite the UR
Thanks for your reply,
The redirect location is actually on a different server that is behind the
firewall. What is best way to configure for this?
Sriram
On Feb 26, 2010, at 1:36 PM, Willy Tarreau wrote:
> On Fri, Feb 26, 2010 at 01:24:25PM -0800, Sriram Chavali wrote:
>> I have written a ru
On Fri, Feb 26, 2010 at 01:24:25PM -0800, Sriram Chavali wrote:
> I have written a rule in my haproxy configs to redirect the incoming request
> to a certain page based on an acl rule being satisfied. It looks like as
> following:
> redirect location http://server:port/violation.html if acl_met
>
I have written a rule in my haproxy configs to redirect the incoming request to
a certain page based on an acl rule being satisfied. It looks like as following:
redirect location http://server:port/violation.html if acl_met
The redirected page is on the same server - however I don't want the redi
Willy Tarreau wrote:
On Fri, Feb 26, 2010 at 03:57:16PM -0500, Jeff Buchbinder wrote:
With that patch it does seem to build the files that were getting stuck
before under OpenBSD 4.3.
Excellent, thanks very much Jeff for your quick response,
I'm applying the patch now.
Much apprecia
On Fri, Feb 26, 2010 at 03:57:16PM -0500, Jeff Buchbinder wrote:
> With that patch it does seem to build the files that were getting stuck
> before under OpenBSD 4.3.
Excellent, thanks very much Jeff for your quick response,
I'm applying the patch now.
Cheers,
Willy
Fwd to list to keep it in the loop
-- Forwarded message --
From: Ariel Moreno
Date: Feb 26, 2010 3:53 PM
Subject: Re: HAProxy - Frontend / Backend transparency
To: "German Gutierrez :: OLX Operation Center"
German, yes in deed! I have site redundancy configured for this
service
Willy Tarreau wrote:
Could you please check if the following patch is enough to fix it ?
I think it should in fact.
Thanks,
Willy
diff --git a/include/common/compat.h b/include/common/compat.h
index 3c939ce..9eecdfb 100644
--- a/include/common/compat.h
+++ b/include/common/compat.h
@@ -23,8 +23
Hello,
On Fri, Feb 26, 2010 at 03:11:07PM -0300, Ariel Moreno wrote:
> Dear Sir.
> We are testing HAProxy in our network to balance some proxy
> servers and I was wandering about how the front-end and back-end interact to
> make the solution reliable.
> In this particular case, I h
On Fri, Feb 26, 2010 at 03:35:41PM -0500, Jeff Buchbinder wrote:
> Willy Tarreau wrote:
> >Thanks for your feedback, that helps a lot. Unfortunately I don't
> >have any OpenBSD anymore here :-/
> >
> No problem.
>
> About the error messages; it gives a bunch of error messages about
> "/usr/incl
On Fri, Feb 26, 2010 at 03:35:41PM -0500, Jeff Buchbinder wrote:
> Willy Tarreau wrote:
> >Thanks for your feedback, that helps a lot. Unfortunately I don't
> >have any OpenBSD anymore here :-/
> >
> No problem.
>
> About the error messages; it gives a bunch of error messages about
> "/usr/incl
Willy Tarreau wrote:
Thanks for your feedback, that helps a lot. Unfortunately I don't
have any OpenBSD anymore here :-/
No problem.
About the error messages; it gives a bunch of error messages about
"/usr/include/sys/socket.h", complaining about syntax errors.
If you run it on an OpenBSD
On Fri, Feb 26, 2010 at 10:45:58AM -0500, Jeff Buchbinder wrote:
> Willy Tarreau wrote:
> >I'm obviously interested in any problem report :-)
> >
> One other OpenBSD build problem that I saw was that OBJS in Makefile.bsd
> seems to be missing:
>
> src/auth.o src/stick_table.o src/pattern.o
oop
Hi Jeff,
On Fri, Feb 26, 2010 at 10:38:55AM -0500, Jeff Buchbinder wrote:
> Willy Tarreau wrote:
> >I'm obviously interested in any problem report :-)
> >
> Build on OpenBSD 4.3 seems to fail unless "#include "
> is commented out of the src/lb_*.c files. This seemed to be the case on
> both th
Dear Sir.
We are testing HAProxy in our network to balance some proxy
servers and I was wandering about how the front-end and back-end interact to
make the solution reliable.
In this particular case, I have simulated a full back-end proxy fail in
order to know if there will be any c
> Also, changing -devel right now at the same will cause all sorts of
> support issues as people deal with the migration - not everyone reads
> the UPDATING file before issuing "portupgrade -a".
Even a solution should be to mark the haproxy-devel has "Moved" (see
/usr/ports/MOVED)
I see in portup
AH>> However, the way I think it should go in the ideal situation, is that
AH>> the haproxy port should contain the latest and greatest stable release
AH>> (1.4.x), and the haproxy-devel port should go to the latest experimental
AH>> snapshot.. If you think keeping a 1.3.x tree alive is usefull (wh
On 26 Feb 2010, at 10:04, Angelo Höngens wrote:
> On 26-2-2010 16:42, Ross West wrote:
>>
>> Opening up a bit of discussion:
>>
>> For those Freebsd port users out there, I'm looking to submit updates
>> for the haproxy port to take it from it's current v1.2.18 to the new
>> v1.4.x tree - Leapf
On 26-2-2010 16:42, Ross West wrote:
>
> Opening up a bit of discussion:
>
> For those Freebsd port users out there, I'm looking to submit updates
> for the haproxy port to take it from it's current v1.2.18 to the new
> v1.4.x tree - Leapfrogging the v1.3.x tree (which is part of the
> haproxy-de
Willy Tarreau wrote:
I'm obviously interested in any problem report :-)
One other OpenBSD build problem that I saw was that OBJS in Makefile.bsd
seems to be missing:
src/auth.o src/stick_table.o src/pattern.o
to build properly. Once those are back in the OBJS list (and the
previous fix ha
Opening up a bit of discussion:
For those Freebsd port users out there, I'm looking to submit updates
for the haproxy port to take it from it's current v1.2.18 to the new
v1.4.x tree - Leapfrogging the v1.3.x tree (which is part of the
haproxy-devel port).
Note: I'm _not_ looking to change the h
Willy Tarreau wrote:
I'm obviously interested in any problem report :-)
Build on OpenBSD 4.3 seems to fail unless "#include "
is commented out of the src/lb_*.c files. This seemed to be the case on
both the i386 and amd64 targets I was building on.
--
Jeff Buchbinder
Senior Infrastructure
Hi all,
now's THE day.
1.4-rc1 was emitted 3 weeks ago, and very minor issues were reported
and fixed. There's no need to wait any longer, so let's release it now.
The code is remarkably stable and has no known regressions from 1.3.
(Some fixes from 1.4 will even have to be backported to 1.3 soo
hi,
just a followup with a solution that might save some other rails dude some
time. the fix below allows you to set the same timeouts for db connections
as you have for your webserver backends without major invasive surgery to
what rails expects (ie a persistent connection to db).
turns out that
Hi Malcolm,
On Fri, Feb 26, 2010 at 11:39:04AM +, Malcolm Turnbull wrote:
> Willy,
>
> Just a quick thank you for the new stick table feature:
>
> Brief testing has show this works really well, especially the option persist
> and option redispatch which when combined provide a very graceful
Willy,
Just a quick thank you for the new stick table feature:
Brief testing has show this works really well, especially the option persist
and option redispatch which when combined provide a very graceful shutdown
of the server for maintenance.
listenVIP_Name 192.168.2.194:80
modetc
Hi
Dnia 2010-02-25, czw o godzinie 21:07 -0500, Greg Gard pisze:
> hi guys,
>
> thanks for the feedback. yet another rails issue that makes deployment
> a hassle. my biggest issue with setting the timeouts is that when a
> user hits the page after a timeout, they will get a 5xx error, but
> perha
29 matches
Mail list logo
