Last Modified: Nov 07, 2022
Affected Product:
See more info
BIG-IP LTM, PEM
Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 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.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 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: Sep 15, 2015
Severity: 4-Minor
An ICAP status code from the ICAP server of any 2xx response other than 200 or 204, is treated as an error, causing a reset of the ICAP connection and the service-down-action to be performed on the parent virtual server (as configured in the requestadapt or responseadapt profile). The RFC 3507 requires the ICAP client (the BIG-IP server) to handle the response normally (i.e., like it handles 200).
Transactions involving an ICAP server that returns a non-ICAP 2xx response do not work, and the service-down action is performed.
The ICAP server returns a 2xx status code that is not defined explicitly for ICAP.
If possible, have the ICAP server return status code 200.
An ICAP status code from the ICAP server of any 2xx response other than 200 or 204, is treated as a normal 200 status code; thus the encapsulated HTTP request or response is returned to the HTTP client or server.
