Forum Discussion
navgup_66025
Nimbostratus
Aug 08, 2013Auth_Status and Persist
1) I have PoolK and PoolF and default pool has to be PoolK
2) first client request always go to PoolK
3) Check if client has been authenticated to PoolK using Auth_status command, if YES pe...
Kevin_Stewart
Employee
Aug 10, 2013I think the bigger issues are this:
1. When the server sends back a 401, presumably to request authentication, you're immediate changing that to a 302 redirect. I don't suspect you're getting prompted for authentication??
2. If you let the 401 through to the client (don't do the redirect), then you should only need to check for the existence of the "PD-S-SESSION-ID-PROD2" cookie (sent in the 401) on each future request to send traffic back to poolK. So perhaps something like this:
when HTTP_REQUEST {
if { ( [string tolower [HTTP::uri]] starts_with "/nad" ) or ( [HTTP::cookie exists PD-S-SESSION-ID-PROD2] ) } {
pool poolK
}
}
You would also want to enable a OneConnect profile and (simple) cookie persistence.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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