HTTP 302 redirect

I run an application that is extremely sensitive to persistence on a farm of 20+ web servers.

You will want to enable a suitable client-to-F5 persistence, I set the pool for cookie persistence but overwrite it with UIE in an iRule. (My clients are embedded systems and the old ones don't honor cookies, so I use SSL credentials and an in-memory table, but that's another story).

I've found that oneConnect is critical to maintaining the F5 to web server persistence for client traffic, if oneConnect is removed I have seen traffic bounce across web servers.

If I recall correctly there was a less-than-documented feature in 10.x where a oneConnect profile shared across more than one VIP resulted in some confusion when distinct traffic from the same source IP hit different VIPs. To fix this, I have a unique oneConnect profile for each VIP. Each profile also specifies the subnet mask 255.255.255.255 .

Finally, round-robin is (in my experience) not very round. Use Least connections (member) with a priority group (greater than 1).

As for the source of your 302's, wireshark or clonepool dump your traffic. That's a server problem. :-)