Forum Discussion
Hyun-Sub_Kim_37
Nimbostratus
Jul 01, 2005the existing user must connect the Web Server even if the Connection reach the limit.
1. Using the Connection limit with Cookie.
- So. If user reach the connection limit, Web Server reject only new connection.
2. If user have cookie(the existing user), the existing user must connect the Web Server even if the Connection reach the limit.
I find answer of number 1 in Forum. But I can not find answer of the number 2.
How should I use iRule ?
2 Replies
- drteeth_127330Historic F5 AccountThis should work as you want without an iRule. The connection limit on a virtual server only applies to new connections, not persistent connections.
- Hyun-Sub_Kim_37
Nimbostratus
Test 1. Using Cookie persistence and connection limit on virtual server. (Service check is http)
When I use connection limit on virtual server, the BIG-IP do not receive new session and existing session.
That`s why, the existing session is disconnected when user already established session.
Test 2. Using Cookie persistence and connect limit on pool member. (Service check is http)
When connections on the pool member reach the limit, status on pool member is also yellow color and then unavailable.
Also client can not connect the same web server.
So, I think I shoud use iRule. drteeth !
Thank you drteeth
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
