Forum Discussion
mpfeifer_63884
Nimbostratus
Nov 30, 2009cookie expire
Hi.
We'd like to change the expiration date of a Cookie when a client comes in with a certain Useragent-string.
Normally our users just get the default Cookie which expires after the session. ...
mpfeifer_63884
Nimbostratus
Dec 04, 2009Thank you Aaron. OK, this kind of works. But still is not my favourite way to handle the whole thing.
Isn't there a way to already set the Cookie at the first Request already instead of waiting for the response?
I tried a few options:
when LB_SELECTED {
if {[IP::addr [LB::server addr] equals 10.1.110.105] } {
persist cookie insert Cookie_Test 18144000
}
}
What I am trying to do here:
When the member 10.1.110.105 gets selected to direct the traffic to, then set Cookie with expirydate.
But it doesn't set the expiry-date of the cookie, instead they get the normal default session-cookie
A similar idea was the following:
when HTTP_REQUEST {
if { [LB::status pool preview99 member 10.1.110.105 80] eq "up" } {
persist cookie insert Cookie_Test 18144000
}
}
If the specified member in pool preview99 is up, give the special expiry cookie.
But this gives the Cookie with exprydate to all members in the pool and not only to 10.1.110.105
Probably because for the LB it is only important if that member is up, regardless if he is going to use it or not.
I must be overseeing something.
Does someone have an idea?
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
