Changeset 1944

Timestamp:

22/10/12 15:34:30 (8 years ago)

Author:

julian.reschke@…

Message:

fix typos

Location:

draft-ietf-httpbis/latest

Files:

• p5-range.html (modified) (7 diffs)
• p5-range.xml (modified) (2 diffs)

draft-ietf-httpbis/latest/p5-range.html

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires April 6, 2013"; 
+       content: "Expires April 25, 2013"; 
   } 
   @bottom-right {
@@ -493 +493 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2012-10-03">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-10-22">
       <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, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
@@ -519 +519 @@
             </tr>
             <tr>
-               <td class="left">Expires: April 6, 2013</td>
+               <td class="left">Expires: April 25, 2013</td>
                <td class="right">J. Reschke, Editor</td>
             </tr>
@@ -528 +528 @@
             <tr>
                <td class="left"></td>
-               <td class="right">October 3, 2012</td>
+               <td class="right">October 22, 2012</td>
             </tr>
          </tbody>
@@ -553 +553 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on April 6, 2013.</p>
+      <p>This Internet-Draft will expire on April 25, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -751 +751 @@
       </p>
       <p id="rfc.section.4.2.p.4">If the new response is a <a href="#status.206" class="smpl">206 (Partial Content)</a> response and at least one of the matching stored responses is a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a>, then the combined response header fields consist of the most recent 200 response's header fields. If all of the matching
-         stored responses are 206 responses, then the stored response with the most header fields is used as the source of header fields
-         for the combined response, except that the client <em class="bcp14">MUST</em> use other header fields provided in the new response, aside from <a href="#header.content-range" class="smpl">Content-Range</a>, to replace all instances of the corresponding header fields in the stored response.
+         stored responses are 206 responses, then the stored response with the most recent header fields is used as the source of header
+         fields for the combined response, except that the client <em class="bcp14">MUST</em> use other header fields provided in the new response, aside from <a href="#header.content-range" class="smpl">Content-Range</a>, to replace all instances of the corresponding header fields in the stored response.
       </p>
       <p id="rfc.section.4.2.p.5">The combined response message body consists of the union of partial content ranges in the new response and each of the selected
@@ -804 +804 @@
          whose instance-length value is less than or equal to its last-byte-pos value, is invalid. The recipient of an invalid byte-content-range-spec <em class="bcp14">MUST</em> ignore it and any content transferred along with it.
       </p>
-      <p id="rfc.section.5.2.p.7">In the case of a byte range request: A server sending a response with status code <a href="#status.416" class="smpl">416 (Requested Range Not
+      <p id="rfc.section.5.2.p.7">In the case of a byte range request: a server sending a response with status code <a href="#status.416" class="smpl">416 (Requested Range Not
             Satisfiable)</a>  <em class="bcp14">SHOULD</em> include a Content-Range field with a byte-range-resp-spec of "*". The instance-length specifies the current length of the
          selected resource. A response with status code <a href="#status.206" class="smpl">206 (Partial Content)</a>  <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*".

draft-ietf-httpbis/latest/p5-range.xml

@@ -393 +393 @@
    header fields consist of the most recent 200 response's header fields.
    If all of the matching stored responses are 206 responses, then the
-   stored response with the most header fields is used as the source of
+   stored response with the most recent header fields is used as the source of
    header fields for the combined response, except that the client &MUST;
    use other header fields provided in the new response, aside from
@@ -510 +510 @@
 <t>
    In the case of a byte range request:
-   A server sending a response with status code <x:ref>416 (Requested Range Not
+   a server sending a response with status code <x:ref>416 (Requested Range Not
    Satisfiable)</x:ref> &SHOULD; include a Content-Range field with a byte-range-resp-spec
    of "*". The instance-length specifies the current length of