Bug ID 1497369: HTTP::respond will not always be executed when rate limit on all pool members is reached.

Last Modified: Dec 31, 2024

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

Fixed In:
17.1.2

Opened: Jan 30, 2024

Severity: 3-Major

Symptoms

HTTP::respond will not always be executed when the rate limit on all pool member is reached.

Impact

LB_FAILED not executed when all pool member rate limit have been reached.

Conditions

When the rate limit is reached on all pool members, LB_FAILED does not get called. If any HTTP::respond is in that rule to generate a redirect, it will not be invoked.

Workaround

If only a 302 redirect is what is needed, then configure a fallback-host in the ltm-profile. The iRule event is triggered when a fallback host exists. If a 301 redirect is needed, then there are no workaround.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips