ICAP Extensions
draft-stecher-icap-subid-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Martin Stecher | ||
| Last updated | 2003-04-10 | ||
| 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
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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)