Loadbalance Web server

If I may add, if I understand you correctly, you want the pool member selection to be "in-sticky", so that when you make multiple requests, you flip back and forth between the members. Is that correct? If so, there are a few considerations:

1. Understand that load balancing is generally a layer 4 mechanism. You can affect a load balancing decision at different levels, but once a member is selected that selection will, regardless of load balancing method, persist for the life of that TCP session. If you open a browser, get a particular pool member, and then refresh repeatedly and quickly, you will most likely keep that single TCP session alive and continue to persist to the same member. If you pause long enough to let the TCP session expire, and HTTP isn't setting a Keep-Alive in the browser, then a subsequent request will probably re-load balance to the next member. Enabling a OneConnect profile on the VIP can help, or using an iRule to force the TCP session to close with a "Connection: Close" header in the HTTP responses.

    

2. If you watch the HTTP communications between the client and VIP, you may see cache control headers in either the requests or responses. Sometimes, regardless of client side cache settings, a browser will still send out an If-Modified-Since header, and the server might respond with a 304. This would be especially important if the images on both pool members had the same name.