Forum Discussion
irule or persistence session not holding on to session
Hi all, we have a web application upon logging in, it will be redirect to Pool_5555 for autentication then redirect back to Pool_5556 for the main webpage. Upon testing we notice it doesn't go back to the original node and causes "Session Expired" several times.
On the persistence profile, it's the normal cookie session but this issue will go away with source_ip_persistence profile. From my understanding source_ip_persistence is meant for TCP or UDP traffic while this is HTTP traffic.
I just like to know this is something to be fix on application or it's just the irule causing the issue ?
What we want to avoid is using F5 to have workaround solution for application shortcomings.
when HTTP_REQUEST {
switch -glob [string tolower [HTTP::path]] {
"/auth*" {
if {[HTTP::path] equals "/auth" }
{
HTTP::redirect "https://[getfield [HTTP::host] ":" 1][HTTP::uri]/"
} else {
HTTP::path [string map {"/auth" ""} [HTTP::path]]
pool Pool_5555
}
}
default {
pool Pool_5556
}
}
}
- jwlarger
Cirrus
Sounds like you need persistence across the services (same server for pools on 5555 & 5556)?
Recent Discussions
Related Content
* 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