Simplifying route irules

Question

Is there anyway to simplify the following rules  &nbsp;

&nbsp;
&nbsp;

&nbsp;
&nbsp;
 Route traffic to server1 if URL listed in class_goto_server1&nbsp;

&nbsp;
&nbsp;

&nbsp;
&nbsp;
when HTTP_REQUEST {&nbsp;

set $HTTPuri [string tolower [HTTP::uri]]&nbsp;
&nbsp;

URL starts_with check and Node select &nbsp;

if {[class match -name $HTTPuri starts_with class_toserver1_StartsWith]} {&nbsp;

pool server_1
&nbsp;

}&nbsp;

URL equals check and Node select &nbsp;

if {[class match -name $HTTPuri equals class_toserver1_Equals]} {&nbsp;

pool server1
&nbsp;

}&nbsp;
}&nbsp;

&nbsp;
&nbsp;

&nbsp;
&nbsp;
The content of the external class file: &nbsp;

&nbsp;
&nbsp;
- class_toserver1_StartsWith&nbsp;
/s/&nbsp;
/staff/&nbsp;
/tax/&nbsp;

&nbsp;
&nbsp;
- class_toserver1_Equals&nbsp;

/s
&nbsp;

/staff
&nbsp;

/tax
&nbsp;

&nbsp;
&nbsp;
The list is quite long ( about 500 lines ) &nbsp;

&nbsp;
&nbsp;
The reason we have these 2 class match  is because we want /staff/ to go to server1, but staff-profile to go to default server .&nbsp;
Im thinking of having just 1 class file and do the matching programatically using iRules. Is this possible and how ?  &nbsp;

&nbsp;
&nbsp;

hooleylist · Answer

Anything else I can think of would require looping through the datagroup element by element.  I think what you've got is probably the most efficient even if it's a bit inelegant to have nearly duplicate entries in two separate datagroups. 
 You should move the second lookup into an elseif clause to avoid doing a second lookup if the first one matched.  Or you could put it in one if clause with an ||.  But I think elseif might be a bit more legible.
You could remove the -name option from both class commands as you're not doing anything with the matching element. 
 Route traffic to server1 if URL listed in class_goto_server1
when HTTP_REQUEST {
   set $HTTPuri [string tolower [HTTP::uri]]
    URL starts_with check and Node select 
   if {[class match $HTTPuri starts_with class_toserver1_StartsWith]} {
      pool server_1
   } elseif {[class match $HTTPuri equals class_toserver1_Equals]} {
      pool server1
   }
}
 Aaron

_pre_ · Answer

Hoolio ! Thanks for the confirmation and code suggestions. It's comforting to hear that the code is the efficient  (especially from you) :)  &nbsp;

spark_86682 · Answer

Hm. I think you actually could do a bit better. How about something like:

when HTTP_REQUEST {

set HTTPuri "[string tolower [HTTP::uri]]/"

URL starts_with check and Node select 
   if {[class match $HTTPuri starts_with class_toserver1_StartsWith]} {
      pool server_1
   }
}

Basically, always append a "/" character to the URI and then just do a "starts_with" search. If the URI is already "/staff-profile/" (or even "/staff-profile"), then that won't start with "/staff/", so it won't match that class entry.  That way you're only doing one class lookup, and only have to maintain the one class.

If all of your class entries are only one directory level deep, then you can do even better than that:
when HTTP_REQUEST {

set HTTPtopdir "/[getfield [string tolower [HTTP::uri]] "/" 2]/"

top directory equals check and Node select 
   if {[class match $HTTPtopdir equals class_toserver1_equals]} {
      pool server_1
   }
}

That second example assumes the entries in class_toserver1_equals all end with slashes (meaning, "/staff/", and not "/staff").

ryan_paras_7933 · Answer

Similar to spark's second snippet of code, if you are looking only one directory level deep you can do the following: &nbsp;
&nbsp; when HTTP_REQUEST {

&nbsp; set HTTPtopdir [lindex [split [string tolower [HTTP::uri]] /] 1]
   
&nbsp; if {[class match $HTTPtopdir equals class_toserver1]}
&nbsp; {
&nbsp;   pool server1
   
&nbsp; }
&nbsp;}&nbsp;
&nbsp; This takes URI "/xxx/yyy/zzz" and sets HTTPtopdir to just "xxx". It then does a class match against a class looking to match "xxx". &nbsp;
&nbsp; This would allow you to have a simpler class definition, such as: 
&nbsp;class class_toserver1 {
   
&nbsp; {
      
&nbsp;  "s"
      
&nbsp;  "staff"
      
&nbsp;  "tax"
   
&nbsp; }

&nbsp;}&nbsp;

_pre_ · Answer

Thanks for the reply guys, but unfortunately I need to have "equals" lookup as well as starts_with and directory level varied from 1 to 6.   
&nbsp;  &nbsp;

Forum Discussion

Simplifying route irules

7 Replies

Recent Discussions

How to target only webview rendering with CSS?

ltm policy asm_auto_l7_policy

MAC address not showing up in LLDP packet

F5Access | MacOS Sonoma

Active- Active HA setup

Related Content

Application Programming Interface (API) Authentication types simplified

Simplifying Kubernetes Ingress using F5 Technologies

Re: Public Cloud Simplified with F5 NGINX for Azure

F5 SLEDFest 2022 Sacramento Edition - Simplify Your App Security with F5 Distributed Cloud (XC)

Routing traffic by URI using iRule