Bug ID 922261: WebSocket server messages are logged even it is not configured

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP ASM(all modules)

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1

Fixed In:
16.1.0, 16.0.1.2, 15.1.4, 14.1.4.2

Opened: Jun 30, 2020
Severity: 3-Major

Symptoms

BIG-IP systems send unexpected WebSocket server messages to the remote logging server.

Impact

Remote logging server overloaded with unexpected WebSocket messages.

Conditions

-- ASM provisioned. -- ASM policy and WebSocket profile attached to a virtual server. -- More than one remote logging profile is attached to a virtual server. -- One of the remote loggers has response-logging=all.

Workaround

Set response-logging=illegal in all remote logging profiles.

Fix Information

BIG-IP sends WebSocket server messages to a remote logger only when it is enabled in the logging profile.

Behavior Change