Bug ID 667414: JSON learning of parameters in WebSocket context is not working

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, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1

Fixed In:
14.0.0

Opened: Jun 01, 2017

Severity: 3-Major

Symptoms

When a JSON parameter arrives in WebSocket, it is not sent to policy builder, and thus is not learned.

Impact

JSON parameter arriving in WebSocket is not learned.

Conditions

1. WebSocket traffic contains JSON data. 2. In the JSON profile, parse parameter is enabled.

Workaround

None.

Fix Information

The system now correctly reports a JSON parameter that arrives in WebSocket to the policy builder, so it is learned.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips