Changeset 1926 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 01/10/12 10:17:51 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1925 r1926 842 842 </ul> 843 843 <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> <a id="introduction" href="#introduction">Introduction</a></h1> 844 <p id="rfc.section.1.p.1">Each HTTP message is either a request or a response. A server listens on a connection for a request, parses each message received, 845 interprets the message semantics in relation to the identified request target, and responds to that request with one or more 846 response messages. This document defines HTTP/1.1 request and response semantics in terms of the architecture defined in <a href="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. 847 </p> 848 <p id="rfc.section.1.p.2">HTTP provides a uniform interface for interacting with resources regardless of their type, nature, or implementation. HTTP 849 semantics includes the intentions defined by each request method (<a href="#methods" title="Request Methods">Section 5</a>), extensions to those semantics that might be described in request header fields (<a href="#request.header.fields" title="Request Header Fields">Section 6</a>), the meaning of status codes to indicate a machine-readable response (<a href="#status.codes" title="Response Status Codes">Section 7</a>), and other control data and resource metadata that might be given in response header fields (<a href="#response.header.fields" title="Response Header Fields">Section 8</a>). 850 </p> 851 <p id="rfc.section.1.p.3"><span id="rfc.iref.c.1"></span> In addition, this document defines the payload of messages (a.k.a., content), the associated metadata header fields that define 852 how the payload is intended to be interpreted by a recipient, the request header fields that might influence content selection, 853 and the various selection algorithms that are collectively referred to as "<dfn>content negotiation</dfn>". 844 <p id="rfc.section.1.p.1">Each Hypertext Transfer Protocol (HTTP) message is either a request or a response. A server listens on a connection for a 845 request, parses each message received, interprets the message semantics in relation to the identified request target, and 846 responds to that request with one or more response messages. A client constructs request messages to communicate specific 847 intentions, and examines received responses to see if the intentions were carried out and determine how to interpret the results. 848 This document defines HTTP/1.1 request and response semantics in terms of the architecture defined in <a href="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. 849 </p> 850 <p id="rfc.section.1.p.2">HTTP provides a uniform interface for interacting with a resource (<a href="#resource" title="Resource">Section 2</a>), regardless of its type, nature, or implementation, and for transferring content in message payloads in the form of a representation 851 (<a href="#representation" title="Representation">Section 3</a>). 852 </p> 853 <p id="rfc.section.1.p.3">HTTP semantics include the intentions defined by each request method (<a href="#methods" title="Request Methods">Section 5</a>), extensions to those semantics that might be described in request header fields (<a href="#request.header.fields" title="Request Header Fields">Section 6</a>), the meaning of status codes to indicate a machine-readable response (<a href="#status.codes" title="Response Status Codes">Section 7</a>), and the meaning of other control data and resource metadata that might be given in response header fields (<a href="#response.header.fields" title="Response Header Fields">Section 8</a>). 854 </p> 855 <p id="rfc.section.1.p.4"><span id="rfc.iref.c.1"></span> This document also defines representation metadata that describe how a payload is intended to be interpreted by a recipient, 856 the request header fields that might influence content selection, and the various selection algorithms that are collectively 857 referred to as "<dfn>content negotiation</dfn>" (<a href="#content.negotiation" title="Content Negotiation">Section 3.4</a>). 854 858 </p> 855 859 <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a> <a id="conformance" href="#conformance">Conformance and Error Handling</a></h2>
Note: See TracChangeset
for help on using the changeset viewer.