Hypertext Transfer Protocol: Semantics and Content
draft-fielding-httpbis-http-semantics-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Roy T. Fielding , Julian Reschke | ||
| Last updated | 2018-03-05 | ||
| Replaced by | draft-ietf-httpbis-semantics | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-httpbis-semantics | |
| 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 Hypertext Transfer Protocol (HTTP) is a stateless application- level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation. This document obsoletes RFC 7231.
Authors
Roy T. Fielding
Julian Reschke
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)