Forum Discussion
Client persistance through 2 VS in a single request
Consider the following situation:
1) A virtual server is configured that passes traffic from a client to a pool of servers that provide authentication and authorization. Once authorization is complete, these servers will proxy all traffic to a secondary VIP (the target application) on every request.
2) Once the client is authenticated, The pool members of the first VIP send the clients request to a second VIP to connect to the application. This application also includes a session ID that must be persisted.
3) In order for the connection to function correctly with the application behind the second VIP, persistence must be maintained with the original client.
How can session persistence be maintained when the client IP is manipulated in this manner? I read the descriptions for the persist across pool members / virtual servers setting available within the persistence options, but it didn't seem to be appropriate for this situation
Client persistence with original client and pool member 2 of Vip 2.
Client -> VIP -> Pool member -> Vip 2 -> Pool member2
Any ideas?
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