Bug ID 680755: max-request enforcement no longer works outside of OneConnect

Last Modified: May 29, 2024

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

Known Affected Versions:
11.4.1, 11.5.4, 11.5.5, 11.5.6, 11.6.1, 11.6.2, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
14.0.0, 12.1.3.2, 11.6.3, 11.5.7

Opened: Aug 29, 2017

Severity: 3-Major

Related Article: K27015502

Symptoms

max-request enforcement does not work when OneConnect is not configured.

Impact

max-request enforcement does not work.

Conditions

-- The max-request enforcement option is configured. -- OneConnect is not configured.

Workaround

Always use OneConnect.

Fix Information

max-request enforcement now works when OneConnect is not configured.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips