Bug ID 753482: Proxy initialization fails/port denied when excessively large max header size is set in the HTTP/1 profile

Last Modified: Jan 20, 2023

Bug Tracker

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

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4

Opened: Dec 18, 2018
Severity: 3-Major

Symptoms

If the configuration has an excessively large 'Maximum Header Size' value in the HTTP/1 profile on a virtual server that also has HTTP/2, initialization fails. The tmm log file contains messages similar to the following: notice Proxy initialization failed for /Common/https_virtual1. Defaulting to DENY. The ltm log file contains messages that indicate that the virtual server is not accepting traffic.

Impact

-- As a result, the initialization fails. -- Browsing via the virtual server does not work.

Conditions

-- Large max_header_size (e.g., 4294967295) is configured in HTTP profile. -- The system does not have enough free memory.

Workaround

To prevent this issue from occurring, if a virtual server has an HTTP/2 profile on it, the max_header_size value inside the HTTP profile should be between 0 and 131072.

Fix Information

None

Behavior Change

If Virtual Server has HTTP2 profile on it, the max_header_size value inside HTTP profile should be between 0 and 131072.