RFC 2774: An HTTP Extension Framework
In plain English — editorial summary, not part of the RFC
A wide range of applications have proposed various extensions of the HTTP protocol. Current efforts span an enormous range, including distributed authoring, collaboration, printing, and remote procedure call mechanisms. These HTTP extensions are not coordinated, since there has been no standard framework for defining extensions and thus, separation of concerns. This document describes a generic extension mechanism for HTTP, which is designed to address the tension between private agreement and public specification and to accommodate extension of applications using HTTP clients, servers, and proxies. The proposal associates each extension with a globally unique identifier, and uses HTTP header fields to carry the extension identifier and related information between the parties involved in the extended communication.
Document record
- Document ID
- RFC2774
- Published
- February 2000
- Authors
- H. Nielsen; P. Leach; S. Lawrence
- Status
- HISTORIC
- Stream
- Legacy
- Area
- —
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2554SMTP Service Extension for AuthenticationObsoleted
March 1999
- RFC 2505Anti-Spam Recommendations for SMTP MTAsCurrent
February 1999
- RFC 2487SMTP Service Extension for Secure SMTP over TLSObsoleted
January 1999
- RFC 2442The Batch SMTP Media TypeCurrent
November 1998
- RFC 2376XML Media TypesObsoleted
July 1998
- RFC 3205On the use of HTTP as a SubstrateObsoleted
February 2002
- RFC 2197SMTP Service Extension for Command PipeliningObsoleted
September 1997
- RFC 2186Internet Cache Protocol (ICP), version 2Current
September 1997
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?