Changeset 1732 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 06/07/12 06:32:41 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1728 r1732 449 449 } 450 450 @bottom-center { 451 content: "Expires January 6, 2013";451 content: "Expires January 7, 2013"; 452 452 } 453 453 @bottom-right { … … 497 497 <meta name="dct.creator" content="Reschke, J. F."> 498 498 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 499 <meta name="dct.issued" scheme="ISO8601" content="2012-07-0 5">499 <meta name="dct.issued" scheme="ISO8601" content="2012-07-06"> 500 500 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 501 501 <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."> … … 528 528 </tr> 529 529 <tr> 530 <td class="left">Expires: January 6, 2013</td>530 <td class="left">Expires: January 7, 2013</td> 531 531 <td class="right">greenbytes</td> 532 532 </tr> 533 533 <tr> 534 534 <td class="left"></td> 535 <td class="right">July 5, 2012</td>535 <td class="right">July 6, 2012</td> 536 536 </tr> 537 537 </tbody> … … 563 563 in progress”. 564 564 </p> 565 <p>This Internet-Draft will expire on January 6, 2013.</p>565 <p>This Internet-Draft will expire on January 7, 2013.</p> 566 566 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 567 567 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2330 2330 <p id="rfc.section.6.p.2">A "<dfn>payload</dfn>" in HTTP is always a partial or complete representation of some resource. We use separate terms for payload and representation 2331 2331 because some messages contain only the associated representation's header fields (e.g., responses to HEAD) or only some part(s) 2332 of the representation (e.g., the 206status code).2332 of the representation (e.g., the <a href="p5-range.html#status.206" class="smpl">206 (Partial Content)</a> status code). 2333 2333 </p> 2334 2334 <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a> <a id="payload.header.fields" href="#payload.header.fields">Payload Header Fields</a></h2> … … 2391 2391 target resource. 2392 2392 </li> 2393 <li>If the response status code is 204, 206, or 304 and the request method was GET or HEAD, the response payload is a partial 2394 representation of the target resource. 2393 <li>If the response status code is 204, <a href="p5-range.html#status.206" class="smpl">206</a>, or 304 and the request method was GET or HEAD, the response payload is a partial representation of the target resource. 2395 2394 </li> 2396 2395 <li>If the response has a Content-Location header field, and that URI is the same as the effective request URI, the response payload
Note: See TracChangeset
for help on using the changeset viewer.