ICAP the Internet Content Adaptation Protocol
draft-elson-opes-icap-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jeremy Elson | ||
| Last updated | 2001-02-28 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
ICAP, the Internet Content Adaptation Protocol, is part of an evolving architecture that facilitates better distribution and caching for the web. ICAP is, in essence, a lightweight protocol for executing a 'remote procedure call' on HTTP messages. That is, it allows ICAP clients to pass HTTP messages to ICAP servers for 'adaptation' -- some sort of transformation or other processing. The server executes its transformation service on messages and sends back responses to the client, usually with modified messages. The adapted messages may be either HTTP requests or HTTP responses.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)