SSL Heartbleed iRule update
Get the latest updates on how F5 mitigates HeartbleedGet the latest updates on how F5 mitigates Heartbleed
For those of you tuning in to learn more about the OpenSSL Heartbleed vulnerability, here ...
Updated Mar 18, 2022
Version 2.0
Hi Sam.
 
 
If you already have an SSL profile, I suspect that it would be more efficient to use either CLIENTSSL_DATA or SERVERSSL_DATA events to find the heartbeats.
 
https://clouddocs.f5.com/api/irules/CLIENTSSL_DATA.html 
 
As for the @${i} warning, we haven't seen it despite having passed hundreds of gigabytes of traffic from curl. It is likely non-TLS traffic, or possibly an aborted client.