Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content (RFC7231)

IP.com Disclosure Number: IPCOM000237191D
Original Publication Date: 2014-Jun-01
Included in the Prior Art Database: 2014-Jun-08

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Fielding: AUTHOR [+4]

Abstract

Each Hypertext Transfer Protocol (HTTP) message is either a request or a response. A server listens on a connection for a request, parses each message received, interprets the message semantics in relation to the identified request target, and responds to that request with one or more response messages. A client constructs request messages to communicate specific intentions, examines received responses to see if the intentions were carried out, and determines how to interpret the results. This document defines HTTP/1.1 request and response semantics in terms of the architecture defined in [RFC7230].

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 1% of the total text.

Internet Engineering Task Force (IETF)                  R. Fielding, Ed. Request for Comments: 7231                                         Adobe Obsoletes: 2616                                          J. Reschke, Ed. Updates: 2817                                                 greenbytes Category: Standards Track                                      June 2014 ISSN: 2070-1721

      Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content

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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7231.

 Fielding & Reschke           Standards Track                    [Page 1]
 RFC 7231             HTTP/1.1 Semantics and Content            June 2014

 Copyright Notice

   Copyright (c) 2014 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    (http://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. ...