Forum Discussion
vinceKahn_97184
Apr 17, 2008Historic F5 Account
only redirect new http requests to outage pool
I'm trying to create an irule that checks active pool members and current sessions before sending them to an outage pool. If the user is already logged in and the pool members are down I don't want them to get redirected to the outage pool. Only new requests at this point should get the outage page. I've managed to key off the existence of the persistence cookie we set but I'm not sure this is the best or most dependable method to validate a current session. Is there a better method? Here's what I have:
when HTTP_REQUEST {
if { [active_members sso_pool] == 0 and ![HTTP::cookie exists BIGip] } {
pool sso_outage_pool
}
}
Thanks for your help.
Vince
- hoolio
Cirrostratus
nmenant provided a good rule-less solution for this using a fallback host on the HTTP profile (Click here). - vinceKahn_97184Historic F5 AccountThanks I didn't see that. It appears from that thread the best way to validate an existing session is cookie.
- hoolio
Cirrostratus
You can configure the URL to redirect to in the HTTP profile on the VIP. nmenant pointed out that the default behavior when you disable a node is to still allow requests that have a valid persistence record or an existing TCP connections to continue. So you shouldn't need a rule.
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