On 06/06/17 03:20, rolelael wrote: > I understand , but .. > > /^route_gcgw: BE/ WARN Test > > is triggered now.....
Because that's a single-line test. Your other test is failing because if the /route_gcgw/ condition is triggered, you try to compare *the line that triggered it* against a condition that cannot match it because it's in a different header line. Consider this: I have four colors of balls, red, blue, green, yellow. I toss you balls I pull out of a bag. You have a large pipe at your feet. You are instructed that if you catch a red ball, you toss the next ball back to me *if it is blue*; otherwise you drop all other balls down the pipe. I toss you a red ball. What are you going to do with the next ball that I haven't pulled out of the bag yet? You have to decide now, because you have a red ball in your hand. Or suppose I give you another rule. If I toss you a green ball, toss the ball you received three balls ago back to me, instead of dropping it down the pipe, *if it was yellow*. You must not drop it down the pipe if it was yellow and I toss you a green ball now. Do you see the problem here? This is why your multiline tests are not working. You're trying to make action decisions on headers you've either already decided not to take that action on, and can't refer back to, or which you haven't seen yet. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958
