Symptoms

After 200-ok following 100-continue, the BIG-IP system ICAP client sometimes stops sending ICAP request body to ICAP server, mid-stream (no ICAP termination).

Impact

Server stops receiving data so cannot complete its response. Transaction hangs and adaptation virtual server (with response-adapt profile) will eventually time out and perform its service-down action.

Conditions

ICAP preview-length >= ADAPT preview-size(lesser is used). Server responds with 100-continue after preview, and later with 200-ok.

Workaround

Increasing ADAPT preview-size to a few KB greater than ICAP preview-length might reduce the frequency of occurrence.

Fix Information

None

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips