Cookie Insert - non absolute timestamp

Posted By Hamish on 09/21/2010 03:26 AM

 

 

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?

 

 

 

You could...

 

 

Yes but in my world it´s gonna be complicates/resource increasing etc. If i can choose I want so little irules that is possibly.

 

 

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.

 

 

 

Again... You could. But that's not the way it works out of the box... If you want candy, you have to make it yourself (Or hire someone to doit for you).

 

 

Should be a feature, if you compare to Nortels old boxes then you can use session expire but when you put a node in disable state a timer is activate. Pretty nice feature.

 

i think also that this is a simple feature (if you had it before) so this is not candy for me =)

 

 

 

 

We have an internal "timestamp" for the application so the user will be logged out after 15 min if the are inactive.

 

 

 

OK. So set a session cookie with a 910 second timeout...

 

 

But as you say, then I´m forced to make up a session table or else i have the same situation as now. I´m dependent of the users clock....

 

 

 

 

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 =) ).

 

 

 

yes it does... Set the poolmember to 'Disabled' Then only persistent or active connections are allowed. Eventually they'll time out and you'll have no session left (How long is up to your users I'm afraid, but there's always 'Forced Offline' as well).

 

 

we do that now but we have pretty much users =) so a node will never have 0.

 

Of course i can put in a script that says that if it´s below aprox 50 we put the node offline.

 

However this will affect users and if it affect only one user, it´s one user to much.

 

 

Can you evolve this: "The value in the table for the key is the session info"

 

 

 

Yep. The cookie is a key (Encrypted or not). An opaque entity that when looked up in a hash table will give you the session information. Doesn't matter if the browser presents the cookie 30 minutes later. If the session table doesn't have the entry, it's expired. But if you set the cookie expiry to 901 (Or just over 900 seconds), then it'll expire in the browser about the same time as the session expires anyway. And won't be presented. And the number of people being distributed to that node WILL decrease.

 

 

H

 

 

 

maybe this can be a the way to do it, but it´s involving a lot of "homemade" tricks I guess.

 

 

 

 

So if nobody else have a solution I´m gonna move to "request feature" section at F5