> Pound already does this. Once a connection is established, that connection > can be bound using the session configuration:
> Session > Type IP > TTL xxx > End > That will keep the IP address of the client bound to the same BE. I know > this works because I use it and would not be able to have my applications > work if it didn't work. Sorry - after reading my previous post, I realize I wasn't too clear in my question. I understand that pound session tracking can be used a number of different ways, and we use those other methods (IP, Cookie) in production environments today. What I am looking for is a way for pound to do two things: 1. Identify which backend to send the request to by looking at a custom header "X-Notes". (The only way I know of doing this is using "HeadRequire". 2. Send subsequent requests for the same client back to that backend. The problem is that my backends cannot continuously add the header - they can only do it once. This is being done by a login page that does a lookup on the userid and sets the header accordingly. Once the user is at a backend, they don't get the header set any more. Once the users are in a session with the backend, the HeadRequire will always fail because the header isn't being sent. So the rule that allows them in for the first request is the same rule that assures they won't get back in if they don't have the header set. Thanks, Justin -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
