Altostratus
MVPHi cmeyer,
are you looking for Content Switching / URL based load balancing? In that case, this iRule should be a starting point:
when HTTP_REQUEST {
switch -glob -- [string tolower [HTTP::path]] {
"/path1*" {
pool pool_app1
return
}
"/path2*" {
pool pool_app2
return
}
default {
pool pool_default
}
}
}Is this helpful for you?
KR
Daniel
AltostratusDaniel_Wolf In this case my pools would stay the same. I am utilizing the same servers in each case. Not sure if that matters.
MVPIf you have loadbalancing for page.domain.com, loadbalancing will also work for page.domain.com/subsite1, page.domain.com/subsite2, or anything else - since they are served by the same pool of servers as page.domain.com. In this scenario, there is no need for an additional iRule.
Unless... I didn't get your setup right 🙂
AltostratusI think I understand. I would specify the same pool in the rule and define "path1" and "path2". There is currently no iRule in place since we were balancing just the single page. I will give that a try. Thanks for the help!
MVPEven less complicated. You don't have to specify the paths anywhere.
You have a virtual IP address configured on the BIG-IP, DNS resolves a FQDN to this IP address. The BIG-IP will accept any request from the client to the virtual IP and load balance the request to servers in the pool.
In this scenario there is no need to further specify the path. The servers in the pool will serve them anyway.