Forum Discussion
Help with URI string-based session persistence
- Jun 11, 2015
If this happens the LB just sends the request to the same node that the TCP session is tied to - but the iRule still logs as seeing the new strID value. I was confused and expected this to create a new persistence record and load balance the request, but something tells me I would need more logic in my iRule to detach the connection and re-load balance it with a new persistence record.
you can use oneconnect profile. it will do that for you.
Hi Nitass
Thank you for your input!
I did originally have a similar iRule setup to yours but what does your show persistence persist-records output when you change the string?
Ie. I would go to:
/some_uri?strID=Asb20322232343&strTimeLimitInSecs=180&request=submit
then, I would change the string and I would try going to
/some_uri?strID=Asb20321&strTimeLimitInSecs=180&request=submit
The output below shows that a persist record is formed on the first request, but the second does not show up. I'm not sure why it doesn't create a new persist record that is re-load balanced? Does it matter if the source IP or browser session is the same?
tm@(test)(cfg-sync Standalone)(Active)(/TEST)(tmos) show ltm persistence persist-records
Sys::Persistent Connections
universal Asb20322232343 10.64.114.155:80 10.64.115.151:80 (tmm: 0)
I hope I'm explaining that clearly.... I think maybe I'm misunderstanding how universal persistence is supposed to work.
Thank you!
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