Forum Discussion
Hi,
First please indicate if user was logout of the application ? you have to distinguish the difference between session and connection.
A session is a collection (a superset) of connections. A connection only tells you very basic things (layer 3-4 information) about a single TCP/UDP connection.
A session correlates what happens over several individual connections (Application session for example with session cookie...).
You indicate that applying your irule disconnect user, it's not possible unless you put a condition in your irule that disconnects the user and he has met this condition...
moreover, to apply an Irule does not impact the sessions.
keep me in touch if you need more details.
regards,
- ccraddockSep 20, 2019Cirrus
Youssef,
Thanks for the response. All I know is that around the time of editing the iRule, the user stated that they were logged into the portal conducting work and then suddenly got booted back to the login screen (losing all their work). I had assumed at the time that editing the iRule was the cause, but I wasn't 100% sure of that was the cause.
- jaikumar_f5Sep 23, 2019MVP
Can you also tell what logical change you modified in your irule.
Making any object level or configuration level change impacts or gets applied to the new connections only. The older connections does not take these new changes unless they timeout and establish a new connection. In other words, existing connections behave to the old irule and the new connections behave to the new irule.
Refer this article to know the behavior of changes.
- youssef1Sep 23, 2019Cumulonimbus
I think it's just a game of circumstance.
let's take the example of a form, if the user takes time to finalize and push his form (application timeout).
he will lose all his work because he loses his context (session)...
I think it could only be normal behavior related to the user session.