ICAP Interface Support
▀ Configuring ICAP Interface Support
▄ Cisco ASR 5x00 Packet Data Network Gateway Administration Guide
380
Configuring ICAP Server and Other Parameters
Use the following example to configure the active content filtering (ICAP server) and other related parameters:
configure
context
<icap_context_name>
content-filtering server-group
<icap_server_grp_name>
icap server
<ip_address>
[ port
<port_number>
] [ max
<max_msgs>
] [ priority
<priority>
]
deny-message
<msg_string>
response-timeout
<timeout>
connection retry-timeout
<retry_timeout>
failure-action { allow | content-insertion
<content_string>
| discard |
redirect-url
<url>
| terminate-flow }
dictionary { custom1 | custom2 | standard }
end
Notes:
In 8.1 and later releases, a maximum of five ICAP servers can be configured per Content Filtering Server Group.
In release 8.0, only one ICAP Server can be configured per Content Filtering Server Group.
The maximum outstanding request per ICAP connection configured using the optional
max
<max_msgs>
keyword is limited to one. Therefore, any other value configured using the
max
keyword will be ignored.
Optional
. To configure the ICAP URL extraction behavior, in the Content Filtering Server Group configuration
mode, enter the following command:
url-extraction { after-parsing | raw }
By default, percent-encoded hex characters in URLs sent from the ACF client to the ICAP server will be
converted to corresponding ASCII characters and sent.
Configuring ECS Rulebase for ICAP Server Group
Use the following example to configure the content filtering mode to ICAP server mode in the ECS rulebase for content
filtering:
configure
require active-charging [ optimized-mode ]
active-charging service
<acs_svc_name>
[ -noconfirm ]
rulebase
<rulebase_name>
[ -noconfirm ]
content-filtering mode server-group
<cf_server_group>
