Internet Content Adaptation Protocol
||This article includes a list of references, related reading or external links, but its sources remain unclear because it lacks inline citations. (October 2015)|
The Internet Content Adaptation Protocol (ICAP) is a lightweight HTTP-like protocol specified in RFC 3507 which is used to extend transparent proxy servers, thereby freeing up resources and standardizing the way in which new features are implemented. ICAP is generally used to implement virus scanning and content filters in transparent HTTP proxy caches. Content adaptation refers to performing the particular value added service (content manipulation) for the associated client request/response.
ICAP concentrates on leveraging edge-based devices (caching proxies) to help deliver value-added services. At the core of this process is a cache that will proxy all client transactions and will process them through ICAP Web servers. These ICAP servers are focused on a specific function, for example, ad insertion, virus scanning, content translation, language translation, or content filtering. Off-loading value-added services from Web servers to ICAP servers allows those same web servers to be scaled according to raw HTTP throughput versus having to handle these extra tasks.
ICAP was proposed in late 1999 by Peter Danzig and John Schuster from Network Appliance. Don Gillies took over the project in the spring of 2000 and enhanced the protocol to allow pipelined ICAP servers and to support all 3 encapsulations[clarification needed] of HTTP allowed by HTTP 1.1. Gillies also prototyped the first ICAP client and server for the NetCache series of internet caches in mid-2000 and produced training materials for vendors. The first demonstration ICAP Server was written in Perl and employed the Debian word-replacement filters to rewrite web pages, skipping over the HTML tags, and translate web pages into Swedish Chef or Jive in real time.