Hi Bryan,
I am somewhat confused now..
So it sounds like the behavior of the brackets in combination with
default_backend is wrong since it seems to work fine there even with IP ACLs.
And what I meant is, wouldn’t it make sense to support e.g. IP ACLs with either
{} or () or whatever else to allow one to group the rules instead of writing
multiple use_backend lines?
For small stuff, like in my example, it would make it slightly “easier”.
use_backend if somecondition (foo or bar)
vs.
use_backend if someconditoon foo
use_backend if someconditoon bar
Mit freundlichen Grüßen,
Christian Ruppert
--------------------------------------------
Christian Ruppert
Systemadministrator
Babiel GmbH
Erkrather Str. 224 a
D-40233 Düsseldorf
Tel: 0211-179349 0
Fax: 0211-179349 29
E-Mail: [email protected]
Internet: http://www.babiel.com <http://www.babiel.com/>
Geschäftsführer: Georg Babiel, Dr. Rainer Babiel, Harald Babiel Amtsgericht
Düsseldorf HRB 38633
~~~~~~~~~~~~~~ DISCLAIMER ~~~~~~~~~~~~~~~
The information transmitted in this electronic mail message may contain
confidential and or privileged materials. Any review, retransmission,
dissemination or other use of or taking of any action in reliance upon, this
information by persons or entities other than the intended recipient is
prohibited. If you receive such e-mails in error, please contact the sender and
delete the material from any computer.
Von: Bryan Talbot [mailto:[email protected]]
Gesendet: Freitag, 22. März 2013 16:35
An: Christian Ruppert
Cc: Baptiste; HAproxy Mailing Lists
Betreff: Re: use_backend: brackets/grouping not accepted in condition
On Fri, Mar 22, 2013 at 2:47 AM, Christian Ruppert <[email protected]> wrote:
Hi Baptiste,
it is IMHO not really clear that brackets are for anonymous ACLs only.
Wouldn't it make sense to support it for use_backend as well?
Those two are not mutually exclusive: you can use them with use_backend and
they are for anonymous acls.
for example:
use_backend www if METH_POST or {path_beg /static /images /img /css}
-Bryan
