Bug ID 1634669: The CATEGORY::lookup iRule command prioritizes default categories over custom categories.

Last Modified: Dec 18, 2024

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

Known Affected Versions:
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, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2

Opened: Aug 28, 2024

Severity: 4-Minor

Symptoms

While executing the CATEGORY::lookup iRule command, the default categories will be first included in the resulting array before any custom categories. If the URL does not match any default categories, the first result will be UNCATEGORIZED.

Impact

The iRule prioritizes default categories which may be unexpected, especially if the iRule only looks at the first (primary) category returned.

Conditions

Use the CATEGORY::lookup iRule command with request_default_and_custom and custom categories are in use.

Workaround

None

Fix Information

None

Behavior Change

'CATEGORY::lookup' will return the same set of results, but custom categories (including recategorization of default categories) will be returned before default categories.

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips