Universal persistence using header values for multiple client IPs.

Hell Kai,

Match across services will not work as the client is not the same and therefore the target pool member selection and resultant persistence entry will be completely independent.

I get your point about the server connecting effectively to itself, but I am told by the app team that there are various reasons why they need to reconnect back through the F5 one of which is the other intelligence the F5 provides through the proxypass configuration.

What I really need is this.

Client makes a connection to the F5, the F5 sets a persistence record to a pool member based upon XFF or another header I insert (maybe containing the selected pool member). Then when the server makes it's connection the F5 will see either the preserved XFF value (or the headre value for the selected pool member in the first connection) and will target the same IP.

I would prefer to use persistence records and lookups if possible as it makes it much easier to support an understand what is happening as the logic will be that the persistence table entry for a client informs the F5 where to send server connections for the same use session.

Many thanks