Route to different pools based on /content

Just to verify, you're only trying to remove the QA/UAT string between LTM and the Pool Member? The client's will still see QA/UAT in their browser. If you're trying to remove it client-side, you'll need to do a redirect instead. I'll modify the rule assuming you're just trying to remove it between the LTM and pool member until you say otherwise.

Since I'm not solid with string first, let's do this:

when HTTP_REQUEST {
      Check URI set to lower case with wildcard matching
     switch [string tolower [HTTP::uri]] {
          "uat*" { pool uat_pool
              HTTP::uri [string range [HTTP::uri] 4 end ]
           }
           "qa*" { pool qa_pool
               HTTP::uri [string range [HTTP::uri] 3 end ]
           }
           default_pool { pool qeneral_pool
           }
      }
 }