Changeset 1288 for draft-ietf-httpbis
- Timestamp:
- 25/05/11 08:22:40 (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1287 r1288 359 359 } 360 360 @bottom-center { 361 content: "Expires November 2 1, 2011";361 content: "Expires November 26, 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-05-2 0">411 <meta name="dct.issued" scheme="ISO8601" content="2011-05-25"> 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: November 2 1, 2011</td>442 <td class="left">Expires: November 26, 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">May 2 0, 2011</td>495 <td class="right">May 25, 2011</td> 496 496 </tr> 497 497 </tbody> … … 522 522 in progress”. 523 523 </p> 524 <p>This Internet-Draft will expire on November 2 1, 2011.</p>524 <p>This Internet-Draft will expire on November 26, 2011.</p> 525 525 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 526 526 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1621 1621 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 1622 1622 of the success to its user, in accord with its own interface, and apply any new or updated metadata in the response to the 1623 active representation. For example, a 204 status code is commonly used with document editing interfaces corresponding to a 1624 "save" action, such that the document being saved remains available to the user for editing. It is also frequently used with 1625 interfaces that expect automated data transfers to be prevalent, such as within distributed version control systems. 1626 </p> 1627 <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. 1623 active representation. 1624 </p> 1625 <p id="rfc.section.8.2.5.p.4">For example, a 204 status code is commonly used with document editing interfaces corresponding to a "save" action, such that 1626 the document being saved remains available to the user for editing. It is also frequently used with interfaces that expect 1627 automated data transfers to be prevalent, such as within distributed version control systems. 1628 </p> 1629 <p id="rfc.section.8.2.5.p.5">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. 1628 1630 </p> 1629 1631 <div id="rfc.iref.29"></div> … … 1775 1777 <div id="rfc.iref.s.22"></div> 1776 1778 <h3 id="rfc.section.8.4.4"><a href="#rfc.section.8.4.4">8.4.4</a> <a id="status.403" href="#status.403">403 Forbidden</a></h3> 1777 <p id="rfc.section.8.4.4.p.1">The server understood the request, but is refusing to fulfill it. Authorization will not help and the request <em class="bcp14">SHOULD NOT</em> be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, 1778 it <em class="bcp14">SHOULD</em> describe the reason for the refusal in the representation. If the server does not wish to make this information available 1779 <p id="rfc.section.8.4.4.p.1">The server understood the request, but is refusing to fulfill it. Authorization will not help and the request <em class="bcp14">SHOULD NOT</em> be repeated. 1780 </p> 1781 <p id="rfc.section.8.4.4.p.2">If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it <em class="bcp14">SHOULD</em> describe the reason for the refusal in the representation. If the server does not wish to make this information available 1779 1782 to the client, the status code 404 (Not Found) can be used instead. 1780 1783 </p> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1283 r1288 1334 1334 <list style="hanging"> 1335 1335 <t hangText="GET"> 1336 1336 a representation of the target resource is sent in the response; 1337 1337 </t> 1338 1338 <t hangText="HEAD"> 1339 1339 the same representation as GET, except without the message-body; 1340 1340 </t> 1341 1341 <t hangText="POST"> … … 1443 1443 and apply any new or updated metadata in the response to the active 1444 1444 representation. 1445 </t> 1446 <t> 1445 1447 For example, a 204 status code is commonly used with document editing 1446 1448 interfaces corresponding to a "save" action, such that the document … … 1770 1772 The server understood the request, but is refusing to fulfill it. 1771 1773 Authorization will not help and the request &SHOULD-NOT; be repeated. 1774 </t> 1775 <t> 1772 1776 If the request method was not HEAD and the server wishes to make 1773 1777 public why the request has not been fulfilled, it &SHOULD; describe the … … 1798 1802 <t> 1799 1803 The method specified in the Request-Line is not allowed for the target 1800 resource. The response &MUST; include an 1801 Allow header field containing a list of valid methods for the requested 1802 resource. 1804 resource. The response &MUST; include an Allow header field containing a 1805 list of valid methods for the requested resource. 1803 1806 </t> 1804 1807 </section>
Note: See TracChangeset
for help on using the changeset viewer.