Changeset 1257 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 04/04/11 14:46:15 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1255 r1257 359 359 } 360 360 @bottom-center { 361 content: "Expires October 5, 2011";361 content: "Expires October 6, 2011"; 362 362 } 363 363 @bottom-right { … … 409 409 <meta name="dct.creator" content="Reschke, J. F."> 410 410 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 411 <meta name="dct.issued" scheme="ISO8601" content="2011-04-0 3">411 <meta name="dct.issued" scheme="ISO8601" content="2011-04-04"> 412 412 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 413 413 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia 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."> … … 440 440 </tr> 441 441 <tr> 442 <td class="left">Expires: October 5, 2011</td>442 <td class="left">Expires: October 6, 2011</td> 443 443 <td class="right">HP</td> 444 444 </tr> … … 493 493 <tr> 494 494 <td class="left"></td> 495 <td class="right">April 3, 2011</td>495 <td class="right">April 4, 2011</td> 496 496 </tr> 497 497 </tbody> … … 520 520 in progress”. 521 521 </p> 522 <p>This Internet-Draft will expire on October 5, 2011.</p>522 <p>This Internet-Draft will expire on October 6, 2011.</p> 523 523 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 524 524 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1596 1596 <div id="rfc.iref.s.8"></div> 1597 1597 <h3 id="rfc.section.8.2.5"><a href="#rfc.section.8.2.5">8.2.5</a> <a id="status.204" href="#status.204">204 No Content</a></h3> 1598 <p id="rfc.section.8.2.5.p.1">The server has successfully fulfilled the request, but there is no additional content to return in the response payload body. 1599 The resource metadata and representation metadata in the response message's header fields refer to the target resource and 1600 its current representation, respectively, after the requested action. For example, if a 204 status code is received in response 1601 to a PUT and the response contains an ETag header field, then the value of that field is the current entity-tag for the representation 1602 that was successfully PUT. 1603 </p> 1604 <p id="rfc.section.8.2.5.p.2">If the client is a user agent, it <em class="bcp14">SHOULD NOT</em> change its document view from that which caused the request to be sent. This response is primarily intended to allow input 1605 for actions to take place without causing a change to the user agent's active document view, although any new or updated metadata <em class="bcp14">SHOULD</em> be applied to the document currently in the user agent's active view. 1606 </p> 1607 <p id="rfc.section.8.2.5.p.3">The 204 response <em class="bcp14">MUST NOT</em> include a message-body, and thus is always terminated by the first empty line after the header fields. 1598 <p id="rfc.section.8.2.5.p.1">The 204 (No Content) status code indicates that the server has successfully fulfilled the request and that there is no additional 1599 content to return in the response payload body. Metadata in the response header fields refer to the target resource and its 1600 current representation after the requested action. 1601 </p> 1602 <p id="rfc.section.8.2.5.p.2">For example, if a 204 status code is received in response to a PUT request and the response contains an ETag header field, 1603 then the PUT was successful and the ETag field-value contains the entity-tag for the new representation of that target resource. 1604 </p> 1605 <p id="rfc.section.8.2.5.p.3">The 204 response allows a server to indicate that the action has been successfully applied to the target resource while implying 1606 that the user agent <em class="bcp14">SHOULD NOT</em> traverse away from its current "document view" (if any). The server assumes that the user agent will provide some indication 1607 of the success to its user, in accord with its own interface, and apply any new or updated metadata in the response to the 1608 active representation. For example, a 204 status code is commonly used with document editing interfaces corresponding to a 1609 "save" action, such that the document being saved remains available to the user for editing. It is also frequently used with 1610 interfaces that expect automated data transfers to be prevalent, such as within distributed version control systems. 1611 </p> 1612 <p id="rfc.section.8.2.5.p.4">The 204 response <em class="bcp14">MUST NOT</em> include a message-body, and thus is always terminated by the first empty line after the header fields. 1608 1613 </p> 1609 1614 <div id="rfc.iref.29"></div>
Note: See TracChangeset
for help on using the changeset viewer.