Forum Discussion
Hash Persistence and its different types & SSL persistence
SSL Persistence: Persistence based on SSL Session ID. You can use this if you are not terminating the SSL certificate on the F5.
Hash Persistence: This is similar to UIE persistence. Basically, you can create an hash based on any "key" that is available in the incoming packet and persist based on that "key".
Cookie Persistence: Persistence based on cookie that is stored in the client. This can be the following types:
- "Cookie Insert" - where the F5 inserts its cookie.
- "Cookie Hash" - Application inserts this cookie and F5 creates an hash of this cookie to persist.
- "Cookie Rewrite" - Server needs to create the cookie name. The cookie value will be inserted by F5 based on the pool and member selected.
- "Cookie Passive" - Server inserts this cookie and F5 can use the application cookie to persist.
For cookie persistence, either 1 or 2 should solve your use-case. I don't recommend 3 or 4.
See reference link.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* 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