Forum Discussion
question about Irule.
Dear.
I have a problem. I have the following configuration:
-> I have a application with this Irule, and a persistence (Cockie).
ltm rule /Common/IER_CACHE { when HTTP_REQUEST { if {[HTTP::uri] contains ".css"} { set foundmatch 1 } if {[HTTP::uri] contains ".do"} { set foundmatch 1 } else { set foundmatch 0 } } when HTTP_RESPONSE { if {$foundmatch == 1} { HTTP::header replace Cache-Control no-cache HTTP::header replace Pragma no-cache } }
}
The problem is that sometimes when the users was login the balanced application; appear the sesion of other user and not the user that was logged.
Some times I see the error the sesion is duplicate. and only, one user is in the application.
What happen? the irule has some problem or is the persistence?
What is your recommendation?
4 Replies
- vita_139467
Nimbostratus
ltm rule /Common/IER_CACHE { when HTTP_REQUEST { if {[HTTP::uri] contains ".css"} { set foundmatch 1 } if {[HTTP::uri] contains ".do"} { set foundmatch 1 } else { set foundmatch 0 } } when HTTP_RESPONSE { if {$foundmatch == 1} { HTTP::header replace Cache-Control no-cache HTTP::header replace Pragma no-cache } } } - Kevin_Stewart
Employee
I'd venture that this iRule has probably nothing to do with the session jumping. Can you elaborate on how you have cookie persistence and the VIP configured?
- vita_139467
Nimbostratus
Dear
The cookie persistence is insert and it is the sesión coockie actívate. Can to be this the problema? Upload the picture. Please help me. I need to know why when my user login with the user appear other sesión ( user in the sesión) and not the sesión of the user that login in this moment.
- Kevin_Stewart
Employee
Cookie persistence is really just there to get the client to the same server throughout his session, and really has nothing to do with application session state. If for example you had no persistence, or persistence failed, and the LTM sent the user to the wrong server, the worst that should happen is that the user session blows up. I'm assuming that your application builds its own session with the client, presumably with a cookie. And so in order for you to experience a session jumping event, two clients would have to have the same application session cookie. Can you:
-
Replicate this event, and if so
-
Examine the application session cookies that are being used by each client - in other words, the application will send a session cookie to the client and the client will send this cookie back in each request. Is that cookie unique to a single client?
-
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