Forum Discussion
Stefan_Klotz
Cumulonimbus
CumulonimbusChange default cookie insert name
Is there any possibility to change the default cookie name (BIGipServer) for a cookie insert persistence profile? We want to use a standard cookie insert profile across several virtual servers, but a...
Ben_Novak
Employee
EmployeeLooks like you can set the cookie name when creating a custom cookie profile.
The example below is running v15.1
Stefan_KlotzCumulonimbus
CumulonimbusBen_Novak yes I know this, but I'm looking for a generic cookie insert persistence profile, which I can use for several different VS, but where the cookie name will be generated dynamically based on the pool-name like for the default cookie profile. But I don't want to have the prefix "BIGipServer" included for security reasons.
Thank you!
- Ben_Novak
They you will probably need to configure that in a Local Traffic Policy or iRule.
However, having the cookie name change can be problematic for standardizing app/web server configs, or whatever is reading the cookie.
Since security is the driving factor here, I suggest having a standard/simple cookie name, but encoding all the details you want in the value of the cookie. Then you can encrypt/encode/secure all the details as needed.
- zamroni777
Nacreous
adding to Ben_Novak answer,
the traffic policy or irules will be:
on server response: insert your customized persistence header,
on client request: read the presistence header and select intended pool
