Forum Discussion
Beinhard_8950
Nimbostratus
Sep 20, 2010Cookie Insert - non absolute timestamp
Hi,
Little history first of my problem.
At first i have used session expire.
If you do that you can´t use disable on a node (gracefully) because the session expire is just in ...
Beinhard_8950
Nimbostratus
Sep 21, 2010hmm,
if you use cookie as persistence i don´t have a session table (persistence table).
So you mean that i should do a irule that make that table?
Why can´t just the f5 do a timestamp that just the f5 understand so the client doesn´t know to understand, as you say, a opaque value.
"FWIW trying to do session timings in the client is NOT a good idea"
I agree to 100%, thats why i started this thread.
We have an internal "timestamp" for the application so the user will be logged out after 15 min if the are inactive.
In the apps we use a timestamp that is just opaque (timer starts from zero and counting up to 900) so it´s independant from time.
But this doesn´t help if i want the gracefully service for a node, so no new "users" go to that node and the current users will decrease becaue i have session expire in the F5 (yeah, i´m repeating again =) ).
Can you evolve this: "The value in the table for the key is the session info"
If it´s to any help i´m using SSL to clients and to the backend servers.
Regards,
Beinhard
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