Bug ID 566565: ADAPT could time out during sending to IVS with no preview

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:

Opened: Jan 08, 2016

Severity: 4-Minor


If ADAPT is sending a very long HTTP request or response to an internal virtual server (IVS), its timeout might expire before sending is complete, not giving a chance for the IVS to respond. This might occur in this following case: the IVS has an ICAP profile and the ICAP server waits for the entire ICAP request before responding, by which time the ADAPT timeout has fired.


The IVS transaction fails and ADAPT performs its service-down action. In this no-preview case, an 'ignore' (bypass) action is not possible, so the HTTP transaction fails.


A request-adapt or response-adapt profile has preview-size 0 and a timeout short enough to expire before the IVS has a chance to respond.


Increase the timeout in the requestadapt or responseadapt profile, to cover the longest HTTP payload expected to be sent to the IVS.

Fix Information

The ADAPT timeout begins after the entire payload has been sent to the IVS, so IVS has the full allowed time to respond.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips