Forum Discussion
source address persistence maximum session timeout
- Jul 03, 2023
williamcs The following are the answers to your questions.
1. Based on F5 documentation the value can be within range 1 and 2,147,483,647.
2. The only real downside I see to increasing the timeout value higher than the default is if you have a high connection virtual server you could theoretically reach a very large persistence table which would cause performance degredation.
1. you can set it to 'undefinite' and the persistence entry will not time out (I'm not aware of any use case of this)
2. No but.. There is no impact because 180s is often unsufficient and we often set it to 30mn to 12 hours or more, but theoretically if you have a huge number of users, the persistence table will get extremely large and this is bad for performance. In this case, you can use cookie persistence or if you have to use source persistence you can specify a shorter prefix length
Hi Amine_Kadimi ,
Yes, I'm thinking to change to either SSL or cookie persistence. Which would be recommended if the vs is mainly for https web browser?
- Amine_KadimiJul 03, 2023MVP
SSL persistence uses persitence table too, but cookie persistence does not. The latter works in majority of the cases but in some few cases it doesn't work as expected. If your app is 100% browser based then it should work without problem (supposing you are using a clientssl profile).
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