Bug ID 672828: Different ASM logging profiles can have cross-impact on response logging decision

Last Modified: Jul 12, 2023

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

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0

Opened: Jul 06, 2017

Severity: 3-Major

Symptoms

When attaching both local ASM logging profile and remote ASM logging profile to the same virtual server, response logging may not match configuration on logging profile for the remote logger.

Impact

Response is not logged for the remote profile although it is turned on in config.

Conditions

-- Have both ASM local logging profile and ASM remote logging profile attached to the same virtual server. -- Have response logging turned on for the remote profile, but disabled on the local.

Workaround

Enable response logging for local profile.

Fix Information

The system now makes separate response logging decisions between local and remote loggers.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips