There is a somewhat easy way to do this via leveraging the
functionality of SetEnvIfExpr. For example, what I am testing
is the idea of:
SetEnvIfCond "-R '10.0.0.0/8' || -R '172.16.0.0/12' || -R
'192.168.0.0/16'" rfc1918
Which creates and stores *but does not evaluate* the above expression,
which is called 'rfc1918' (ie: the name of the envvar also serves as the
name/label of the condition).
We can then call:
EvalEnvfIfCond rfc1918
which will then evaluate the expression at *that* time, and
set/unset the 'rfc1918' envvar as required.
> On Dec 29, 2015, at 3:21 PM, Jim Jagielski <[email protected]> wrote:
>
> I've been mulling over having the check return
> the response headers which can then be checked/verified using
> our Expression routines ala <If>. eg:
>
> Condition all_good "%{REQUEST_STATUS} in { '200', '304' }"
>
> And there is a 'check' mini-directive:
>
> BalancerMember http://www.example.com/ method=get check=all_good
>
> which uses the stored condition for the pass/fail test.
