Header Request for HTTP
draft-sharhalakis-httphreq-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Stefanos Harhalakis | ||
| Last updated | 2007-09-04 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes a method that extends HTTP to support optional on-demand headers as an addition to its dialogs. Any server side application using this method becomes able to request additional headers from conforming HTTP clients. It can also serve as an intermediate step for introducing new HTTP headers without placing the need for always exchanging them. An additional HTTP header is described and its ABNF description is provided. IANA is requested to extend its HTTP registry to support the 'on-demand' flag. IANA is also requested to provide support for header names that actually identify groups of headers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)