A Proposed Extension Mechanism for HTTP
draft-kristol-http-extensions-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | David M. Kristol | ||
| Last updated | 1994-12-29 | ||
| Stream | (None) | ||
| Formats |
Expired & archived
ps
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-kristol-http-extensions-00.txt
Abstract
HTTP, the hypertext transfer protocol, underpins the World-Wide Web (WWW). As the Web has grown, pressures have mounted to add a variety of facilities to HTTP. Some of the new features that have been proposed include: keep-alive, packetized data, compression, security, and payment. This memo offers an alternative: well-defined hooks in a slightly modified HTTP framework that make it possible to add extensions to the basic protocol in a way that will retain compatible behavior between clients and servers, yet allow both clients and servers to discover and use extended capabilities. The goal is to use HTTP as just a transport mechanism, leaving other, higher-level (session) activities to extensions.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)