Bug ID 578564: ICAP: Client RST when HTTP::respond in HTTP_RESPONSE_RELEASE after ICAP REQMOD returned HTTP response

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 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, 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

Fixed In:
13.0.0, 12.1.2, 11.6.1 HF1

Opened: Mar 08, 2016

Severity: 3-Major

Symptoms

Connection aborted with RST "ADAPT unexpected state transition (old_state 22 event 7)"

Impact

HTTP::respond cannot be used to modify an HTTP response returned by an ICAP server that is modifying an HTTP request.

Conditions

An HTTP virtual has a request-adapt profile. The ICAP server returns an HTTP response for REQMOD. An iRule executes HTTP::respond in the HTTP_RESPONSE_RELEASE event.

Workaround

None

Fix Information

HTTP::respond works as expected even on an HTTP response returned by an ICAP server after request adaption.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips