Check Point R80.20 - Page 73

ICAP Client
Next Generation Security Gateway Guide R80.20 | 73
Additional HTTP response X-Headers
You can add additional HTTP response X-Headers for the ICAP Client to recognize:
HTTP Response X-Header
Description
Examples
X-Response-Info
Contains a one word
description of the action the
ICAP Server applied on the
HTTP request.
This header is available in all
responses sent by the ICAP
Server.
X-Response-Info: Allowed
X-Response-Info: Blocked
X-Response-Info: Options
X-Response-Desc
Contains a one line description
about the action that the ICAP
Server applied on the content.
This header is available in all
"blocked" responses.
In case of the content was
scanned, and some violations
were found, the returned string
is equivalent to
X-Blocked-Reason
's value.
X-Response-Desc: Infected
X-Response-Desc: Encrypted
Archive
X-Include
Contains the list of requested
HTTP headers, which the ICAP
Client should add to the HTTP
requests, if the information is
available.
This header is present only in
HTTP Options responses.
This header is a
comma-separated list of any
ICAP header extension field
names that the ICAP Server
wants the ICAP Client to add to
the requests, if the information
is available and the header is
supported.
X-Include: X-Client-IP
X-Blocked-Reason
Metadefender specific custom
header. Contains the blocking
reason of the content.
This header is available only if
the content was scanned, and
some violations were found.
X-Blocked-Reason: Infected
X-ICAP-Profile
Contains the applied
workflow's name (user profile).
This header is available only if
the file was scanned.
X-ICAP-Profile: Proxy