Changeset 1784 for draft-ietf-httpbis/latest
- Timestamp:
- 15/07/12 06:50:17 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1782 r1784 500 500 <meta name="dct.issued" scheme="ISO8601" content="2012-07-14"> 501 501 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 502 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the six-part specification that defines the protocol referred to as "HTTP/1.1". Part 2 defines the semantics of HTTP messages, as expressed by request methods, request header fields, response status codes, and response header fields, the payload of messages as metadata and body content, and themechanisms for content negotiation.">503 <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the six-part specification that defines the protocol referred to as "HTTP/1.1". Part 2 defines the semantics of HTTP messages, as expressed by request methods, request header fields, response status codes, and response header fields, the payload of messages as metadata and body content, and themechanisms for content negotiation.">502 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an 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."> 503 <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an 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."> 504 504 </head> 505 505 <body onload="init();"> … … 541 541 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 542 542 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information 543 systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the 544 six-part specification that defines the protocol referred to as "HTTP/1.1". 545 </p> 546 <p>Part 2 defines the semantics of HTTP messages, as expressed by request methods, request header fields, response status codes, 547 and response header fields, the payload of messages as metadata and body content, and the mechanisms for content negotiation. 543 systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, 544 response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms 545 for content negotiation. 548 546 </p> 549 547 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> … … 804 802 </ul> 805 803 <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> <a id="introduction" href="#introduction">Introduction</a></h1> 806 <p id="rfc.section.1.p.1"> This document defines HTTP/1.1 request and response semantics in terms of the architecture, syntax notation, and conformance807 criteria defined in <a href="p1-messaging.html#architecture" title="Architecture">Section 2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. Each HTTP message is either a request or a response. A server listens on a connection for a request, parses each message808 re ceived, interprets the message semantics in relation to the identified request target, and responds to that request with809 one or more response messages.804 <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, 805 interprets the message semantics in relation to the identified request target, and responds to that request with one or more 806 response messages. This document defines HTTP/1.1 request and response semantics in terms of the architecture, syntax notation, 807 and conformance criteria defined in <a href="p1-messaging.html#architecture" title="Architecture">Section 2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 810 808 </p> 811 809 <p id="rfc.section.1.p.2">HTTP provides a uniform interface for interacting with resources regardless of their type, nature, or implementation. HTTP … … 819 817 </p> 820 818 <div class="note" id="rfc.section.1.p.4"> 821 <p> This document is currently disorganized in order to minimize the changes between drafts and enable reviewers to see the smaller819 <p> <b>Note:</b> This document is currently disorganized in order to minimize changes between drafts and enable reviewers to see the smaller 822 820 errata changes. A future draft will reorganize the sections to better reflect the content. In particular, the sections will 823 821 be ordered according to the typical processing of an HTTP request message (after message parsing): resource mapping, methods, -
draft-ietf-httpbis/latest/p2-semantics.xml
r1782 r1784 186 186 <t> 187 187 The Hypertext Transfer Protocol (HTTP) is an application-level protocol for 188 distributed, collaborative, hypertext information systems. HTTP has been in 189 use by the World Wide Web global information initiative since 1990. This 190 document is Part 2 of the six-part specification that defines the protocol 191 referred to as "HTTP/1.1". 192 </t> 193 <t> 194 Part 2 defines the semantics of HTTP messages, as expressed by request 188 distributed, collaborative, hypertext information systems. This document 189 defines the semantics of HTTP/1.1 messages, as expressed by request 195 190 methods, request header fields, response status codes, and response header 196 fields, the payload of messages as metadata and body content, and the191 fields, along with the payload of messages (metadata and body content) and 197 192 mechanisms for content negotiation. 198 193 </t> … … 216 211 </note> 217 212 </front> 213 218 214 <middle> 219 215 <section title="Introduction" anchor="introduction"> 220 216 <t> 217 Each HTTP message is either a request or a response. A server listens on a 218 connection for a request, parses each message received, interprets the 219 message semantics in relation to the identified request target, and 220 responds to that request with one or more response messages. 221 221 This document defines HTTP/1.1 request and response semantics in terms of 222 222 the architecture, syntax notation, and conformance criteria defined in 223 &architecture;. Each HTTP message is either a request or a response. 224 A server listens on a connection for a request, parses each message 225 received, interprets the message semantics in relation to the identified 226 request target, and responds to that request with one or more response 227 messages. 223 &architecture;. 228 224 </t> 229 225 <t> … … 244 240 </t> 245 241 <x:note><t> 246 This document is currently disorganized in order to minimize the changes242 &Note; This document is currently disorganized in order to minimize changes 247 243 between drafts and enable reviewers to see the smaller errata changes. 248 244 A future draft will reorganize the sections to better reflect the content.
Note: See TracChangeset
for help on using the changeset viewer.