Bug ID 555229: Transactional PEM policies without an HTTP profile on the virtual server do not result in transactional classification.

Last Modified: Nov 07, 2022

Affected Product(s):
BIG-IP PEM(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,

Opened: Oct 30, 2015

Severity: 4-Minor


Transactional HTTP flows will be classified only on the first transaction.


PEM actions that differ between transactions for a flow will not take effect. Instead, the flow adheres to the PEM actions against the first transaction.


Virtual server with a PEM profile, classification profile, no HTTP profile, and transactional PEM policy.


Add an HTTP profile to the virtual server if transactional flows need to be evaluated for each transaction.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips