Jason L Tibbitts III <tibbs@hpc.uh.edu> writes:
> subscribe
> consult
> ADDRESS_MISMATCH
>
> subscribe
> allow
> /sps\.mot\.com$/i
> /mcu\.mot\.com$/i
>
> subscribe
> consult
> ALL
I don't know if this is more powerful or more intiutive, but I like
the way NCSA-derived http servers do this, in that they allow you to
establish your default behavior explicitly and then modify that:
order deny, allow
allow from /(sps|mcu)\.mot\.com$/i
or:
order allow, deny
deny from ADDRESS_MISMATCH
I, at least, find this much more intuitive than the above, which
reminds me of the hosts.allow/hosts.deny stuff, the order of
processing of which I always have to look up. With the http servers,
I can glance at the config file and know if I'm being paranoid or not
right off the bat.
> As for storing these expressions, I'm not quite sure of how to do
> it.
Maybe you could create a reference to an eval which creates a
subroutine which does the regex---I think that might do what you want,
I'm not sure.
Mike.
Follow-Ups:
References:
|
|
