Hypertext Transfer Protocol (HTTP/1.1): Range Requests
RFC 7233
| Document | Type |
RFC - Proposed Standard
(June 2014; Errata)
Obsoletes RFC 2616
|
|
|---|---|---|---|
| Authors | Roy Fielding , Yves Lafon , Julian Reschke | ||
| Last updated | 2020-01-21 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized with errata bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Mark Nottingham | ||
| Shepherd write-up | Show (last changed 2013-10-07) | ||
| IESG | IESG state | RFC 7233 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Barry Leiba | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) R. Fielding, Ed.
Request for Comments: 7233 Adobe
Obsoletes: 2616 Y. Lafon, Ed.
Category: Standards Track W3C
ISSN: 2070-1721 J. Reschke, Ed.
greenbytes
June 2014
Hypertext Transfer Protocol (HTTP/1.1): Range Requests
Abstract
The Hypertext Transfer Protocol (HTTP) is a stateless 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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7233.
Fielding, et al. Standards Track [Page 1]
RFC 7233 HTTP/1.1 Range Requests June 2014
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Fielding, et al. Standards Track [Page 2]
RFC 7233 HTTP/1.1 Range Requests June 2014
Table of Contents
1. Introduction ....................................................4
1.1. Conformance and Error Handling .............................4
1.2. Syntax Notation ............................................4
2. Range Units .....................................................5
2.1. Byte Ranges ................................................5
2.2. Other Range Units ..........................................7
2.3. Accept-Ranges ..............................................7
3. Range Requests ..................................................8
3.1. Range ......................................................8
3.2. If-Range ...................................................9
4. Responses to a Range Request ...................................10
4.1. 206 Partial Content .......................................10
4.2. Content-Range .............................................12
4.3. Combining Ranges ..........................................14
4.4. 416 Range Not Satisfiable .................................15
5. IANA Considerations ............................................16
5.1. Range Unit Registry .......................................16
5.1.1. Procedure ..........................................16
5.1.2. Registrations ......................................16
5.2. Status Code Registration ..................................17
5.3. Header Field Registration .................................17
5.4. Internet Media Type Registration ..........................17
5.4.1. Internet Media Type multipart/byteranges ...........18
6. Security Considerations ........................................19
6.1. Denial-of-Service Attacks Using Range .....................19
Show full document text