Internet Content Adaptation Protocol
 | This article may be written in a style that is too abstract to be readily understandable by general audiences. (April 2020) |
 | This article includes a list of references, related reading, or external links, but its sources remain unclear because it lacks inline citations. (October 2015) |
| Communication protocol | |
| Abbreviation | ICAP |
|---|---|
| Purpose | Content adaptation |
| Developer(s) | Peter Danzig and John Schuster |
| Introduction | Proposed: 1999 Standardized: April 2003 |
| OSI layer | Application layer (7) |
| RFC(s) | 3507 |
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 web servers. These ICAP servers are focused on a specific function, for example, ad insertion, virus scanning, multi-AV 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.
History
[edit]ICAP was proposed in late 1999 by Peter Danzig and John Schuster[1] from Network Appliance.[2] Don Gillies took over the project in the spring of 2000 and enhanced the protocol in three main ways:
- To allow pipelined ICAP servers. One web page could be streamed through virus-scan, content-filtering, and language translation servers, quickly.
- To support all 3 content encodings (content-length, chunked, and TCP-close) in HTTP 1.1. This replaced original store-and-forward protocol with continuous streaming of content through many servers at once.
- To provide a feature called "content preview" that allowed the ICAP server to look at the first few hundred bytes of content before deciding to process the content or not. This was implemented by embedding the preview argument size in the ICAP webserver URL when configured on the ICAP client.
Gillies prototyped the first ICAP client and server for the NetCache series of internet caches in mid-2000 (known as ICAP 0.9 protocol) and produced training materials for vendors. The client was written in C++ in the core of the NetCache server, and the demonstration ICAP Server was written in Perl and employed the Debian word-replacement filters to rewrite web pages, skipping over the HTML tags, and translating web pages into Swedish Chef or Jive in real time.[3] With knowledge learned from the prototyping experience, Gillies revised the IETF draft standard to make RPCs using only chunked encoding, greatly simplifying the ICAP protocol.[1]
References
[edit]- ^ a b J. Elson; A. Cerpa (2003). Internet Content Adaptation Protocol (ICAP). IETF. doi:10.17487/RFC3507. RFC 3507.
- ^ "Internet Content Adaptation Protocol (ICAP)" (PDF). NetApp. 2001-07-30.
- ^ Gillies, Donald. "ICAP Installation Instructions". UBC ECE Dept. Archived from the original on 2016-03-04. Retrieved 2016-01-04.