Universal persistence using header values for multiple client IPs.

Hi ajohnson,

This is not the case, the only requirements are that the target pool member both be the same for the two separate connections from the client and the server. At present this is how the application has to work, but of course standard load balancing must distribute load.

This means in effectively, that if a client connects initially to NodeA (via Random selection), the NodeA will then always connect its backend connection to itself. Thats why I'm asking if this connection really needs to pass your F5 and I've proposed a solution (see at the very buttom of this page) which doesn't require any

[persist]

I am now looking at adding a new header to the clients initial request to the server (containing the target node IP), then when the server request arrives with this header value use it to target the required node, but I would prefer to use universal persistence (persist lookup perhaps) if possible.

Okay... will write you an

[persist]

Match Across Service

Cheers, Kai