Forum Discussion
João_Assad_4295
Nimbostratus
Mar 22, 2006persistence cookie domain
When using the cookie persistence profile, there is no way to configure the cookie domain. Is there a way to do it via iRules ?
João_Assad_4295
Nimbostratus
Mar 22, 2006Ok here is the problem.
I have a virtual server configured using the default cookie persistent profile.
This virtual server responds to a number of hostnames:
www1.mydomain.com
www2.mydomain.com
www3.mydomain.com
the virtual server points all requests to a single pool.
so if a user go to www1.mydomain.com, the BigIP will add a cookie like this "BIGipServermy_pool=88888888.55555.4444" so next time this user sends a request it will be directed to the same node as before.
the thing is, this cookie doesnt have a domain set, so if I redirect the user to www2.mydomain.com, the BIGipServermy_pool cookie wont be sent since www2.mydomain.com is different than www1.mydomain.com. The BigIP then will select a new node for this user and create a new cookie.
I tried doing this:
when HTTP_RESPONSE {
HTTP::cookie domain BIGipServermy_pool mydomain.com
}
But I see it was completely ignored, the cookie is still set without a domain.
I am aware I can use the universal persistence profile to do the persistence based on the JSESSIONID cookie created by my application, which has the domain set. But Im only willing to do that as a last resort, because it is possible (very hard) that two different nodes have sessions with the same JSESSIONID.
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