Last Modified: Nov 07, 2022
Affected Product:
See more info
BIG-IP LTM
Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 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, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4
Fixed In:
14.0.0.5, 13.1.1.4, 12.1.4.1
Opened: Aug 28, 2018
Severity: 2-Critical
When a 100 response a quickly followed by another HTTP response (2xx/4xx), the second response might be dropped.
The second response might be dropped, so the end user client might not receive all the HTTP responses coming from the server. Note: This does not happen all the time, and depends on how the underlying data packets are formed and delivered to the HTTP filter.
When a 100 response is quickly followed by another HTTP response (i.e., a 2xx/4xx response arrives within a few microseconds).
You can use either of the following workarounds: -- Use an iRule to disable the HTTP filter in the HTTP_REQUEST event. -- Disable LRO by running the following command: tmsh modify sys db tm.tcplargereceiveoffload value disable
None
