Forum Discussion
bruno_thomas_12
Nimbostratus
Nimbostratuspersistence cookie at BIG IP level too persistent?
When a cookie is created at the bIG IP level it seems that the user is stuck on the same server for his session (which is a requirement of our solution) but should that server fail during the session, user gets Pages cannot be display..(probably because of the cookie)
Is there a way (like health monitor) to determine that the node is down AND the session would be clenaly failed over the other server?
12 Replies
bruno_thomas_12I could not resist to ask that last question:
when you say:
keep the authentication information so that it could re-insert it to the new server
ok for authentication info BUT:
what about re insert session (environment,what page etc..) information to the other server.- In 9.2 you'll be able to re-play the entire request (and even modify it) to another server if the first server fails (either due to no connection or because it gives a bad response).
Currently you can save off specific information from one request and then modify a subsequent request to contain some of the original request. This is what I was implying you could do with the Authenitication information.
