<?xml version="1.0" encoding="UTF-8"?>
<!--
    This XML document is the output of clean-for-DTD.xslt; a tool that strips
    extensions to RFC2629(bis) from documents for processing with xml2rfc.
-->
<!--TARGET-GENERATOR: 201706-->
<?xml-stylesheet type='text/xsl' href='lib/myxml2rfc.xslt'?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes"?>
<?rfc subcompact="no" ?>
<?rfc linkmailto="no" ?>
<?rfc editing="no" ?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc rfcedstyle="yes"?>
<!DOCTYPE rfc
  SYSTEM "rfc2629.dtd">
<rfc category="std" ipr="pre5378Trust200902" docName="draft-ietf-httpbis-range-01">

<front><title>HTTP Range Requests</title><author fullname="Roy T. Fielding" initials="R." surname="Fielding" role="editor">
    <organization>Adobe</organization>
    <address>
      <postal>
        <street>345 Park Ave</street>
        <city>San Jose</city>
        <region>CA</region>
        <code>95110</code>
        <country>USA</country>
      </postal>
      <email>fielding@gbiv.com</email>
      <uri>https://roy.gbiv.com/</uri>
    </address>
  </author><author fullname="Mark Nottingham" initials="M." surname="Nottingham" role="editor">
    <organization>Fastly</organization>
    <address>
      <email>mnot@mnot.net</email>
      <uri>https://www.mnot.net/</uri>
    </address>
  </author><author fullname="Julian F. Reschke" initials="J. F." surname="Reschke" role="editor">
    <organization abbrev="greenbytes">greenbytes GmbH</organization>
    <address>
      <postal>
        <street>Hafenweg 16</street>
        <city>Muenster</city><region>NW</region><code>48155</code>
        <country>Germany</country>
      </postal>
      <email>julian.reschke@greenbytes.de</email>
      <uri>https://greenbytes.de/tech/webdav/</uri>
    </address>
  </author><date month="May" year="2018" day="31"/>

  

  

  

  

  

  <area>Applications and Real-Time</area>
  <workgroup>HTTP Working Group</workgroup>

  <keyword>Hypertext Transfer Protocol</keyword>
  <keyword>HTTP</keyword>
  <keyword>HTTP Range Requests</keyword>

<abstract>
<t>
   The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for
   distributed, collaborative, hypertext information systems. This document
   formerly defined range requests and the rules for constructing and combining
   responses to those requests, which
   has since been moved to the core HTTP Semantics document.
</t>
</abstract>

<note title="Editorial Note"><t>This note is to be removed before publishing as an RFC.</t>
  <t>
    Discussion of this draft takes place on the HTTP working group
    mailing list (ietf-http-wg@w3.org), which is archived at
    <eref target="https://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
  </t>
  <t>
    Working Group information can be found at <eref target="https://httpwg.org/"/>;
    source code and issues list for this draft can be found at
    <eref target="https://github.com/httpwg/http-core"/>.
  </t>
  <t>
    The changes in this draft are summarized in <xref target="changes.since.00"/>.
  </t>
</note>
</front>
<middle>
<section anchor="introduction" title="Introduction">
<t>
   Hypertext Transfer Protocol (HTTP) clients often encounter interrupted data
   transfers as a result of canceled requests or dropped connections.
   This document defined HTTP/1.1 range requests, partial responses, and the
   multipart/byteranges media type.
</t>
<t>
   The entire content of this document (previously in
   <xref target="RFC2616"/> and <xref target="RFC7233"/>)
   has been moved to <xref target="Semantics"/>.
</t>
</section>
</middle>
<back>

<references title="Normative References">

<reference anchor="Semantics"><front><title>HTTP Semantics</title><author fullname="Roy T. Fielding" initials="R." surname="Fielding" role="editor">
    <organization>Adobe</organization>
    <address>
      <postal>
        <street>345 Park Ave</street>
        <city>San Jose</city>
        <region>CA</region>
        <code>95110</code>
        <country>USA</country>
      </postal>
      <email>fielding@gbiv.com</email>
      <uri>https://roy.gbiv.com/</uri>
    </address>
  </author><author fullname="Mark Nottingham" initials="M." surname="Nottingham" role="editor">
    <organization>Fastly</organization>
    <address>
      <email>mnot@mnot.net</email>
      <uri>https://www.mnot.net/</uri>
    </address>
  </author><author fullname="Julian F. Reschke" initials="J. F." surname="Reschke" role="editor">
    <organization abbrev="greenbytes">greenbytes GmbH</organization>
    <address>
      <postal>
        <street>Hafenweg 16</street>
        <city>Muenster</city><region>NW</region><code>48155</code>
        <country>Germany</country>
      </postal>
      <email>julian.reschke@greenbytes.de</email>
      <uri>https://greenbytes.de/tech/webdav/</uri>
    </address>
  </author><date month="May" year="2018" day="31"/>

  

  

  

  

  

  <area>Applications and Real-Time</area>
  <workgroup>HTTP Working Group</workgroup>

  <keyword>Hypertext Transfer Protocol</keyword>
  <keyword>HTTP</keyword>
  <keyword>HTTP semantics</keyword>
  <keyword>HTTP payload</keyword>
  <keyword>HTTP content</keyword>
  <keyword>HTTP method</keyword>
  <keyword>HTTP status code</keyword>

<abstract>
<t>
   The Hypertext Transfer Protocol (HTTP) is a stateless application-level
   protocol for distributed, collaborative, hypertext information systems.
   This document defines the semantics of HTTP: its architecture,
   terminology, the "http" and "https" Uniform Resource Identifier (URI)
   schemes, core request methods, request header fields, response status
   codes, response header fields, and content negotiation.
</t>
<t>
   This document obsoletes RFC 7231, RFC 7232, RFC 7233,
   RFC 7235, and portions of RFC 7230.
</t>
</abstract>

<note title="Editorial Note"><t>This note is to be removed before publishing as an RFC.</t>
  <t>
    Discussion of this draft takes place on the HTTP working group
    mailing list (ietf-http-wg@w3.org), which is archived at
    <eref target="https://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
  </t>
  <t>
    Working Group information can be found at <eref target="https://httpwg.org/"/>;
    source code and issues list for this draft can be found at
    <eref target="https://github.com/httpwg/http-core"/>.
  </t>
  <t>
    The changes in this draft are summarized in <xref target="changes.since.00"/>.
  </t>
</note>
</front><seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-semantics-01"/></reference>

</references>

<references title="Informative References">

<reference anchor="RFC2616" target="https://www.rfc-editor.org/info/rfc2616"><front><title>Hypertext Transfer Protocol -- HTTP/1.1</title><author initials="R." surname="Fielding" fullname="R. Fielding">
      <organization>University of California, Irvine</organization>
      <address><email>fielding@ics.uci.edu</email></address>
    </author><author initials="J." surname="Gettys" fullname="J. Gettys">
      <organization>W3C</organization>
      <address><email>jg@w3.org</email></address>
    </author><author initials="J." surname="Mogul" fullname="J. Mogul">
      <organization>Compaq Computer Corporation</organization>
      <address><email>mogul@wrl.dec.com</email></address>
    </author><author initials="H." surname="Frystyk" fullname="H. Frystyk">
      <organization>MIT Laboratory for Computer Science</organization>
      <address><email>frystyk@w3.org</email></address>
    </author><author initials="L." surname="Masinter" fullname="L. Masinter">
      <organization>Xerox Corporation</organization>
      <address><email>masinter@parc.xerox.com</email></address>
    </author><author initials="P." surname="Leach" fullname="P. Leach">
      <organization>Microsoft Corporation</organization>
      <address><email>paulle@microsoft.com</email></address>
    </author><author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
      <organization>W3C</organization>
      <address><email>timbl@w3.org</email></address>
    </author><date month="June" year="1999"/>
    
    
    
    
    
    
    
    
    
  </front><seriesInfo name="RFC" value="2616"/><seriesInfo name="DOI" value="10.17487/RFC2616"/></reference>

<reference anchor="RFC7233" target="https://www.rfc-editor.org/info/rfc7233"><front><title>Hypertext Transfer Protocol (HTTP): Range Requests</title><author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
      <organization>Adobe</organization>
      <address><email>fielding@gbiv.com</email></address>
    </author><author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
      <organization abbrev="W3C">World Wide Web Consortium</organization>
      <address><email>ylafon@w3.org</email></address>
    </author><author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
      <organization abbrev="greenbytes">greenbytes GmbH</organization>
      <address><email>julian.reschke@greenbytes.de</email></address>
    </author><date month="June" year="2014"/>
    
    
    
    
    
  </front><seriesInfo name="RFC" value="7233"/><seriesInfo name="DOI" value="10.17487/RFC7233"/></reference>

</references>

<section anchor="changes.since.00" title="Changes from RFC 7233">
<t>
  All content has been moved to <xref target="Semantics"/>.
</t>
</section>

<section anchor="acks" numbered="false" title="Acknowledgments">
<t>
  See Appendix "Acknowledgments" of <xref target="Semantics"/>.
</t>
</section>
</back>
</rfc>