Hypertext Transfer Protocol: Semantics and Content
draft-fielding-httpbis-http-semantics-00

Document Type Active Internet-Draft (individual)
Last updated 2018-03-05
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                   R. Fielding, Ed.
Internet-Draft                                                     Adobe
Obsoletes: 7231 (if approved)                            J. Reschke, Ed.
Intended status: Standards Track                              greenbytes
Expires: September 6, 2018                                 March 5, 2018

           Hypertext Transfer Protocol: Semantics and Content
                draft-fielding-httpbis-http-semantics-00

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.

Editorial Note

   This note is to be removed before publishing as an RFC.

   _This is a temporary document for the purpose of planning the
   revisions of RFCs 7230 to 7235.  This is not yet an official work
   item of the HTTP Working Group._

   Discussion of this draft takes place on the HTTP working group
   mailing list (ietf-http-wg@w3.org), which is archived at
   <http://lists.w3.org/Archives/Public/ietf-http-wg/>.

   Errata for RFC 7231 have been collected at <https://www.rfc-
   editor.org/errata_search.php?rfc=7231>, and an additional issues list
   lives at <https://github.com/httpwg/http11bis/issues>.

   The changes in this draft are summarized in Appendix E.1.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute

Fielding & Reschke      Expires September 6, 2018               [Page 1]
Internet-Draft         HTTP Semantics and Content             March 2018

   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 6, 2018.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   5
     1.1.  Conformance and Error Handling  . . . . . . . . . . . . .   6
     1.2.  Syntax Notation . . . . . . . . . . . . . . . . . . . . .   6
   2.  Resources . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   3.  Representations . . . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  Representation Metadata . . . . . . . . . . . . . . . . .   8
       3.1.1.  Processing Representation Data  . . . . . . . . . . .   8
       3.1.2.  Encoding for Compression or Integrity . . . . . . . .  11
       3.1.3.  Audience Language . . . . . . . . . . . . . . . . . .  12

Fielding & Reschke      Expires September 6, 2018               [Page 2]
Internet-Draft         HTTP Semantics and Content             March 2018

       3.1.4.  Identification  . . . . . . . . . . . . . . . . . . .  14
     3.2.  Representation Data . . . . . . . . . . . . . . . . . . .  17
     3.3.  Payload Semantics . . . . . . . . . . . . . . . . . . . .  17
     3.4.  Content Negotiation . . . . . . . . . . . . . . . . . . .  18
Show full document text