Internet Content Adaptation Protocol (ICAP)
draft-elson-icap-01

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3507.
Authors Alberto Cerpa , Jeremy Elson
Last updated 2021-03-04 (Latest revision 2002-06-07)
RFC stream Independent Submission
Intended RFC status Informational
Formats
txt htmlized pdf bibtex bibxml
Stream ISE state (None)
Consensus boilerplate Unknown
Document shepherd (None)
IESG IESG state Became RFC 3507 (Informational)
Action Holders
(None)
Telechat date (None)
Responsible AD Ned Freed
IESG note
Send notices to (None)
Email authors IPR References Referenced by Nits Search email archive
draft-elson-icap-01 
A new Request for Comments is now available in online RFC libraries.

        RFC 3507

        Title:      Internet Content Adaptation Protocol (ICAP)
        Author(s):  J. Elson, A. Cerpa
        Status:     Informational
        Date:       April 2003
        Mailbox:    jelson@cs.ucla.edu, cerpa@cs.ucla.edu
        Pages:      49
        Characters: 98772
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-elson-icap-01.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3507.txt

ICAP, the Internet Content Adaption Protocol, is a protocol aimed
at providing simple object-based content vectoring for HTTP
services.  ICAP is, in essence, a lightweight protocol for
executing a "remote procedure call" on HTTP messages.  It allows ICAP
clients to pass HTTP messages to ICAP servers for some sort of
transformation or other processing ("adaptation").  The server
executes its transformation service on messages and sends back
responses to the client, usually with modified messages.  Typically,
the adapted messages are either HTTP requests or HTTP responses.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.