Ignore:
Timestamp:
Jan 10, 2008, 9:57:39 PM (12 years ago)
Author:
fielding@…
Message:

editorial: add introduction for ranges

File:
1 edited

Legend:

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

    r153 r158  
    524524      </ul>
    525525      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    526       <p id="rfc.section.1.p.1">This document will define aspects of HTTP related to range requests, partial responses, and the multipart/byteranges media
    527          type. Right now it only includes the extracted relevant sections of <a href="#RFC2616">RFC 2616</a> <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">[RFC2616]</cite> without edit.
     526      <p id="rfc.section.1.p.1">HTTP clients often encounter interrupted data transfers as a result of cancelled requests or dropped connections. When a cache
     527         has stored a partial representation, it is desirable to request the remainder of that representation in a subsequent request
     528         rather than transfer the entire representation. There are also a number of Web applications that benefit from being able to
     529         request only a subset of a larger representation, such as a single page of a very large document or only part of an image
     530         to be rendered by a device with limited local storage.
     531      </p>
     532      <p id="rfc.section.1.p.2">This document defines aspects of HTTP/1.1 related to range requests, partial responses, and the multipart/byteranges media
     533         type. The protocol for range requests is an <em class="bcp14">OPTIONAL</em> feature of HTTP/1.1, designed so resources or recipients that do not implement this feature can respond as if it is a normal
     534         GET request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken
     535         for full responses by intermediate caches that might not implement the feature.
     536      </p>
     537      <p id="rfc.section.1.p.3">Although the HTTP/1.1 range request mechanism is designed to allow for extensible range types, this specification only defines
     538         requests for byte ranges.
    528539      </p>
    529540      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
     
    917928      <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC2616
    918929      </h2>
    919       <p id="rfc.section.C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     930      <p id="rfc.section.C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    920931      </p>
    921932      <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p5-range-00
     
    10451056                  <li class="indline1"><em>RFC2046</em>&nbsp;&nbsp;<a class="iref" href="#RFC2046"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC2046.1">A</a></li>
    10461057                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>9.1</b></a></li>
    1047                   <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">C.1</a></li>
     1058                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#RFC2616"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">C.1</a></li>
    10481059               </ul>
    10491060            </li>
Note: See TracChangeset for help on using the changeset viewer.