Load Balancing based off TCP Payload entity

A few thoughts:

1. It looks like the iRule should work as it is. Are you seeing different or just questioning if it could fail?

2. Unless you're specifically doing mblb, I don't think you need the TCP::notify. TCP load balancing is by default session-based, so all traffic within a single TCP session will stick to the same node after an initial decision. I threw in some additional logging to show what the persistence record actually points to per TCP session.

   when CLIENT_ACCEPTED {
       TCP::collect
   }
   when CLIENT_DATA {
       set entityID [findstr [TCP::payload] "User-Agent: " 12 " "]
       log local0. "entityID = $entityID"
   
       persist uie $entityID
       log local0. "using persistence for entityId ($entityID): [persist lookup uie $entityID]"
   
       TCP::release
   }