Forum Discussion
Jason0_309417
Apr 17, 2017Cirrus
I usaully use a URI forwarding policy to direct traffic based off URI. You can setup a different pool, with whatever port you want, for each special URI and use the virtual server's default pool for all other traffic
Local Traffic >> Policy
Rule X: HTTP URI path starts with /X Forward traffic to pool testsite.uri.X
Rule Y: HTTP URI path starts with /Y Forward traffic to pool testsite.uri.X
- JoelS_272975Apr 18, 2017Nimbostratus
Thanks Jason. That does seem more efficient. I haven't ever messed with policies to be honest. However, I'm guess the configuration would look something like this (we are running 11.6 code):
Policy Strategy: First-Match Requires: http Controls: forwarding Rules Conditions. operand: http-uri event: request* selector: path condition: equal (or contains) */X */Y Actions Target: Forward Event: Request Action: select Parameter: pool (POOL-ABC)
Does that look correct based on your experience?
Thanks in advance!
- Jason0Apr 19, 2017Nimbostratus
That's how I've configued my URI policies. One piece of advice, don't put a / as the first character of your rule name. 11.6 processes rules with this syntax but 12.1.2 cannot.