Hello,
I just wanted to check the feasibility of implementing the below scenario using iRules/any other options provided by the tool.
The usual way of implementing sticky sessions is through cookie persistence where a client once associated with a node is automatically redirected to the same node based on the cookie that’s set on the first request. Our requirement is to have sticky sessions but the stickiness is required at a level that’s based on application key/logic. As an example, let’s say, an application works with ‘n’ objects. Although an initial request for an object can be handled by any of the servers, if a request for say object ‘x’ hits a server m, all future requests for object ‘x’ by any user (or from any machine) should hit server ‘m’ only. So, in this sense, the stickiness is to the object (or object ID) rather than client machine/browser. As application developers, we can embed the object ID or any other identification in the HTTP headers/request and even though I can extract the object Id from the request data via iRules, as long as I don’t have the ability to store earlier mapping data/table I won’t be able to solve this affinity problem. At least, I think so.
Do we have a way to solve this problem? Please let me know.
Thanks in advance.
-Chaitanya