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
           }
      }
 }

We were hoping that we could send the traffic to the appropriate environment (QA, UAT, Prod) based on what the end user was entering for a uri (/QA, /UAT or /Prod) such as https://www.domain.com/QA/Signon.jsp but the actual QA web server does not have a /QA so that "/QA" would need to be removed from the uri but everything before or after the "/QA" would be valid and need to keep that in the uri. So what the web server would see coming in would be https://www.domain.com/Signon.jsp. Hopefully that makes more sense. Clear as mud?

 

 

Thanks,

 

Greg

 

 

 

Thanks...that's what I assumed. Does the most recent rule I wrote accomplish this? I had made a small error that I just modified.

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 qeneral_pool
                        }
      }
 }

Chris,

The string first command works nicely with this because you can skip the first forward slash and get the index of the second forward slash (after the /qa or /uat directory) using the "startIndex" parameter. But the string range commands you used have the same effect. But make sure you're checking for URIs starting with a forward slash in your switch statement (/uat and /qa). And you'll need a -glob flag on the switch statement.

Greg,

The HTML content that the server replies with won't have these /qa or /uat prefixes unless the servers have been configured to include them. You could try to insert them in all of the HTML, but it would get complicated trying to parse the HTML. If the initial request from the users contains the prefix, you could set a cookie to track that they're a UAT, QA or general user. You could check for that cookie if the URI doesn't match a UAT or QA URI.

Here's an untested example:

when HTTP_REQUEST {
    Default to not setting a pool cookie
   set pool_cookie ""
    Check URI set to lower case with wildcard matching
   switch -glob [string tolower [HTTP::uri]] {
      "/uat*" {
         pool uat_pool
         HTTP::uri [string range [HTTP::uri] [string first "/" [HTTP::uri] 1] end]
         set pool_cookie uat
      }
      "/qa*" {
         pool qa_pool
         HTTP::uri [string range [HTTP::uri] [string first "/" [HTTP::uri] 1] end]
         set pool_cookie qa
      }
      default_pool {
          Check if user has pool cookie
         switch [HTTP::cookie pool_selector] {
            "qa" {
               pool qa_pool
            }
            "uat" {
               pool uat_pool
            }
            default {
               pool general_pool
            }
         }
      }
   }
}
when HTTP_RESPONSE {
    Set a pool selector cookie if a UAT or QA pool as selected in request
   if {$pool_cookie ne ""}{
      HTTP::cookie insert name pool_selector value $pool_cookie
   }
}

Aaron

Hi Greg,

 

We have a similar kind of situation here ie. there is an existing pool on the Loadbalancer supporting a website "www.domain.com". Currently, whenever an user types in the URL tab as www.domain.com, that request is re-directed to that existing pool on our Loadbalancer. The requirement is that whenever an user enters the URL name as www.domain.com, the request should be re-directed to one particular pool( which is yet to be created ) and if the user types specifically www.domain.com/abc or whatever the content maybe after the domain-name, the request should hit the existing pool. To accomplish this, will this below given script help?

 

 

switch [string tolower [HTTP::uri]] {

 

"*" {

 

existing_pool

 

}

 

default_pool {

 

New_pool

 

}

 

}

 

 

Thanks..