<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.elson-opes-icap" target="https://datatracker.ietf.org/doc/html/draft-elson-opes-icap-01">
   <front>
      <title>ICAP the Internet Content Adaptation Protocol</title>
      <author initials="J." surname="Elson" fullname="Jeremy Elson">
         </author>
      <date month="February" day="28" year="2001" />
      <abstract>
	 <t>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 &#x27;remote procedure call&#x27; on HTTP messages.  That is, it
allows ICAP clients to pass HTTP messages to ICAP servers for
&#x27;adaptation&#x27; -- 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.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-elson-opes-icap-01" />
   
</reference>
