Need a sanity check on a URI parsing rule...

You may also use multiple classes to partition your pool matching.

Eg, create several classes (aka "data groups" or "value lists").

   
 class hrmstest_uris {   
  "/hrtest"   
  "/hr"   
  "/psp/HR"   
 }   
 class crtest_uris {   
  "/cr"   
 }   
 

Then in your rule have:

   
 when HTTP_REQUEST {   
    if { [matchclass [HTTP::uri] starts_with $::hrmstest_uris] } {   
       pool hrmstest   
    }   
    elseif { [matchclass [HTTP::uri] starts_with $::crtest_uris] } {   
       pool crtest   
    }   
    else {   
       pool fintest   
    }   
 }   
 

You could also use a combination of matchclass tests with standard contains/starts_with tests.

Also, the matchclass commmand can be used with the operators equals, contains, starts_with and ends_with.