How OneConnect Profile works with Cookie Persistence

Thanks for sharing with the capture. But the question is why F5 ignores the persistence record for multiple HTTP request in single TCP connection. so does it mean, F5 records the source address perist to server internally somewhre when there is a single TCP connection although if cookie is present? or it may be the behaviour of F5.  In that case oneconnect provide benefits of having the connection to be opened to server and make it re-use and as well looking at l7 http request for cookie to make load balancing decision or to send traffic to persisted connection.