ICAP Extensions

Document Type Expired Internet-Draft (individual)
Last updated 2003-04-10
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


The Internet Content Adaptation Protocol (ICAP) [1] provides simple, object-based content vectoring for HTTP services. User-defined header extensions are widely used by many ICAP client and server implementations. Some implementations have also introduced new ICAP methods. This document describes and defines a number of ICAP extensions to ensure ongoing interoperability between the implementations.


Martin Stecher (martin.stecher@webwasher.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)