Bug ID 867257: CONNECT_RESET_ERROR is reported when Subroutine Timeout is reached for HTTP connections

Last Modified: Apr 17, 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

Fixed In:
16.0.0

Opened: Jan 08, 2020

Severity: 2-Critical

Symptoms

The system reports a CONNECT_RESET_ERROR when the Subroutine Timeout is reached for HTTP connections.

Impact

You cannot complete Per-Request Policy definition after a long period of inactivity.

Conditions

You do not proceed with a policy action within a subroutine until the subroutine timeout interval is reached.

Workaround

None.

Fix Information

You can now restart the Per-Request Policy Subroutine for a certain period after Subroutine Timeout is reached. The previous behavior was to reject requests for expired subroutine with CONNECTION_RESET_ERROR.

Behavior Change

You can now restart the Per-Request Policy Subroutine for a certain period after the subroutine timeout interval passes. The previous behavior was to reject requests when the expired Subroutine Timeout was reached for HTTP connections, at which point the system reported the CONNECTION_RESET_ERROR.

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips