FastHTTP profile and TCP proxying

I'm getting stuck a bit on semantics and want to better understand SOL8024's description of the FastHTTP profile. Does this profile "proxy" the TCP connection or not?

 

My confusion stems from the table at the bottom of SOL8024 that notes the FastHTTP profile uses a "single TCP connection". In my mind this would mean the virtual server would pass through the TCP handshake rather than complete the handshake for the client side, then initiate the handshake on the server side.

 

Testing (BigIP-VE version 11.4.1) gives different behavior than what I would expect reading the SOL. A test VS using the fastHTTP profile completes the client side handshake, waits for the first client data packet, then establishes the server side TCP connection and passes data. In addition, the FastHTTP utilizes aspects of OneConnect which pools connections on the server side for subsequent use by other clients. Based on what I have seen the FastHTTP profile would use separate TCP connections and effectively proxy the TCP connection. I suppose it would not be a 'full proxy' as one cannot separately configure TCP options on the client and server side of the connection (as could be done using different TCP profiles with the HTTP profile, rather than the FastHTTP profile).

 

Appreciate input on this - whether I am misunderstanding the terminology or am correct and the SOL is referring to 'proxy' as full control of TCP options on both sides of the load balancer. Thanks! -Ed