Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP ASM
Known Affected Versions:
12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6
Fixed In:
14.1.0
Opened: May 01, 2018 Severity: 4-Minor
ASM provides no visibility regarding which requests are considered long, as well as the frequency of such requests, in order to better determine the long_request_buffer_size and max_concurrent_long_requests internal parameters.
You are unable to determine the long_request_buffer_size and max_concurrent_long_requests internal parameters.
Arrival of long requests.
N/A
A new logging module: "LONG_REQUEST" was added in order to log these long requests. Two log entries were added: 1. DEBUG - Printed once every long request. 2. NOTICE - Printed together with UMU stats (every 15 seconds or so), when the total number of concurrent long requests has changed. For example: LONG_REQUEST|DEBUG |Sep 07 11:42:55.776|21996|io_plugin.c:9596|Long request for account id 1, url /index.php, buffer size 10000000, content-length :200000, content-type: application/x-www-form-urlencoded, number of concurrent long requests: 1, maximum number of concurrent long requests allowed: 111, beginning of payload: 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222 LONG_REQUEST|NOTICE|Sep 07 11:43:03.296|22010|temp_func.c:4164|Total allocated long request buffers: 1, Total memory used by long request buffers: 10000000 bytes