Title: RFC 2774 - An HTTP Extension Framework
Description: 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.
Mail addresses
DCrocker@UDel-Relay
timbl@w3.org
fielding@ics.uci.edu
frystyk@w3.org
sob@harvard.edu
ned@innosoft.com
nsb@nsb.fv.com
fielding@ics.uci.edu
jg@w3.org
mogul@wrl.dec.com
frystyk@w3.org
timbl@w3.org
sob@harvard.edu
masinter@parc.xerox.com
timbl@w3.org
fielding@ics.uci.edu
masinter@parc.xerox.com
frystyk@microsoft.com
paulle@microsoft.com
lawrence@agranat.com
Generator: http://greenbytes.de/tech/webdav/rfcxml.xslt, Revision 1.1579, 2026/10/05 08:26:26, XSLT vendor: SAXON 6.5.5 from Michael Kay http://saxon.sf.net/
Domain: greenbytes.de
address: Henrik Frystyk Nielsen| None | text/html; charset=utf-8 |
| dcterms.creator | Lawrence, S. |
| dcterms.identifier | urn:ietf:rfc:2774 |
| dcterms.issued | 2000-02 |
| dcterms.abstract | 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. |
| dcterms.isPartOf | urn:issn:2070-1721 |
Links:
Viewport: initial-scale=1