Bug ID 734797: URL suggestion is still explicit though it should be *.[Jj][Ss]

Last Modified: Jun 10, 2021

Bug Tracker

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

Known Affected Versions:
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, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 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, 14.1.4.2, 14.1.4.3

Fixed In:
15.0.0

Opened: Jul 16, 2018
Severity: 3-Major

Symptoms

Unexpected URL suggestion populated for explicit URL even though URL's Filetype is defined in list: 'File types for which wildcard HTTP URLs will be configured (e.g. *.jpg)'.

Impact

Unexpected URL suggestion populated for explicit URL when it should not.

Conditions

Adding a Filetype to the 'File types for which wildcard HTTP URLs will be configured (e.g. *.jpg)' list after first traffic for specific URL with that Filetype arrived (problem persists even if suggestions is deleted).

Workaround

- Ignore the suggestion (use the ignore button). - Restart policy builder (run the command pabnagd).

Fix Information

When adding a new Filetype to the 'File types for which wildcard HTTP URLs will be configured (e.g. *.jpg)' list, once the first traffic for an explicit URL with a suggestion arrives, the explicit URL suggestion will be deleted and a wildcard URL suggestion for matching Filetype will be created.

Behavior Change