Ignore:
Timestamp:
May 25, 2011, 1:22:40 AM (8 years ago)
Author:
julian.reschke@…
Message:

add a para break into section about 403, src code reformat (editorial)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1287 r1288  
    359359  }
    360360  @bottom-center {
    361        content: "Expires November 21, 2011";
     361       content: "Expires November 26, 2011";
    362362  }
    363363  @bottom-right {
     
    409409      <meta name="dct.creator" content="Reschke, J. F.">
    410410      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    411       <meta name="dct.issued" scheme="ISO8601" content="2011-05-20">
     411      <meta name="dct.issued" scheme="ISO8601" content="2011-05-25">
    412412      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    413413      <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 &#34;HTTP/1.1&#34; 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.">
     
    440440            </tr>
    441441            <tr>
    442                <td class="left">Expires: November 21, 2011</td>
     442               <td class="left">Expires: November 26, 2011</td>
    443443               <td class="right">HP</td>
    444444            </tr>
     
    493493            <tr>
    494494               <td class="left"></td>
    495                <td class="right">May 20, 2011</td>
     495               <td class="right">May 25, 2011</td>
    496496            </tr>
    497497         </tbody>
     
    522522         in progress”.
    523523      </p>
    524       <p>This Internet-Draft will expire on November 21, 2011.</p>
     524      <p>This Internet-Draft will expire on November 26, 2011.</p>
    525525      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    526526      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    16211621         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
    16221622         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.
    16281630      </p>
    16291631      <div id="rfc.iref.29"></div>
     
    17751777      <div id="rfc.iref.s.22"></div>
    17761778      <h3 id="rfc.section.8.4.4"><a href="#rfc.section.8.4.4">8.4.4</a>&nbsp;<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
    17791782         to the client, the status code 404 (Not Found) can be used instead.
    17801783      </p>
Note: See TracChangeset for help on using the changeset viewer.