Changeset 1288 for draft-ietf-httpbis

Timestamp:

25/05/11 08:22:40 (10 years ago)

Author:

julian.reschke@…

Message:

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

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (7 diffs)
• p2-semantics.xml (modified) (4 diffs)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -359 +359 @@
   } 
   @bottom-center {
-       content: "Expires November 21, 2011"; 
+       content: "Expires November 26, 2011"; 
   } 
   @bottom-right {
@@ -409 +409 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2011-05-20">
+      <meta name="dct.issued" scheme="ISO8601" content="2011-05-25">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <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.">
@@ -440 +440 @@
             </tr>
             <tr>
-               <td class="left">Expires: November 21, 2011</td>
+               <td class="left">Expires: November 26, 2011</td>
                <td class="right">HP</td>
             </tr>
@@ -493 +493 @@
             <tr>
                <td class="left"></td>
-               <td class="right">May 20, 2011</td>
+               <td class="right">May 25, 2011</td>
             </tr>
          </tbody>
@@ -522 +522 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on November 21, 2011.</p>
+      <p>This Internet-Draft will expire on November 26, 2011.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <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
          of the success to its user, in accord with its own interface, and apply any new or updated metadata in the response to the
-         active representation. For example, a 204 status code is commonly used with document editing interfaces corresponding to a
-         "save" action, such that the document being saved remains available to the user for editing. It is also frequently used with
-         interfaces that expect automated data transfers to be prevalent, such as within distributed version control systems.
-      </p>
-      <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.
+         active representation.
+      </p>
+      <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
+         the document being saved remains available to the user for editing. It is also frequently used with interfaces that expect
+         automated data transfers to be prevalent, such as within distributed version control systems.
+      </p>
+      <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.
       </p>
       <div id="rfc.iref.29"></div>
@@ -1775 +1777 @@
       <div id="rfc.iref.s.22"></div>
       <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>
-      <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,
-         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
+      <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.
+      </p>
+      <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
          to the client, the status code 404 (Not Found) can be used instead.
       </p>

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -1334 +1334 @@
   <list style="hanging">
     <t hangText="GET">
-          a representation of the target resource is sent in the response;
+      a representation of the target resource is sent in the response;
     </t>
     <t hangText="HEAD">
-          the same representation as GET, except without the message-body;
+      the same representation as GET, except without the message-body;
     </t>
     <t hangText="POST">
@@ -1443 +1443 @@
    and apply any new or updated metadata in the response to the active
    representation.
+</t>
+<t>
    For example, a 204 status code is commonly used with document editing
    interfaces corresponding to a "save" action, such that the document
@@ -1770 +1772 @@
    The server understood the request, but is refusing to fulfill it.
    Authorization will not help and the request &SHOULD-NOT;  be repeated.
+</t>
+<t>
    If the request method was not HEAD and the server wishes to make
    public why the request has not been fulfilled, it &SHOULD; describe the
@@ -1798 +1802 @@
 <t>
    The method specified in the Request-Line is not allowed for the target
-   resource. The response &MUST; include an
-   Allow header field containing a list of valid methods for the requested
-   resource.
+   resource. The response &MUST; include an Allow header field containing a
+   list of valid methods for the requested resource.
 </t>
 </section>