Search RFCs

RFC Editor

File formats:

Status:

HISTORIC (changed from EXPERIMENTAL)

Authors:

H. Nielsen
P. Leach
S. Lawrence

Stream:

[Legacy]

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC2774

Discuss this RFC: Send questions or comments to the mailing listiesg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 2774

Abstract

A wide range of applications have proposed various extensions of theHTTP protocol. Current efforts span an enormous range, includingdistributed authoring, collaboration, printing, and remote procedurecall mechanisms. These HTTP extensions are not coordinated, sincethere has been no standard framework for defining extensions andthus, separation of concerns. This document describes a genericextension mechanism for HTTP, which is designed to address thetension between private agreement and public specification and toaccommodate extension of applications using HTTP clients, servers,and proxies. The proposal associates each extension with a globallyunique identifier, and uses HTTP header fields to carry the extensionidentifier and related information between the parties involved inthe extended communication.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.