"Caching" of iRule commands
we found out some strange behavior, that sometimes iRule-commands are not directly active.
For example, we have some logging in place to verify something, but when we disable it again and checking the logs with "tail -f" we still see the log-entries from that iRule.
Might this be related to TCP-connection bundling from Akamai, which is in front of the BIG-IP? And the new iRule code will only match for new TCP-connection?
If that's the case, how can this behavior be broken/corrected? Because in case of troubleshooting or fine tuning for specific commands, the BIG-IP doesn't use the latest iRule changes.
fyi: we are already using a Oneconnect profile with a /32 mask.
Ciao Stefan :)