Changeset 1257 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 04/04/11 14:46:15 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r1254 r1257 1398 1398 <iref primary="true" item="Status Codes" subitem="204 No Content" x:for-anchor=""/> 1399 1399 <t> 1400 The server has successfully fulfilled the request, but there is no 1401 additional content to return in the response payload body. The 1402 resource metadata and representation metadata in the response message's 1403 header fields refer to the target resource 1404 and its current representation, respectively, after the requested action. 1400 The 204 (No Content) status code indicates that the server has 1401 successfully fulfilled the request and that there is no additional 1402 content to return in the response payload body. Metadata in the 1403 response header fields refer to the target resource and its current 1404 representation after the requested action. 1405 </t> 1406 <t> 1405 1407 For example, if a 204 status code is received in response to a PUT 1406 and the response contains an ETag header field, then the value of 1407 that field is the current entity-tag for the representation that 1408 was successfully PUT. 1409 </t> 1410 <t> 1411 If the client is a user agent, it &SHOULD-NOT; change its document view 1412 from that which caused the request to be sent. This response is 1413 primarily intended to allow input for actions to take place without 1414 causing a change to the user agent's active document view, although 1415 any new or updated metadata &SHOULD; be applied to the document 1416 currently in the user agent's active view. 1408 request and the response contains an ETag header field, then the PUT 1409 was successful and the ETag field-value contains the entity-tag for 1410 the new representation of that target resource. 1411 </t> 1412 <t> 1413 The 204 response allows a server to indicate that the action has been 1414 successfully applied to the target resource while implying that the 1415 user agent &SHOULD-NOT; traverse away from its current "document view" 1416 (if any). The server assumes that the user agent will provide some 1417 indication of the success to its user, in accord with its own interface, 1418 and apply any new or updated metadata in the response to the active 1419 representation. 1420 For example, a 204 status code is commonly used with document editing 1421 interfaces corresponding to a "save" action, such that the document 1422 being saved remains available to the user for editing. It is also 1423 frequently used with interfaces that expect automated data transfers 1424 to be prevalent, such as within distributed version control systems. 1417 1425 </t> 1418 1426 <t>
Note: See TracChangeset
for help on using the changeset viewer.