Forum Discussion
NimbostratusSingle Source IP - Ideal Persistence Method?
If I have HTTP traffic sourcing from a single IP address, what is the ideal method for session persistence? Ideally, I'd like each new connection from this single source to persist to a different server in the pool. What are my options?
Cookie persistence - I don't want to use cookies on this particular connection.
Destination address affinity persistence - No benefit here.
Microsoft® Remote Desktop Protocol persistence - Not applicable
SIP persistence - Not applicable
Source address affinity persistence - No benefit here.
SSL persistence - Not a fan of SSL persistence due to renegotiation.
Admittedly, I do not know enough about Hash or Universal persistence iRule configuration methods. Would these be applicable?
1 Reply
Max_Q_factorCirrocumulus
If you can find something unique about each "session" that requires persistence, then you can use the universal persistence function.
SOL7392: Overview of universal persistence
the example that everyone likes to use is to latch on to the JSESSION cookie id value. You need to have a way to distinguish what makes a session with your application. Weather it be encoded in a url ( ), another HTTP header from something like Akamai's True Client IP http header or something that the universal inspection engine can use as a session.
