Forum Discussion
Jason_Hook_4092
Jun 28, 2011Nimbostratus
PERSIST at the pool level only
I have a single VIP that will have two types of users. I don't want to define URLs for both so I'd like to use the PERSIST functionality, but only to keep a session going to the same pool, and not s...
Jason_Hook_4092
Jul 11, 2011Nimbostratus
I will actually need to hybrid the two together, but keep them separate. I'm sure that makes a lot of sense.
I have 2 complete environments behind one VIP. One client is paying for separate hardware (one set of servers) and then there's everyone else (other set of servers).
I need to accomplish 2 things.
1) I need to determine if I have client A or not client A and choose a web pool based on A or not. I'm setting a session cookie to track this and direct appropriatly.
2) I need to take all /streamer calls and persist to a node, but only after I pick client A or not A. So I need to only get to the correct side/pool (based on the solution for 1) then let the PERSIST kick in to the node.
If I check the URI for <> "/streamer' for the regular iRule for 1 above.... and then for 2 only process when URI = "/streamer" I should be ok?
I hope I explained that clear enough.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects