Loading...
Loading...
If an iRule changes the SNI then the wrong session ID will be retrieved (using the original SNI).
Connection may be rejected by the client if checking at the client occurs (Apache commonly does this). If the client finds that the SNI does not match the SNI in the session information, the connection may be rejected.
Occurs when SNI is being modified by an iRule to an SNI that is different from the one specified in the server SSL profile.
Disable SSL session cache. This has the side effect of reducing performance.
None
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.