Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6
Fixed In:
13.0.0
Opened: Apr 20, 2016 Severity: 3-Major Related Article:
K00432449
HTML_TAG_MATCHED might be raised for tags not configured in HTML profile rules. This issue only causes extra executions of iRule events and does not affect work of configured HTML tag-raise-event rules.
HTML_TAG_MATCHED might be executed with unexpected HTML::tag values. The event handler might fail if it does not verify tag and attribute values.
Erroneous extra match might happen in two situations: - When the last HTML tag in the current chunk of data (network packet) contains event handler attributes. - When the same tag in the current buffer has tag-remove and tag-raise-event HTML rules configured. The tag will be removed and HTML_TAG_MATCHED event will be raised for the last tag of current buffer instead.
HTML_TAG_MATCHED event handler should contain checks for tag and attribute values. This is a recommended style for writing iRules with HTML_TAG_MATCHED, and DevCentral examples are already written this way.
None