Bug ID 1058665: Bot signature with a semicolon followed by a space is not detected.

Last Modified: Jan 25, 2022

Bug Tracker

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

Opened: Nov 01, 2021
Severity: 4-Minor

Symptoms

When creating a user-defined Bot Signature, semicolon followed by space cannot be used.

Impact

The signature is not detected.

Conditions

-- Using a user-defined Bot Signature in Simple mode. -- There is a semicolon followed by a space in the User-Agent or URL sections.

Workaround

Escaping the semicolon in the signature created as "|3B|".

Fix Information

None

Behavior Change