Bug ID 425974: max_requests wasn't respected when iRule-generated responses are used to exceed the limit

Last Modified: Feb 13, 2019

Bug Tracker

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

Known Affected Versions:
11.3.0, 11.4.0

Fixed In:
11.5.0

Opened: Jul 23, 2013
Severity: 3-Major
Related AskF5 Article:
K14701

Symptoms

If many iRule-generated HTTP responses are created, then max_requests can be exceeded. The connection to the server can then last longer than the intended number of requests. In extreme cases, this may lead to out of memory situations.

Impact

Overlong connections. Overlarge memory usage in the TMM

Conditions

max_requests is set, and HTTP::redirect or HTTP::respond are used for all requests after the max_requests limit is reached.

Workaround

In the iRule, keep track of how many redirects or responses you make. Above a certain number, close the connection.

Fix Information

HTTP::respond and HTTP::redirect respect the max_requests limit, closing the connection to the server when it is reached.

Behavior Change