Load Balancing based off TCP Payload entity

OK i ran a capture on the SSL/outside and see there are indeed 2 SSL connections made exactly 3 seconds apart and this is why we see the second message in the LTM logs relating to an empty persistence. the 2nd SSL connection sends a packet with payload but its not anything I am expecting. but its obvious this is impacting the Irule interaction.

I am assuming there is no way for irule to ignore the second SSL handshake ?

I am going to run another capture with the Irule removed to see what behavior occurs.

The inside/decrypted should only be 1 tcp session.