Hyper Text Caching Protocol (HTCP/0.0)

Metadata

Publisher: IETF
Doc Type: Experimental
Pages: 15
Abstract: This document describes HTCP, a protocol for discovering HTTP caches and cached data, managing sets of HTTP caches, and monitoring cache activity. This is an experimental protocol, one among several proposals to perform these functions. This memo defines an Experimental Protocol for the Internet community.
Publication Date: 2000-01-01
Status Note: Experimental
DOI: 10.17487/RFC2756
Link: https://doi.org/10.17487/RFC2756
Author(s): Paul A. Vixie
Duane Wessels
Keyword(s): HTCP, HTTP Caching, Data

Latest version of IETF RFC 2756

Document Versions — IETF RFC 2756

▶ IETF RFC 2756 (2000-01-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Bibliographic Reference(s)

IETF RFC 2104 [Active, Amended*]
IETF RFC 2186 [Active*]
IETF RFC 2396 [Superseded*]
IETF RFC 2616 [Superseded*]

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC2756.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 2756, Hyper Text Caching Protocol (HTCP/0.0). Available at https://doi.org/10.17487/RFC2756

Snippet:

IETF RFC 2756, Hyper Text Caching Protocol (HTCP/0.0). Available at https://doi.org/10.17487/RFC2756

HTML (ISO 690 compliant)

Preview:

IETF RFC 2756, Hyper Text Caching Protocol (HTCP/0.0). Available at https://doi.org/10.17487/RFC2756

Snippet:

<span class="citation"><cite>IETF RFC 2756</cite>, Hyper Text Caching Protocol (HTCP/0.0). Available at <a href="https://doi.org/10.17487/RFC2756" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2756</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 2756, Hyper Text Caching Protocol (HTCP/0.0)
doi: 10.17487/RFC2756
url: https://doi.org/10.17487/RFC2756

Snippet:

<li>
<cite id="bib-rfc2756">IETF RFC 2756</cite>, Hyper Text Caching Protocol (HTCP/0.0)
<span class="doi">10.17487/RFC2756</span>
</li>

Referenced By

IETF RFC 3040 [Active*]
IETF RFC 3234 [Active*]