Bug ID 741919: HTTP response may be dropped following a 100 continue message.

Last Modified: Nov 07, 2022

Bug Tracker

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

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.4, 13.1.0,,,,,,,,, 13.1.1,,, 14.0.0,,,,

Fixed In:,,

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

Fix Information


Behavior Change