Last Modified: Jun 28, 2019
See more info
Known Affected Versions:
Opened: Nov 24, 2018
Under certain circumstances tmm can reorder or omit HTTP data segments when they are received while processing an iRule which is parked.
Data corruption or loss can occur.
- HTTP iRule execution suspended, e.g., waiting for a table command to return. - Ingress data is processed during this state.
There is no workaround other than not using iRule suspend commands in HTTP_* events.
tmm now handles ingress data correctly when in the parked iRule state.