An Abstract Model for HTTP Resource State
draft-baker-http-resource-state-model-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mark Baker | ||
| Last updated | 2001-11-05 | ||
| 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
The documented semantics of HTTP 1.1 methods, in particular POST, are not well understood, as demonstrated by debates such as whether IPP should have used POST or a new method, how to properly bind SOAP to HTTP, and the ever more common use of POST for tunneling new protocols such as XML-RPC. This note attempts to define an abstract model for the state of HTTP URI scheme addressable resources consistent with HTTP 1.1, but hopefully more descriptive.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)