OneConnect & Multiple Request in the Same TCP Connection

So, it is going to be in the next way. HTTP pipeline of 5 requests comes in. Big-ip checks for persistence. No persistence check for the opened connection with the next pool member according LB algorithm. If there is opened connection, then re-use it for the 1st http request. Second HTTP request comes in using the same TCP connection on the client side. Now, LB algorithm takes HTTP request into account (not tcp connection). Checks for the next pool member according LB. If there is an opened tcp connection, reuse it, no connection - open a new one.

This is true until you apply persistence profile. In case of persistence all the requests from the same client will go to the same pool member.

Oneconnect marge http request from different client on the same tcp connection on the server side. In the packet capture in one tcp flow you can see multiple http requests and replies designed for several clients. This is why your servers need support HTTP pipeline to merge http requests into one tcp connection and http keep-alive to keep the server side connection opened.