Changeset 1640 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 30/03/12 14:38:53 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1639 r1640 4 4 <head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/"> 5 5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> 6 <title>HTTP/1.1, part 2: Message Semantics </title><script>6 <title>HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation</title><script> 7 7 var buttonsAdded = false; 8 8 … … 506 506 <meta name="dct.issued" scheme="ISO8601" content="2012-03-30"> 507 507 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 508 <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 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields. ">509 <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 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields. ">508 <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 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields. Furthermore, it defines HTTP message content, metadata, and content negotiation. #351"> 509 <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 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields. Furthermore, it defines HTTP message content, metadata, and content negotiation. #351"> 510 510 </head> 511 511 <body onload="init();"> … … 544 544 </tbody> 545 545 </table> 546 <p class="title">HTTP/1.1, part 2: Message Semantics <br><span class="filename">draft-ietf-httpbis-p2-semantics-latest</span></p>546 <p class="title">HTTP/1.1, part 2: Message Semantics, Payload and Content Negotiation<br><span class="filename">draft-ietf-httpbis-p2-semantics-latest</span></p> 547 547 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 548 548 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information … … 551 551 </p> 552 552 <p>Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, 553 and response header fields. 553 and response header fields. Furthermore, it defines HTTP message content, metadata, and content negotiation. <span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: #351]</span> 554 554 </p> 555 555 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> … … 761 761 response messages that might be expected as a result of applying that method to the target resource. 762 762 </p> 763 <p id="rfc.section.1.p.2">This document is currently disorganized in order to minimize the changes between drafts and enable reviewers to see the smaller 763 <p id="rfc.section.1.p.2">Furthermore, it defines HTTP/1.1 message payloads (a.k.a., content), the associated metadata header fields that define how 764 the payload is intended to be interpreted by a recipient, the request header fields that might influence content selection, 765 and the various selection algorithms that are collectively referred to as HTTP content negotiation. <span class="comment" id="rfc.comment.2">[<a href="#rfc.comment.2" class="smpl">rfc.comment.2</a>: #351]</span> 766 </p> 767 <p id="rfc.section.1.p.3">This document is currently disorganized in order to minimize the changes between drafts and enable reviewers to see the smaller 764 768 errata changes. A future draft will reorganize the sections to better reflect the content. In particular, the sections will 765 769 be ordered according to the typical processing of an HTTP request message (after message parsing): resource mapping, methods,
Note: See TracChangeset
for help on using the changeset viewer.