Forum Discussion
MR_RJ
May 16, 2011Cirrus
Hi,
I've been looking into a few of those examples and most of them add a persist on either the uri or the content.
I would like to match on both things, if the uri is /blah/securid.dll ...then check content from the web server for "next token..." if these two are true then add the session to the persistent table. This solution should lead to only a few persistent connections which makes the maintenance a lot easier since putting the nodes in disabled would drain the sessions in just a few minutes like it does today (except for the ~3 users that is persistent atm).
//Robert