HTTPS traffic is being passed from behind a NAT router, through a load balancer, to servers without being decrypted. What is the F5-recommended persistence method in this situation?

SSL session ID persistence allows the BIG-IP to inspect the SSL session identifier present in the unencrypted SSL ClientHello and ServerHello handshake messages, routing the client to the same server without needing to decrypt the payload. This approach is reliable in NAT environments because each SSL session carries a unique identifier, unlike source IP addresses which may be shared by many clients behind a NAT device.

Source address persistence is unreliable behind a NAT router because multiple clients share the same external IP address, causing all clients from that network to be incorrectly directed to a single server.

SIP persistence is designed for Session Initiation Protocol traffic used in VoIP applications, not for HTTPS web traffic.

Destination address persistence routes traffic based on the destination IP address, which does not maintain client-to-server affinity across a pool of backend servers.