Mentioned below, are the ICAP Status codes (as found in WebPrevent_Access log) and their description.
(1xx) Informational codes
Continue after ICAP preview
Ready to switch protocol to one requested by client
(2xx) Success codes
The request has succeeded. The information returned depends on the method.
Created. The new resource is created. The URI is specified in the body.
Accepted. The request was accepted but the processing has not being completed.
No modifications needed.
(4xx) Client error codes
ICAP Service not found.
Method not allowed for service (e.g., RESPMOD requested for service that supports only REQMOD)
Request timeout. ICAP server gave up waiting for a request from an ICAP client.
(5xx) Server error codes
Server error. Error on the ICAP server, such as "out of disk space"
Method not implemented. This response is illegal for an OPTIONS request since implementation of OPTIONS is mandatory.
Bad gateway. This is an ICAP proxy and proxying produced an error.
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.
ICAP version not supported by server
For more information on fields in webprevent_access.log, please refer to TECH219620..
Subscribing will provide email updates when this Article is updated. Login is required.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
This will clear the history and restart the chat.