Bug ID 524107: When editing an iRule with regular expressions (regex), an incorrect warning is thrown out to LTM log.

Last Modified: Mar 21, 2019

Bug Tracker

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

Known Affected Versions:
11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Fixed In:
12.1.0

Opened: May 19, 2015
Severity: 4-Minor
Related AskF5 Article:
K59415918

Symptoms

When trying to use special regex metacharacters (for example, \s for whitespaces, \d for digits, and so on), the system posts a warning to the LTM logs, suggesting a change to the syntax, however, making the change as suggested prevents the correct iRule behavior.

Impact

System logs a warning that recommends an incorrect resolution. If you make the change as recommended, the iRule behavior does not work correctly. The error messages appears similar to the following: warning mcpd[8501]: 01071859:4: Warning generated : /Common/test_regex:4: warning: ["\d" has no meaning. Did you mean "\\d" or "d"?][{number=(\d+)}].

Conditions

Writing an iRule that uses metacharacters in a regular expression.

Workaround

Ignore the LTM log warning. Use the regex metacharacters without modification.

Fix Information

When editing an iRule with regular expressions (regex), you can use the regex metacharacters without modification, and the system does not recommend an incorrect resolution.

Behavior Change