Looking for best practices on creating iRules for pool members redirection

Thanks for the reply. Is there way you can add ssl::disabled serverside and contains using the switch command? I like the way I had it before, it allowed me specify everything under one statement for each the specific pools (e.g.. ssl disabled was under each if statement & the word contains). I need to be able to disable SSL serverside to the backend without globally shutting this off at the profile level. Can you take my example before and convert it to the switch commands and show me how this will look?

Yeah, the switch command can use pattern matching. Even some of the examples at the link I posted do this: "/uri/for/pool2/*" { log local0. "Matched pool 2 paths for [HTTP::uri]" pool pool2 }

Thank you. I've just tested out using traffic policy in version 11.6. I've created generic1-vip-443_policy and nested all of my rules which pertain to each separate application. I wanted to make sure going forward, that I can keep adding separate rules to this policy for different applications to be forwarded to different backend pools and if it make sense to create multiple policies for common applications. If it's going to check a top down order and it doesn't matter, then I'll just use generic1 for all of my forwarding decisions. Is the new traffic-policy the preferred method over iRules based on performance or just ease of use without writing complex iRules? Thanks again for your help.

You can control the execution of irules with the priority command. There is no other way to guarantee execution order other than combining them into a single rule. https://clouddocs.f5.com/api/irules/priority.html