Specification of HTTP/1.1 OPTIONS messages
draft-ietf-http-options-02
| Document | Type |
Expired Internet-Draft
(http WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jeffrey Mogul , John W. Cohen M.A. | ||
| Last updated | 1997-08-29 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
RFC2068 defined a new OPTIONS method for HTTP/1.1. The purpose of OPTIONS is to allow a 'client to determine the options and/or requirements associated with a resource, or the capabilities of a server, without implying a resource action or initiating a resource retrieval.' However, RFC2068 did not defined a specific syntax for using OPTIONS to make such a determination. This proposal clarifies the original specification of OPTIONS, adds several new HTTP message headers to provide syntactic support for OPTIONS, and establishes new IANA registries to avoid namespace conflicts.
Authors
Jeffrey Mogul
John W. Cohen M.A.
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)