Last Modified: Jul 24, 2020
See more info
Known Affected Versions:
15.1.0, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206
Opened: Jan 08, 2020
The system reports a CONNECT_RESET_ERROR when the Subroutine Timeout is reached for HTTP connections.
You cannot complete Per-Request Policy definition after a long period of inactivity.
You do not proceed with a policy action within a subroutine until the subroutine timeout interval is reached.
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.
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.