OneConnect & Multiple Request in the Same TCP Connection

OK, what oneconnect does it reuses the tcp session on the server side. Assume next situation. There is no connection to the server side yet. You are pipelining 5 concurrent http requests in one tcp connection. At this stage LB will be made based on HTTP requests, not TCP connection. The 1st request will go to pool 1, 2d to pool 3 etc.

Back-end servers replied for all the requests. Big-ip drops the connection on the client side, but keeps connection opened on the server side.

Now the 2d butch is arriving. Big-ip will not create new TCP connection, it will reuses existing, opened connection on the server side and will send HTTP request via the existing tcp connection, so reducing the time for establishing new TCP session.

Requirements for oneconnect - your back-end servers must support http piplining and keep-alive