Changeset 1944


Ignore:
Timestamp:
Oct 22, 2012, 8:34:30 AM (7 years ago)
Author:
julian.reschke@…
Message:

fix typos

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.html

    r1931 r1944  
    449449  }
    450450  @bottom-center {
    451        content: "Expires April 6, 2013";
     451       content: "Expires April 25, 2013";
    452452  }
    453453  @bottom-right {
     
    493493      <meta name="dct.creator" content="Reschke, J. F.">
    494494      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    495       <meta name="dct.issued" scheme="ISO8601" content="2012-10-03">
     495      <meta name="dct.issued" scheme="ISO8601" content="2012-10-22">
    496496      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    497497      <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.">
     
    519519            </tr>
    520520            <tr>
    521                <td class="left">Expires: April 6, 2013</td>
     521               <td class="left">Expires: April 25, 2013</td>
    522522               <td class="right">J. Reschke, Editor</td>
    523523            </tr>
     
    528528            <tr>
    529529               <td class="left"></td>
    530                <td class="right">October 3, 2012</td>
     530               <td class="right">October 22, 2012</td>
    531531            </tr>
    532532         </tbody>
     
    553553         in progress”.
    554554      </p>
    555       <p>This Internet-Draft will expire on April 6, 2013.</p>
     555      <p>This Internet-Draft will expire on April 25, 2013.</p>
    556556      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    557557      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    751751      </p>
    752752      <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
    753          stored responses are 206 responses, then the stored response with the most header fields is used as the source of header fields
    754          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.
     753         stored responses are 206 responses, then the stored response with the most recent header fields is used as the source of header
     754         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.
    755755      </p>
    756756      <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
     
    804804         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.
    805805      </p>
    806       <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
     806      <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
    807807            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
    808808         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

    r1929 r1944  
    393393   header fields consist of the most recent 200 response's header fields.
    394394   If all of the matching stored responses are 206 responses, then the
    395    stored response with the most header fields is used as the source of
     395   stored response with the most recent header fields is used as the source of
    396396   header fields for the combined response, except that the client &MUST;
    397397   use other header fields provided in the new response, aside from
     
    510510<t>
    511511   In the case of a byte range request:
    512    A server sending a response with status code <x:ref>416 (Requested Range Not
     512   a server sending a response with status code <x:ref>416 (Requested Range Not
    513513   Satisfiable)</x:ref> &SHOULD; include a Content-Range field with a byte-range-resp-spec
    514514   of "*". The instance-length specifies the current length of
Note: See TracChangeset for help on using the changeset viewer.