Forum Discussion
Michael_Mau_108
Nimbostratus
NimbostratusREGEXP parsing URI
Hello all,
I have a customer who assigns each of his 100+ users with a service name, so he is able to indentify who each customer group is, and what environment they are trying to access (accepta...
Michael_Mau_108Nimbostratus
NimbostratusThanks for the replies. I appreciate it. I still have to put more thought into which version would be the most effective:
when HTTP_REQUEST {
switch -glob [HTTP::uri] {
"XML_[A-Z]*_P" -
"XML_[A-Z]*_T"
{
drop
}
default {
pool pool-default
}
}
}
OR
when HTTP_REQUEST {
switch -glob [HTTP::uri] {
"XML_[A-Z]*_T"
{
pool pool-default
}
default {
drop
}
}
}
Either way I go about it, I will have to create a unique i-rule for each unique VIP. Is there any way to send the request to which ever pool is defined within the VIP that the rule is applied to, rather than send to a pool within the I-rule?
Is there any way to say within the rule, to match a URI and reject that request, and if there are no matches, to not use a default statement; or is the request automatically dropped if there is no match for HTTP::uri?
Thanks for the help.
