Thanks, Kees!
But I just found this article:
https://support.f5.com/csp/article/K7964
and it claims that this happens only when both HTTP profile and OneConnect profile are applied:
If no OneConnect profile is associated with the virtual server, the BIG-IP system selects a pool member once, when the client-side connection is first established. After a pool member is selected, and the TCP connection is load balanced, all subsequent requests on the same Keep-Alive connection are sent to the same pool member.
For example, if a OneConnect profile is not associated with the virtual server, and the client request is initially sent to node A in pool A, the BIG-IP system inserts a cookie for node A. Then, the BIG-IP system receives a subsequent request within the same TCP connection that contains a cookie for node B in pool B. The BIG-IP system sends the request to node A.
Is this true, in your experience?
Thanks,
Mucius.