Mentioned below, are the ICAP Status codes (as found in WebPrevent_Access log) and their description.
Status Code |
Meaning |
(1xx) Informational codes |
|
100 |
Continue after ICAP preview |
101 |
Ready to switch protocol to one requested by client |
(2xx) Success codes |
|
200 |
The request has succeeded. The information returned depends on the method. |
201 |
Created. The new resource is created. The URI is specified in the body. |
202 |
Accepted. The request was accepted but the processing has not being completed. |
204 |
No modifications needed. |
(4xx) Client error codes |
|
400 |
Bad request |
404 |
ICAP Service not found. |
405 |
Method not allowed for service (e.g., RESPMOD requested for service that supports only REQMOD) |
408 |
Request timeout. ICAP server gave up waiting for a request from an ICAP client. |
(5xx) Server error codes |
|
500 |
Server error. Error on the ICAP server, such as "out of disk space" |
501 |
Method not implemented. This response is illegal for an OPTIONS request since implementation of OPTIONS is mandatory. |
502 |
Bad gateway. This is an ICAP proxy and proxying produced an error. |
503 |
Service overloaded. The ICAP server has exceeded a maximum connection limit associated with this service; the ICAP client should not exceed this limit in the future. |
505 |
ICAP version not supported by server |
For more information on fields in webprevent_access.log, please refer to TECH219620..