Bug ID 538784: ICAP implementation incorrect when HTTP request or response is missing a payload

Last Modified: Apr 28, 2025

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

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 12.0.0, 12.0.0 HF1, 12.0.0 HF2

Fixed In:
12.1.0, 12.0.0 HF3, 11.6.1

Opened: Aug 08, 2015

Severity: 3-Major

Related Article: K91532102

Symptoms

The ICAP request sent to the ICAP server always contains a payload even if the HTTP request or response to be modified does not contain one.

Impact

If an HTTP request or response to be modified does not contain a payload, the ICAP client sends a zero-byte HTTP payload instead.

Conditions

HTTP request or response does not contain a payload.

Workaround

None.

Fix Information

The system now correctly identifies an empty HTTP payload and sends the appropriate ICAP header, identifying that there is no HTTP payload included.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips