The following table summarizes ICAP features.
Element
|
Feature
|
Protocols
|
HTTP, streaming media encapsulated in HTTP, limited FTP
|
When ICAP services can be invoked (vectoring point)
|
At any of following vectoring points in the request path:
Request modification
- NetCache can send the request to the ICAP server before checking its cache for the object.
- If a cache miss occurs, NetCache can send the request to an ICAP server.
Response modification
- After the origin server responds to the request, NetCache sends the request to the ICAP server. This is the only vectoring point for FTP.
|
Access controls
|
NetCache ACLs are used to implement secure policies and control access to services. NetCache ACLs must be enabled for ICAP services, and rules can be applied to do the following:
- Direct requests for ICAP services
- Control the order of ICAP services
- Control who receives content
|
Number of ICAP servers supported
|
Multiple
|
Load balancing
|
Load balancing between the same service running on multiple ICAP servers is available.
|
NetCache logging of activity
|
An ICAP log and status information are available.
|
The following sections provide information that will help you determine the features you need for your organization.