| 1 | <!DOCTYPE html |
|---|
| 2 | PUBLIC "-//W3C//DTD HTML 4.01//EN"> |
|---|
| 3 | <html lang="en"> |
|---|
| 4 | <head profile="http://www.w3.org/2006/03/hcard"> |
|---|
| 5 | <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> |
|---|
| 6 | <title>HTTP/1.1, part 5: Range Requests and Partial Responses</title><style type="text/css" title="Xml2Rfc (sans serif)"> |
|---|
| 7 | a { |
|---|
| 8 | text-decoration: none; |
|---|
| 9 | } |
|---|
| 10 | a.smpl { |
|---|
| 11 | color: black; |
|---|
| 12 | } |
|---|
| 13 | a:hover { |
|---|
| 14 | text-decoration: underline; |
|---|
| 15 | } |
|---|
| 16 | a:active { |
|---|
| 17 | text-decoration: underline; |
|---|
| 18 | } |
|---|
| 19 | address { |
|---|
| 20 | margin-top: 1em; |
|---|
| 21 | margin-left: 2em; |
|---|
| 22 | font-style: normal; |
|---|
| 23 | } |
|---|
| 24 | body { |
|---|
| 25 | color: black; |
|---|
| 26 | font-family: verdana, helvetica, arial, sans-serif; |
|---|
| 27 | font-size: 10pt; |
|---|
| 28 | } |
|---|
| 29 | cite { |
|---|
| 30 | font-style: normal; |
|---|
| 31 | } |
|---|
| 32 | dd { |
|---|
| 33 | margin-right: 2em; |
|---|
| 34 | } |
|---|
| 35 | dl { |
|---|
| 36 | margin-left: 2em; |
|---|
| 37 | } |
|---|
| 38 | |
|---|
| 39 | dl.empty dd { |
|---|
| 40 | margin-top: .5em; |
|---|
| 41 | } |
|---|
| 42 | dl p { |
|---|
| 43 | margin-left: 0em; |
|---|
| 44 | } |
|---|
| 45 | dt { |
|---|
| 46 | margin-top: .5em; |
|---|
| 47 | } |
|---|
| 48 | h1 { |
|---|
| 49 | font-size: 14pt; |
|---|
| 50 | line-height: 21pt; |
|---|
| 51 | page-break-after: avoid; |
|---|
| 52 | } |
|---|
| 53 | h1.np { |
|---|
| 54 | page-break-before: always; |
|---|
| 55 | } |
|---|
| 56 | h1 a { |
|---|
| 57 | color: #333333; |
|---|
| 58 | } |
|---|
| 59 | h2 { |
|---|
| 60 | font-size: 12pt; |
|---|
| 61 | line-height: 15pt; |
|---|
| 62 | page-break-after: avoid; |
|---|
| 63 | } |
|---|
| 64 | h2 a { |
|---|
| 65 | color: black; |
|---|
| 66 | } |
|---|
| 67 | h3 { |
|---|
| 68 | font-size: 10pt; |
|---|
| 69 | page-break-after: avoid; |
|---|
| 70 | } |
|---|
| 71 | h3 a { |
|---|
| 72 | color: black; |
|---|
| 73 | } |
|---|
| 74 | h4 { |
|---|
| 75 | font-size: 10pt; |
|---|
| 76 | page-break-after: avoid; |
|---|
| 77 | } |
|---|
| 78 | h4 a { |
|---|
| 79 | color: black; |
|---|
| 80 | } |
|---|
| 81 | h5 { |
|---|
| 82 | font-size: 10pt; |
|---|
| 83 | page-break-after: avoid; |
|---|
| 84 | } |
|---|
| 85 | h5 a { |
|---|
| 86 | color: black; |
|---|
| 87 | } |
|---|
| 88 | img { |
|---|
| 89 | margin-left: 3em; |
|---|
| 90 | } |
|---|
| 91 | li { |
|---|
| 92 | margin-left: 2em; |
|---|
| 93 | margin-right: 2em; |
|---|
| 94 | } |
|---|
| 95 | ol { |
|---|
| 96 | margin-left: 2em; |
|---|
| 97 | margin-right: 2em; |
|---|
| 98 | } |
|---|
| 99 | ol p { |
|---|
| 100 | margin-left: 0em; |
|---|
| 101 | } |
|---|
| 102 | p { |
|---|
| 103 | margin-left: 2em; |
|---|
| 104 | margin-right: 2em; |
|---|
| 105 | } |
|---|
| 106 | pre { |
|---|
| 107 | margin-left: 3em; |
|---|
| 108 | background-color: lightyellow; |
|---|
| 109 | padding: .25em; |
|---|
| 110 | } |
|---|
| 111 | pre.text2 { |
|---|
| 112 | border-style: dotted; |
|---|
| 113 | border-width: 1px; |
|---|
| 114 | background-color: #f0f0f0; |
|---|
| 115 | width: 69em; |
|---|
| 116 | } |
|---|
| 117 | pre.inline { |
|---|
| 118 | background-color: white; |
|---|
| 119 | padding: 0em; |
|---|
| 120 | } |
|---|
| 121 | pre.text { |
|---|
| 122 | border-style: dotted; |
|---|
| 123 | border-width: 1px; |
|---|
| 124 | background-color: #f8f8f8; |
|---|
| 125 | width: 69em; |
|---|
| 126 | } |
|---|
| 127 | pre.drawing { |
|---|
| 128 | border-style: solid; |
|---|
| 129 | border-width: 1px; |
|---|
| 130 | background-color: #f8f8f8; |
|---|
| 131 | padding: 2em; |
|---|
| 132 | } |
|---|
| 133 | table { |
|---|
| 134 | margin-left: 2em; |
|---|
| 135 | } |
|---|
| 136 | table.header { |
|---|
| 137 | width: 95%; |
|---|
| 138 | font-size: 10pt; |
|---|
| 139 | color: white; |
|---|
| 140 | } |
|---|
| 141 | td.top { |
|---|
| 142 | vertical-align: top; |
|---|
| 143 | } |
|---|
| 144 | td.topnowrap { |
|---|
| 145 | vertical-align: top; |
|---|
| 146 | white-space: nowrap; |
|---|
| 147 | } |
|---|
| 148 | td.header { |
|---|
| 149 | background-color: gray; |
|---|
| 150 | width: 50%; |
|---|
| 151 | } |
|---|
| 152 | td.reference { |
|---|
| 153 | vertical-align: top; |
|---|
| 154 | white-space: nowrap; |
|---|
| 155 | padding-right: 1em; |
|---|
| 156 | } |
|---|
| 157 | thead { |
|---|
| 158 | display:table-header-group; |
|---|
| 159 | } |
|---|
| 160 | ul.toc { |
|---|
| 161 | list-style: none; |
|---|
| 162 | margin-left: 1.5em; |
|---|
| 163 | margin-right: 0em; |
|---|
| 164 | padding-left: 0em; |
|---|
| 165 | } |
|---|
| 166 | li.tocline0 { |
|---|
| 167 | line-height: 150%; |
|---|
| 168 | font-weight: bold; |
|---|
| 169 | font-size: 10pt; |
|---|
| 170 | margin-left: 0em; |
|---|
| 171 | margin-right: 0em; |
|---|
| 172 | } |
|---|
| 173 | li.tocline1 { |
|---|
| 174 | line-height: normal; |
|---|
| 175 | font-weight: normal; |
|---|
| 176 | font-size: 9pt; |
|---|
| 177 | margin-left: 0em; |
|---|
| 178 | margin-right: 0em; |
|---|
| 179 | } |
|---|
| 180 | li.tocline2 { |
|---|
| 181 | font-size: 0pt; |
|---|
| 182 | } |
|---|
| 183 | ul p { |
|---|
| 184 | margin-left: 0em; |
|---|
| 185 | } |
|---|
| 186 | ul.ind { |
|---|
| 187 | list-style: none; |
|---|
| 188 | margin-left: 1.5em; |
|---|
| 189 | margin-right: 0em; |
|---|
| 190 | padding-left: 0em; |
|---|
| 191 | } |
|---|
| 192 | li.indline0 { |
|---|
| 193 | font-weight: bold; |
|---|
| 194 | line-height: 200%; |
|---|
| 195 | margin-left: 0em; |
|---|
| 196 | margin-right: 0em; |
|---|
| 197 | } |
|---|
| 198 | li.indline1 { |
|---|
| 199 | font-weight: normal; |
|---|
| 200 | line-height: 150%; |
|---|
| 201 | margin-left: 0em; |
|---|
| 202 | margin-right: 0em; |
|---|
| 203 | } |
|---|
| 204 | .bcp14 { |
|---|
| 205 | font-style: normal; |
|---|
| 206 | text-transform: lowercase; |
|---|
| 207 | font-variant: small-caps; |
|---|
| 208 | } |
|---|
| 209 | .comment { |
|---|
| 210 | background-color: yellow; |
|---|
| 211 | } |
|---|
| 212 | .center { |
|---|
| 213 | text-align: center; |
|---|
| 214 | } |
|---|
| 215 | .error { |
|---|
| 216 | color: red; |
|---|
| 217 | font-style: italic; |
|---|
| 218 | font-weight: bold; |
|---|
| 219 | } |
|---|
| 220 | .figure { |
|---|
| 221 | font-weight: bold; |
|---|
| 222 | text-align: center; |
|---|
| 223 | font-size: 9pt; |
|---|
| 224 | } |
|---|
| 225 | .filename { |
|---|
| 226 | color: #333333; |
|---|
| 227 | font-weight: bold; |
|---|
| 228 | font-size: 12pt; |
|---|
| 229 | line-height: 21pt; |
|---|
| 230 | text-align: center; |
|---|
| 231 | } |
|---|
| 232 | .fn { |
|---|
| 233 | font-weight: bold; |
|---|
| 234 | } |
|---|
| 235 | .hidden { |
|---|
| 236 | display: none; |
|---|
| 237 | } |
|---|
| 238 | .left { |
|---|
| 239 | text-align: left; |
|---|
| 240 | } |
|---|
| 241 | .right { |
|---|
| 242 | text-align: right; |
|---|
| 243 | } |
|---|
| 244 | .title { |
|---|
| 245 | color: #990000; |
|---|
| 246 | font-size: 18pt; |
|---|
| 247 | line-height: 18pt; |
|---|
| 248 | font-weight: bold; |
|---|
| 249 | text-align: center; |
|---|
| 250 | margin-top: 36pt; |
|---|
| 251 | } |
|---|
| 252 | .vcardline { |
|---|
| 253 | display: block; |
|---|
| 254 | } |
|---|
| 255 | .warning { |
|---|
| 256 | font-size: 14pt; |
|---|
| 257 | background-color: yellow; |
|---|
| 258 | } |
|---|
| 259 | |
|---|
| 260 | |
|---|
| 261 | @media print { |
|---|
| 262 | .noprint { |
|---|
| 263 | display: none; |
|---|
| 264 | } |
|---|
| 265 | |
|---|
| 266 | a { |
|---|
| 267 | color: black; |
|---|
| 268 | text-decoration: none; |
|---|
| 269 | } |
|---|
| 270 | |
|---|
| 271 | table.header { |
|---|
| 272 | width: 90%; |
|---|
| 273 | } |
|---|
| 274 | |
|---|
| 275 | td.header { |
|---|
| 276 | width: 50%; |
|---|
| 277 | color: black; |
|---|
| 278 | background-color: white; |
|---|
| 279 | vertical-align: top; |
|---|
| 280 | font-size: 12pt; |
|---|
| 281 | } |
|---|
| 282 | |
|---|
| 283 | ul.toc a::after { |
|---|
| 284 | content: leader('.') target-counter(attr(href), page); |
|---|
| 285 | } |
|---|
| 286 | |
|---|
| 287 | a.iref { |
|---|
| 288 | content: target-counter(attr(href), page); |
|---|
| 289 | } |
|---|
| 290 | |
|---|
| 291 | .print2col { |
|---|
| 292 | column-count: 2; |
|---|
| 293 | -moz-column-count: 2; |
|---|
| 294 | column-fill: auto; |
|---|
| 295 | } |
|---|
| 296 | } |
|---|
| 297 | |
|---|
| 298 | @page { |
|---|
| 299 | @top-left { |
|---|
| 300 | content: "INTERNET DRAFT"; |
|---|
| 301 | } |
|---|
| 302 | @top-right { |
|---|
| 303 | content: "January 2008"; |
|---|
| 304 | } |
|---|
| 305 | @top-center { |
|---|
| 306 | content: "HTTP/1.1, Part 5"; |
|---|
| 307 | } |
|---|
| 308 | @bottom-left { |
|---|
| 309 | content: "Fielding, et al."; |
|---|
| 310 | } |
|---|
| 311 | @bottom-center { |
|---|
| 312 | content: "Standards Track"; |
|---|
| 313 | } |
|---|
| 314 | @bottom-right { |
|---|
| 315 | content: "[Page " counter(page) "]"; |
|---|
| 316 | } |
|---|
| 317 | } |
|---|
| 318 | |
|---|
| 319 | @page:first { |
|---|
| 320 | @top-left { |
|---|
| 321 | content: normal; |
|---|
| 322 | } |
|---|
| 323 | @top-right { |
|---|
| 324 | content: normal; |
|---|
| 325 | } |
|---|
| 326 | @top-center { |
|---|
| 327 | content: normal; |
|---|
| 328 | } |
|---|
| 329 | } |
|---|
| 330 | </style><link rel="Contents" href="#rfc.toc"> |
|---|
| 331 | <link rel="Author" href="#rfc.authors"> |
|---|
| 332 | <link rel="Copyright" href="#rfc.copyright"> |
|---|
| 333 | <link rel="Index" href="#rfc.index"> |
|---|
| 334 | <link rel="Chapter" title="1 Introduction" href="#rfc.section.1"> |
|---|
| 335 | <link rel="Chapter" title="2 Range Units" href="#rfc.section.2"> |
|---|
| 336 | <link rel="Chapter" title="3 Status Code Definitions" href="#rfc.section.3"> |
|---|
| 337 | <link rel="Chapter" title="4 Combining Byte Ranges" href="#rfc.section.4"> |
|---|
| 338 | <link rel="Chapter" title="5 Header Field Definitions" href="#rfc.section.5"> |
|---|
| 339 | <link rel="Chapter" title="6 IANA Considerations" href="#rfc.section.6"> |
|---|
| 340 | <link rel="Chapter" title="7 Security Considerations" href="#rfc.section.7"> |
|---|
| 341 | <link rel="Chapter" title="8 Acknowledgments" href="#rfc.section.8"> |
|---|
| 342 | <link rel="Chapter" href="#rfc.section.9" title="9 References"> |
|---|
| 343 | <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A"> |
|---|
| 344 | <link rel="Appendix" title="B Compatibility with Previous Versions" href="#rfc.section.B"> |
|---|
| 345 | <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> |
|---|
| 346 | <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.354, 2007/12/31 13:43:05, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> |
|---|
| 347 | <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> |
|---|
| 348 | <meta name="DC.Creator" content="Fielding, R."> |
|---|
| 349 | <meta name="DC.Creator" content="Gettys, J."> |
|---|
| 350 | <meta name="DC.Creator" content="Mogul, J."> |
|---|
| 351 | <meta name="DC.Creator" content="Frystyk, H."> |
|---|
| 352 | <meta name="DC.Creator" content="Masinter, L."> |
|---|
| 353 | <meta name="DC.Creator" content="Leach, P."> |
|---|
| 354 | <meta name="DC.Creator" content="Berners-Lee, T."> |
|---|
| 355 | <meta name="DC.Creator" content="Lafon, Y."> |
|---|
| 356 | <meta name="DC.Creator" content="Reschke, J. F."> |
|---|
| 357 | <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> |
|---|
| 358 | <meta name="DC.Date.Issued" scheme="ISO8601" content="2008-01"> |
|---|
| 359 | <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2068"> |
|---|
| 360 | <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> |
|---|
| 361 | <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests."> |
|---|
| 362 | </head> |
|---|
| 363 | <body> |
|---|
| 364 | <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1"> |
|---|
| 365 | <tr> |
|---|
| 366 | <td class="header left">Network Working Group</td> |
|---|
| 367 | <td class="header right">R. Fielding, Editor</td> |
|---|
| 368 | </tr> |
|---|
| 369 | <tr> |
|---|
| 370 | <td class="header left">Internet Draft</td> |
|---|
| 371 | <td class="header right">Day Software</td> |
|---|
| 372 | </tr> |
|---|
| 373 | <tr> |
|---|
| 374 | <td class="header left"> |
|---|
| 375 | <draft-ietf-httpbis-p5-range-latest> |
|---|
| 376 | |
|---|
| 377 | </td> |
|---|
| 378 | <td class="header right">J. Gettys</td> |
|---|
| 379 | </tr> |
|---|
| 380 | <tr> |
|---|
| 381 | <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2068">2068</a>, |
|---|
| 382 | <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) |
|---|
| 383 | </td> |
|---|
| 384 | <td class="header right">One Laptop per Child</td> |
|---|
| 385 | </tr> |
|---|
| 386 | <tr> |
|---|
| 387 | <td class="header left">Intended status: Standards Track</td> |
|---|
| 388 | <td class="header right">J. Mogul</td> |
|---|
| 389 | </tr> |
|---|
| 390 | <tr> |
|---|
| 391 | <td class="header left">Expires: July 2008</td> |
|---|
| 392 | <td class="header right">HP</td> |
|---|
| 393 | </tr> |
|---|
| 394 | <tr> |
|---|
| 395 | <td class="header left"></td> |
|---|
| 396 | <td class="header right">H. Frystyk</td> |
|---|
| 397 | </tr> |
|---|
| 398 | <tr> |
|---|
| 399 | <td class="header left"></td> |
|---|
| 400 | <td class="header right">Microsoft</td> |
|---|
| 401 | </tr> |
|---|
| 402 | <tr> |
|---|
| 403 | <td class="header left"></td> |
|---|
| 404 | <td class="header right">L. Masinter</td> |
|---|
| 405 | </tr> |
|---|
| 406 | <tr> |
|---|
| 407 | <td class="header left"></td> |
|---|
| 408 | <td class="header right">Adobe Systems</td> |
|---|
| 409 | </tr> |
|---|
| 410 | <tr> |
|---|
| 411 | <td class="header left"></td> |
|---|
| 412 | <td class="header right">P. Leach</td> |
|---|
| 413 | </tr> |
|---|
| 414 | <tr> |
|---|
| 415 | <td class="header left"></td> |
|---|
| 416 | <td class="header right">Microsoft</td> |
|---|
| 417 | </tr> |
|---|
| 418 | <tr> |
|---|
| 419 | <td class="header left"></td> |
|---|
| 420 | <td class="header right">T. Berners-Lee</td> |
|---|
| 421 | </tr> |
|---|
| 422 | <tr> |
|---|
| 423 | <td class="header left"></td> |
|---|
| 424 | <td class="header right">W3C/MIT</td> |
|---|
| 425 | </tr> |
|---|
| 426 | <tr> |
|---|
| 427 | <td class="header left"></td> |
|---|
| 428 | <td class="header right">Y. Lafon, Editor</td> |
|---|
| 429 | </tr> |
|---|
| 430 | <tr> |
|---|
| 431 | <td class="header left"></td> |
|---|
| 432 | <td class="header right">W3C</td> |
|---|
| 433 | </tr> |
|---|
| 434 | <tr> |
|---|
| 435 | <td class="header left"></td> |
|---|
| 436 | <td class="header right">J. F. Reschke, Editor</td> |
|---|
| 437 | </tr> |
|---|
| 438 | <tr> |
|---|
| 439 | <td class="header left"></td> |
|---|
| 440 | <td class="header right">greenbytes</td> |
|---|
| 441 | </tr> |
|---|
| 442 | <tr> |
|---|
| 443 | <td class="header left"></td> |
|---|
| 444 | <td class="header right">January 2008</td> |
|---|
| 445 | </tr> |
|---|
| 446 | </table> |
|---|
| 447 | <p class="title">HTTP/1.1, part 5: Range Requests and Partial Responses<br><span class="filename">draft-ietf-httpbis-p5-range-latest</span></p> |
|---|
| 448 | <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1> |
|---|
| 449 | <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she |
|---|
| 450 | is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section |
|---|
| 451 | 6 of BCP 79. |
|---|
| 452 | </p> |
|---|
| 453 | <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note |
|---|
| 454 | that other groups may also distribute working documents as Internet-Drafts. |
|---|
| 455 | </p> |
|---|
| 456 | <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other |
|---|
| 457 | documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work |
|---|
| 458 | in progress”. |
|---|
| 459 | </p> |
|---|
| 460 | <p>The list of current Internet-Drafts can be accessed at <<a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>>. |
|---|
| 461 | </p> |
|---|
| 462 | <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. |
|---|
| 463 | </p> |
|---|
| 464 | <p>This Internet-Draft will expire in July 2008.</p> |
|---|
| 465 | <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> |
|---|
| 466 | <p>Copyright © The IETF Trust (2008). All Rights Reserved.</p> |
|---|
| 467 | <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> |
|---|
| 468 | <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information |
|---|
| 469 | systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the |
|---|
| 470 | seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part |
|---|
| 471 | 5 defines range-specific requests and the rules for constructing and combining responses to those requests. |
|---|
| 472 | </p> |
|---|
| 473 | <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> |
|---|
| 474 | <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues |
|---|
| 475 | list is at <<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>> and related documents (including fancy diffs) can be found at <<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>>. |
|---|
| 476 | </p> |
|---|
| 477 | <hr class="noprint"> |
|---|
| 478 | <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1> |
|---|
| 479 | <ul class="toc"> |
|---|
| 480 | <li class="tocline0">1. <a href="#introduction">Introduction</a><ul class="toc"> |
|---|
| 481 | <li class="tocline1">1.1 <a href="#intro.requirements">Requirements</a></li> |
|---|
| 482 | </ul> |
|---|
| 483 | </li> |
|---|
| 484 | <li class="tocline0">2. <a href="#range.units">Range Units</a></li> |
|---|
| 485 | <li class="tocline0">3. <a href="#rfc.section.3">Status Code Definitions</a><ul class="toc"> |
|---|
| 486 | <li class="tocline1">3.1 <a href="#status.206">206 Partial Content</a></li> |
|---|
| 487 | <li class="tocline1">3.2 <a href="#status.416">416 Requested Range Not Satisfiable</a></li> |
|---|
| 488 | </ul> |
|---|
| 489 | </li> |
|---|
| 490 | <li class="tocline0">4. <a href="#combining.byte.ranges">Combining Byte Ranges</a></li> |
|---|
| 491 | <li class="tocline0">5. <a href="#header.fields">Header Field Definitions</a><ul class="toc"> |
|---|
| 492 | <li class="tocline1">5.1 <a href="#header.accept-ranges">Accept-Ranges</a></li> |
|---|
| 493 | <li class="tocline1">5.2 <a href="#header.content-range">Content-Range</a></li> |
|---|
| 494 | <li class="tocline1">5.3 <a href="#header.if-range">If-Range</a></li> |
|---|
| 495 | <li class="tocline1">5.4 <a href="#header.range">Range</a><ul class="toc"> |
|---|
| 496 | <li class="tocline1">5.4.1 <a href="#byte.ranges">Byte Ranges</a></li> |
|---|
| 497 | <li class="tocline1">5.4.2 <a href="#range.retrieval.requests">Range Retrieval Requests</a></li> |
|---|
| 498 | </ul> |
|---|
| 499 | </li> |
|---|
| 500 | </ul> |
|---|
| 501 | </li> |
|---|
| 502 | <li class="tocline0">6. <a href="#IANA.considerations">IANA Considerations</a></li> |
|---|
| 503 | <li class="tocline0">7. <a href="#security.considerations">Security Considerations</a></li> |
|---|
| 504 | <li class="tocline0">8. <a href="#ack">Acknowledgments</a></li> |
|---|
| 505 | <li class="tocline0">9. <a href="#rfc.references">References</a><ul class="toc"> |
|---|
| 506 | <li class="tocline1">9.1 <a href="#rfc.references.1">Normative References</a></li> |
|---|
| 507 | <li class="tocline1">9.2 <a href="#rfc.references.2">Informative References</a></li> |
|---|
| 508 | </ul> |
|---|
| 509 | </li> |
|---|
| 510 | <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li> |
|---|
| 511 | <li class="tocline0">A. <a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li> |
|---|
| 512 | <li class="tocline0">B. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc"> |
|---|
| 513 | <li class="tocline1">B.1 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li> |
|---|
| 514 | <li class="tocline1">B.2 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> |
|---|
| 515 | </ul> |
|---|
| 516 | </li> |
|---|
| 517 | <li class="tocline0">C. <a href="#rfc.section.C">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> |
|---|
| 518 | <li class="tocline1">C.1 <a href="#rfc.section.C.1">Since RFC2616</a></li> |
|---|
| 519 | <li class="tocline1">C.2 <a href="#rfc.section.C.2">Since draft-ietf-httpbis-p5-range-00</a></li> |
|---|
| 520 | </ul> |
|---|
| 521 | </li> |
|---|
| 522 | <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li> |
|---|
| 523 | <li class="tocline0"><a href="#rfc.index">Index</a></li> |
|---|
| 524 | </ul> |
|---|
| 525 | <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> <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. |
|---|
| 528 | </p> |
|---|
| 529 | <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a> <a id="intro.requirements" href="#intro.requirements">Requirements</a></h2> |
|---|
| 530 | <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" |
|---|
| 531 | in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>. |
|---|
| 532 | </p> |
|---|
| 533 | <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant." |
|---|
| 534 | </p> |
|---|
| 535 | <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="range.units" href="#range.units">Range Units</a></h1> |
|---|
| 536 | <p id="rfc.section.2.p.1">HTTP/1.1 allows a client to request that only part (a range of) the response entity be included within the response. HTTP/1.1 |
|---|
| 537 | uses range units in the Range (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section 5.4</a>) and Content-Range (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section 5.2</a>) header fields. An entity can be broken down into subranges according to various structural units. |
|---|
| 538 | </p> |
|---|
| 539 | <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span> range-unit = bytes-unit | other-range-unit |
|---|
| 540 | bytes-unit = "bytes" |
|---|
| 541 | other-range-unit = token |
|---|
| 542 | </pre><p id="rfc.section.2.p.3">The only range unit defined by HTTP/1.1 is "bytes". HTTP/1.1 implementations <em class="bcp14">MAY</em> ignore ranges specified using other units. |
|---|
| 543 | </p> |
|---|
| 544 | <p id="rfc.section.2.p.4">HTTP/1.1 has been designed to allow implementations of applications that do not depend on knowledge of ranges.</p> |
|---|
| 545 | <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> Status Code Definitions |
|---|
| 546 | </h1> |
|---|
| 547 | <div id="rfc.iref.3"></div> |
|---|
| 548 | <div id="rfc.iref.s.1"></div> |
|---|
| 549 | <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a> <a id="status.206" href="#status.206">206 Partial Content</a></h2> |
|---|
| 550 | <p id="rfc.section.3.1.p.1">The server has fulfilled the partial GET request for the resource. The request <em class="bcp14">MUST</em> have included a Range header field (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section 5.4</a>) indicating the desired range, and <em class="bcp14">MAY</em> have included an If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.1" title="If-Range">Section 5.3</a>) to make the request conditional. |
|---|
| 551 | </p> |
|---|
| 552 | <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields: |
|---|
| 553 | </p> |
|---|
| 554 | <ul> |
|---|
| 555 | <li>Either a Content-Range header field (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section 5.2</a>) indicating the range included with this response, or a multipart/byteranges Content-Type including Content-Range fields |
|---|
| 556 | for each part. If a Content-Length header field is present in the response, its value <em class="bcp14">MUST</em> match the actual number of OCTETs transmitted in the message-body. |
|---|
| 557 | </li> |
|---|
| 558 | <li>Date</li> |
|---|
| 559 | <li>ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request</li> |
|---|
| 560 | <li>Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same |
|---|
| 561 | variant |
|---|
| 562 | </li> |
|---|
| 563 | </ul> |
|---|
| 564 | <p id="rfc.section.3.1.p.3">If the 206 response is the result of an If-Range request, the response <em class="bcp14">SHOULD NOT</em> include other entity-headers. Otherwise, the response <em class="bcp14">MUST</em> include all of the entity-headers that would have been returned with a 200 (OK) response to the same request. |
|---|
| 565 | </p> |
|---|
| 566 | <p id="rfc.section.3.1.p.4">A cache <em class="bcp14">MUST NOT</em> combine a 206 response with other previously cached content if the ETag or Last-Modified headers do not match exactly, see <a href="#combining.byte.ranges" title="Combining Byte Ranges">4</a>. |
|---|
| 567 | </p> |
|---|
| 568 | <p id="rfc.section.3.1.p.5">A cache that does not support the Range and Content-Range headers <em class="bcp14">MUST NOT</em> cache 206 (Partial) responses. |
|---|
| 569 | </p> |
|---|
| 570 | <div id="rfc.iref.4"></div> |
|---|
| 571 | <div id="rfc.iref.s.2"></div> |
|---|
| 572 | <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h2> |
|---|
| 573 | <p id="rfc.section.3.2.p.1">A server <em class="bcp14">SHOULD</em> return a response with this status code if a request included a Range request-header field (<a href="#header.range" id="rfc.xref.header.range.3" title="Range">Section 5.4</a>), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request |
|---|
| 574 | did not include an If-Range request-header field. (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec |
|---|
| 575 | values were greater than the current length of the selected resource.) |
|---|
| 576 | </p> |
|---|
| 577 | <p id="rfc.section.3.2.p.2">When this status code is returned for a byte-range request, the response <em class="bcp14">SHOULD</em> include a Content-Range entity-header field specifying the current length of the selected resource (see <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section 5.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type. |
|---|
| 578 | </p> |
|---|
| 579 | <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="combining.byte.ranges" href="#combining.byte.ranges">Combining Byte Ranges</a></h1> |
|---|
| 580 | <p id="rfc.section.4.p.1">A response might transfer only a subrange of the bytes of an entity-body, either because the request included one or more |
|---|
| 581 | Range specifications, or because a connection was broken prematurely. After several such transfers, a cache might have received |
|---|
| 582 | several ranges of the same entity-body. |
|---|
| 583 | </p> |
|---|
| 584 | <p id="rfc.section.4.p.2">If a cache has a stored non-empty set of subranges for an entity, and an incoming response transfers another subrange, the |
|---|
| 585 | cache <em class="bcp14">MAY</em> combine the new subrange with the existing set if both the following conditions are met: |
|---|
| 586 | </p> |
|---|
| 587 | <ul> |
|---|
| 588 | <li>Both the incoming response and the cache entry have a cache validator.</li> |
|---|
| 589 | <li>The two cache validators match using the strong comparison function (see <a href="p4-conditional.html#weak.and.strong.validators" title="Weak and Strong Validators">Section 4</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>). |
|---|
| 590 | </li> |
|---|
| 591 | </ul> |
|---|
| 592 | <p id="rfc.section.4.p.3">If either requirement is not met, the cache <em class="bcp14">MUST</em> use only the most recent partial response (based on the Date values transmitted with every response, and using the incoming |
|---|
| 593 | response if these values are equal or missing), and <em class="bcp14">MUST</em> discard the other partial information. |
|---|
| 594 | </p> |
|---|
| 595 | <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="header.fields" href="#header.fields">Header Field Definitions</a></h1> |
|---|
| 596 | <p id="rfc.section.5.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to range requests and partial responses.</p> |
|---|
| 597 | <p id="rfc.section.5.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who |
|---|
| 598 | receives the entity. |
|---|
| 599 | </p> |
|---|
| 600 | <div id="rfc.iref.a.1"></div> |
|---|
| 601 | <div id="rfc.iref.h.1"></div> |
|---|
| 602 | <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a> <a id="header.accept-ranges" href="#header.accept-ranges">Accept-Ranges</a></h2> |
|---|
| 603 | <p id="rfc.section.5.1.p.1">The Accept-Ranges response-header field allows the server to indicate its acceptance of range requests for a resource:</p> |
|---|
| 604 | <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span> Accept-Ranges = "Accept-Ranges" ":" acceptable-ranges |
|---|
| 605 | acceptable-ranges = 1#range-unit | "none" |
|---|
| 606 | </pre><p id="rfc.section.5.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send |
|---|
| 607 | </p> |
|---|
| 608 | <div id="rfc.figure.u.3"></div><pre class="text"> Accept-Ranges: bytes |
|---|
| 609 | </pre><p id="rfc.section.5.1.p.5">but are not required to do so. Clients <em class="bcp14">MAY</em> generate byte-range requests without having received this header for the resource involved. Range units are defined in <a href="#range.units" title="Range Units">Section 2</a>. |
|---|
| 610 | </p> |
|---|
| 611 | <p id="rfc.section.5.1.p.6">Servers that do not accept any kind of range request for a resource <em class="bcp14">MAY</em> send |
|---|
| 612 | </p> |
|---|
| 613 | <div id="rfc.figure.u.4"></div><pre class="text"> Accept-Ranges: none |
|---|
| 614 | </pre><p id="rfc.section.5.1.p.8">to advise the client not to attempt a range request.</p> |
|---|
| 615 | <div id="rfc.iref.c.1"></div> |
|---|
| 616 | <div id="rfc.iref.h.2"></div> |
|---|
| 617 | <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a> <a id="header.content-range" href="#header.content-range">Content-Range</a></h2> |
|---|
| 618 | <p id="rfc.section.5.2.p.1">The Content-Range entity-header is sent with a partial entity-body to specify where in the full entity-body the partial body |
|---|
| 619 | should be applied. Range units are defined in <a href="#range.units" title="Range Units">Section 2</a>. |
|---|
| 620 | </p> |
|---|
| 621 | <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span> Content-Range = "Content-Range" ":" content-range-spec |
|---|
| 622 | |
|---|
| 623 | content-range-spec = byte-content-range-spec |
|---|
| 624 | byte-content-range-spec = bytes-unit SP |
|---|
| 625 | byte-range-resp-spec "/" |
|---|
| 626 | ( instance-length | "*" ) |
|---|
| 627 | |
|---|
| 628 | byte-range-resp-spec = (first-byte-pos "-" last-byte-pos) |
|---|
| 629 | | "*" |
|---|
| 630 | instance-length = 1*DIGIT |
|---|
| 631 | </pre><p id="rfc.section.5.2.p.3">The header <em class="bcp14">SHOULD</em> indicate the total length of the full entity-body, unless this length is unknown or difficult to determine. The asterisk "*" |
|---|
| 632 | character means that the instance-length is unknown at the time when the response was generated. |
|---|
| 633 | </p> |
|---|
| 634 | <p id="rfc.section.5.2.p.4">Unlike byte-ranges-specifier values (see <a href="#byte.ranges" title="Byte Ranges">Section 5.4.1</a>), a byte-range-resp-spec <em class="bcp14">MUST</em> only specify one range, and <em class="bcp14">MUST</em> contain absolute byte positions for both the first and last byte of the range. |
|---|
| 635 | </p> |
|---|
| 636 | <p id="rfc.section.5.2.p.5">A byte-content-range-spec with a byte-range-resp-spec whose last-byte-pos value is less than its first-byte-pos value, or |
|---|
| 637 | 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. |
|---|
| 638 | </p> |
|---|
| 639 | <p id="rfc.section.5.2.p.6">A server sending a response with status code 416 (Requested range not satisfiable) <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 |
|---|
| 640 | selected resource. A response with status code 206 (Partial Content) <em class="bcp14">MUST NOT</em> include a Content-Range field with a byte-range-resp-spec of "*". |
|---|
| 641 | </p> |
|---|
| 642 | <p id="rfc.section.5.2.p.7">Examples of byte-content-range-spec values, assuming that the entity contains a total of 1234 bytes: </p> |
|---|
| 643 | <ul> |
|---|
| 644 | <li>The first 500 bytes: |
|---|
| 645 | <div id="rfc.figure.u.6"></div><pre class="text"> bytes 0-499/1234 |
|---|
| 646 | </pre> </li> |
|---|
| 647 | <li>The second 500 bytes: |
|---|
| 648 | <div id="rfc.figure.u.7"></div><pre class="text"> bytes 500-999/1234 |
|---|
| 649 | </pre> </li> |
|---|
| 650 | <li>All except for the first 500 bytes: |
|---|
| 651 | <div id="rfc.figure.u.8"></div><pre class="text"> bytes 500-1233/1234 |
|---|
| 652 | </pre> </li> |
|---|
| 653 | <li>The last 500 bytes: |
|---|
| 654 | <div id="rfc.figure.u.9"></div><pre class="text"> bytes 734-1233/1234 |
|---|
| 655 | </pre> </li> |
|---|
| 656 | </ul> |
|---|
| 657 | <p id="rfc.section.5.2.p.8">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to |
|---|
| 658 | a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header, and |
|---|
| 659 | a Content-Length header showing the number of bytes actually transferred. For example, |
|---|
| 660 | </p> |
|---|
| 661 | <div id="rfc.figure.u.10"></div><pre class="text"> HTTP/1.1 206 Partial content |
|---|
| 662 | Date: Wed, 15 Nov 1995 06:25:24 GMT |
|---|
| 663 | Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT |
|---|
| 664 | Content-Range: bytes 21010-47021/47022 |
|---|
| 665 | Content-Length: 26012 |
|---|
| 666 | Content-Type: image/gif |
|---|
| 667 | </pre><p id="rfc.section.5.2.p.10">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping |
|---|
| 668 | ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges" |
|---|
| 669 | as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>. See <a href="#changes.from.rfc.2068" title="Changes from RFC 2068">Appendix B.1</a> for a compatibility issue. |
|---|
| 670 | </p> |
|---|
| 671 | <p id="rfc.section.5.2.p.11">A response to a request for a single range <em class="bcp14">MUST NOT</em> be sent using the multipart/byteranges media type. A response to a request for multiple ranges, whose result is a single range, <em class="bcp14">MAY</em> be sent as a multipart/byteranges media type with one part. A client that cannot decode a multipart/byteranges message <em class="bcp14">MUST NOT</em> ask for multiple byte-ranges in a single request. |
|---|
| 672 | </p> |
|---|
| 673 | <p id="rfc.section.5.2.p.12">When a client requests multiple byte-ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request. |
|---|
| 674 | </p> |
|---|
| 675 | <p id="rfc.section.5.2.p.13">If the server ignores a byte-range-spec because it is syntactically invalid, the server <em class="bcp14">SHOULD</em> treat the request as if the invalid Range header field did not exist. (Normally, this means return a 200 response containing |
|---|
| 676 | the full entity). |
|---|
| 677 | </p> |
|---|
| 678 | <p id="rfc.section.5.2.p.14">If the server receives a request (other than one including an If-Range request-header field) with an unsatisfiable Range request-header |
|---|
| 679 | field (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected |
|---|
| 680 | resource), it <em class="bcp14">SHOULD</em> return a response code of 416 (Requested range not satisfiable) (<a href="#status.416" id="rfc.xref.status.416.1" title="416 Requested Range Not Satisfiable">Section 3.2</a>). |
|---|
| 681 | </p> |
|---|
| 682 | <dl class="empty"> |
|---|
| 683 | <dd> <b>Note:</b> clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for |
|---|
| 684 | an unsatisfiable Range request-header, since not all servers implement this request-header. |
|---|
| 685 | </dd> |
|---|
| 686 | </dl> |
|---|
| 687 | <div id="rfc.iref.i.1"></div> |
|---|
| 688 | <div id="rfc.iref.h.3"></div> |
|---|
| 689 | <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a> <a id="header.if-range" href="#header.if-range">If-Range</a></h2> |
|---|
| 690 | <p id="rfc.section.5.3.p.1">If a client has a partial copy of an entity in its cache, and wishes to have an up-to-date copy of the entire entity in its |
|---|
| 691 | cache, it could use the Range request-header with a conditional GET (using either or both of If-Unmodified-Since and If-Match.) |
|---|
| 692 | However, if the condition fails because the entity has been modified, the client would then have to make a second request |
|---|
| 693 | to obtain the entire current entity-body. |
|---|
| 694 | </p> |
|---|
| 695 | <p id="rfc.section.5.3.p.2">The If-Range header allows a client to "short-circuit" the second request. Informally, its meaning is `if the entity is unchanged, |
|---|
| 696 | send me the part(s) that I am missing; otherwise, send me the entire new entity'. |
|---|
| 697 | </p> |
|---|
| 698 | <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.11"></span> If-Range = "If-Range" ":" ( entity-tag | HTTP-date ) |
|---|
| 699 | </pre><p id="rfc.section.5.3.p.4">If the client has no entity tag for an entity, but does have a Last-Modified date, it <em class="bcp14">MAY</em> use that date in an If-Range header. (The server can distinguish between a valid HTTP-date and any form of entity-tag by examining |
|---|
| 700 | no more than two characters.) The If-Range header <em class="bcp14">SHOULD</em> only be used together with a Range header, and <em class="bcp14">MUST</em> be ignored if the request does not include a Range header, or if the server does not support the sub-range operation. |
|---|
| 701 | </p> |
|---|
| 702 | <p id="rfc.section.5.3.p.5">If the entity tag given in the If-Range header matches the current entity tag for the entity, then the server <em class="bcp14">SHOULD</em> provide the specified sub-range of the entity using a 206 (Partial content) response. If the entity tag does not match, then |
|---|
| 703 | the server <em class="bcp14">SHOULD</em> return the entire entity using a 200 (OK) response. |
|---|
| 704 | </p> |
|---|
| 705 | <div id="rfc.iref.r.1"></div> |
|---|
| 706 | <div id="rfc.iref.h.4"></div> |
|---|
| 707 | <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a> <a id="header.range" href="#header.range">Range</a></h2> |
|---|
| 708 | <h3 id="rfc.section.5.4.1"><a href="#rfc.section.5.4.1">5.4.1</a> <a id="byte.ranges" href="#byte.ranges">Byte Ranges</a></h3> |
|---|
| 709 | <p id="rfc.section.5.4.1.p.1">Since all HTTP entities are represented in HTTP messages as sequences of bytes, the concept of a byte range is meaningful |
|---|
| 710 | for any HTTP entity. (However, not all clients and servers need to support byte-range operations.) |
|---|
| 711 | </p> |
|---|
| 712 | <p id="rfc.section.5.4.1.p.2">Byte range specifications in HTTP apply to the sequence of bytes in the entity-body (not necessarily the same as the message-body).</p> |
|---|
| 713 | <p id="rfc.section.5.4.1.p.3">A byte range operation <em class="bcp14">MAY</em> specify a single range of bytes, or a set of ranges within a single entity. |
|---|
| 714 | </p> |
|---|
| 715 | <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span> ranges-specifier = byte-ranges-specifier |
|---|
| 716 | byte-ranges-specifier = bytes-unit "=" byte-range-set |
|---|
| 717 | byte-range-set = 1#( byte-range-spec | suffix-byte-range-spec ) |
|---|
| 718 | byte-range-spec = first-byte-pos "-" [last-byte-pos] |
|---|
| 719 | first-byte-pos = 1*DIGIT |
|---|
| 720 | last-byte-pos = 1*DIGIT |
|---|
| 721 | </pre><p id="rfc.section.5.4.1.p.5">The first-byte-pos value in a byte-range-spec gives the byte-offset of the first byte in a range. The last-byte-pos value |
|---|
| 722 | gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start |
|---|
| 723 | at zero. |
|---|
| 724 | </p> |
|---|
| 725 | <p id="rfc.section.5.4.1.p.6">If the last-byte-pos value is present, it <em class="bcp14">MUST</em> be greater than or equal to the first-byte-pos in that byte-range-spec, or the byte-range-spec is syntactically invalid. The |
|---|
| 726 | recipient of a byte-range-set that includes one or more syntactically invalid byte-range-spec values <em class="bcp14">MUST</em> ignore the header field that includes that byte-range-set. |
|---|
| 727 | </p> |
|---|
| 728 | <p id="rfc.section.5.4.1.p.7">If the last-byte-pos value is absent, or if the value is greater than or equal to the current length of the entity-body, last-byte-pos |
|---|
| 729 | is taken to be equal to one less than the current length of the entity-body in bytes. |
|---|
| 730 | </p> |
|---|
| 731 | <p id="rfc.section.5.4.1.p.8">By its choice of last-byte-pos, a client can limit the number of bytes retrieved without knowing the size of the entity.</p> |
|---|
| 732 | <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span> suffix-byte-range-spec = "-" suffix-length |
|---|
| 733 | suffix-length = 1*DIGIT |
|---|
| 734 | </pre><p id="rfc.section.5.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the entity-body, of a length given by the suffix-length value. (That |
|---|
| 735 | is, this form specifies the last N bytes of an entity-body.) If the entity is shorter than the specified suffix-length, the |
|---|
| 736 | entire entity-body is used. |
|---|
| 737 | </p> |
|---|
| 738 | <p id="rfc.section.5.4.1.p.11">If a syntactically valid byte-range-set includes at least one byte-range-spec whose first-byte-pos is less than the current |
|---|
| 739 | length of the entity-body, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set is |
|---|
| 740 | satisfiable. Otherwise, the byte-range-set is unsatisfiable. If the byte-range-set is unsatisfiable, the server <em class="bcp14">SHOULD</em> return a response with a status of 416 (Requested range not satisfiable). Otherwise, the server <em class="bcp14">SHOULD</em> return a response with a status of 206 (Partial Content) containing the satisfiable ranges of the entity-body. |
|---|
| 741 | </p> |
|---|
| 742 | <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming an entity-body of length 10000): </p> |
|---|
| 743 | <ul> |
|---|
| 744 | <li>The first 500 bytes (byte offsets 0-499, inclusive): bytes=0-499</li> |
|---|
| 745 | <li>The second 500 bytes (byte offsets 500-999, inclusive): bytes=500-999</li> |
|---|
| 746 | <li>The final 500 bytes (byte offsets 9500-9999, inclusive): bytes=-500</li> |
|---|
| 747 | <li>Or bytes=9500-</li> |
|---|
| 748 | <li>The first and last bytes only (bytes 0 and 9999): bytes=0-0,-1</li> |
|---|
| 749 | <li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive): <br> bytes=500-600,601-999<br> bytes=500-700,601-999 |
|---|
| 750 | </li> |
|---|
| 751 | </ul> |
|---|
| 752 | <h3 id="rfc.section.5.4.2"><a href="#rfc.section.5.4.2">5.4.2</a> <a id="range.retrieval.requests" href="#range.retrieval.requests">Range Retrieval Requests</a></h3> |
|---|
| 753 | <p id="rfc.section.5.4.2.p.1">HTTP retrieval requests using conditional or unconditional GET methods <em class="bcp14">MAY</em> request one or more sub-ranges of the entity, instead of the entire entity, using the Range request header, which applies |
|---|
| 754 | to the entity returned as the result of the request: |
|---|
| 755 | </p> |
|---|
| 756 | <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.20"></span> Range = "Range" ":" ranges-specifier |
|---|
| 757 | </pre><p id="rfc.section.5.4.2.p.3">A server <em class="bcp14">MAY</em> ignore the Range header. However, HTTP/1.1 origin servers and intermediate caches ought to support byte ranges when possible, |
|---|
| 758 | since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large |
|---|
| 759 | entities. |
|---|
| 760 | </p> |
|---|
| 761 | <p id="rfc.section.5.4.2.p.4">If the server supports the Range header and the specified range or ranges are appropriate for the entity: </p> |
|---|
| 762 | <ul> |
|---|
| 763 | <li>The presence of a Range header in an unconditional GET modifies what is returned if the GET is otherwise successful. In other |
|---|
| 764 | words, the response carries a status code of 206 (Partial Content) instead of 200 (OK). |
|---|
| 765 | </li> |
|---|
| 766 | <li>The presence of a Range header in a conditional GET (a request using one or both of If-Modified-Since and If-None-Match, or |
|---|
| 767 | one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition |
|---|
| 768 | is true. It does not affect the 304 (Not Modified) response returned if the conditional is false. |
|---|
| 769 | </li> |
|---|
| 770 | </ul> |
|---|
| 771 | <p id="rfc.section.5.4.2.p.5">In some cases, it might be more appropriate to use the If-Range header (see <a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section 5.3</a>) in addition to the Range header. |
|---|
| 772 | </p> |
|---|
| 773 | <p id="rfc.section.5.4.2.p.6">If a proxy that supports ranges receives a Range request, forwards the request to an inbound server, and receives an entire |
|---|
| 774 | entity in reply, it <em class="bcp14">SHOULD</em> only return the requested range to its client. It <em class="bcp14">SHOULD</em> store the entire received response in its cache if that is consistent with its cache allocation policies. |
|---|
| 775 | </p> |
|---|
| 776 | <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> |
|---|
| 777 | <p id="rfc.section.6.p.1">TBD.</p> |
|---|
| 778 | <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> |
|---|
| 779 | <p id="rfc.section.7.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. |
|---|
| 780 | </p> |
|---|
| 781 | <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> <a id="ack" href="#ack">Acknowledgments</a></h1> |
|---|
| 782 | <p id="rfc.section.8.p.1">Most of the specification of ranges is based on work originally done by Ari Luotonen and John Franks, with additional input |
|---|
| 783 | from Steve Zilles. |
|---|
| 784 | </p> |
|---|
| 785 | <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References |
|---|
| 786 | </h1> |
|---|
| 787 | <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References |
|---|
| 788 | </h2> |
|---|
| 789 | <table summary="Normative References"> |
|---|
| 790 | <tr> |
|---|
| 791 | <td class="reference"><b id="Part1">[Part1]</b></td> |
|---|
| 792 | <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), January 2008. |
|---|
| 793 | </td> |
|---|
| 794 | </tr> |
|---|
| 795 | <tr> |
|---|
| 796 | <td class="reference"><b id="Part4">[Part4]</b></td> |
|---|
| 797 | <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), January 2008. |
|---|
| 798 | </td> |
|---|
| 799 | </tr> |
|---|
| 800 | <tr> |
|---|
| 801 | <td class="reference"><b id="RFC2046">[RFC2046]</b></td> |
|---|
| 802 | <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC 2046, November 1996. |
|---|
| 803 | </td> |
|---|
| 804 | </tr> |
|---|
| 805 | <tr> |
|---|
| 806 | <td class="reference"><b id="RFC2119">[RFC2119]</b></td> |
|---|
| 807 | <td class="top"><a title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP 14, RFC 2119, March 1997. |
|---|
| 808 | </td> |
|---|
| 809 | </tr> |
|---|
| 810 | </table> |
|---|
| 811 | <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References |
|---|
| 812 | </h2> |
|---|
| 813 | <table summary="Informative References"> |
|---|
| 814 | <tr> |
|---|
| 815 | <td class="reference"><b id="RFC2616">[RFC2616]</b></td> |
|---|
| 816 | <td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC 2616, June 1999. |
|---|
| 817 | </td> |
|---|
| 818 | </tr> |
|---|
| 819 | </table> |
|---|
| 820 | <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1> |
|---|
| 821 | <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span> |
|---|
| 822 | (editor) |
|---|
| 823 | <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Day Software</span><span class="adr"><span class="street-address vcardline">23 Corporate Plaza DR, Suite 280</span><span class="vcardline"><span class="locality">Newport Beach</span>, <span class="region">CA</span> <span class="postal-code">92660</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel">Phone: <a href="tel:+1-949-706-5300"><span class="value">+1-949-706-5300</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1-949-706-5305"><span class="value">+1-949-706-5305</span></a></span><span class="vcardline">EMail: <a><span class="email">fielding@gbiv.com</span></a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/" class="url">http://roy.gbiv.com/</a></span></address> |
|---|
| 824 | <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">One Laptop per Child</span><span class="adr"><span class="street-address vcardline">21 Oak Knoll Road</span><span class="vcardline"><span class="locality">Carlisle</span>, <span class="region">MA</span> <span class="postal-code">01741</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">jg@laptop.org</span></a></span><span class="vcardline">URI: <a href="http://www.laptop.org/" class="url">http://www.laptop.org/</a></span></address> |
|---|
| 825 | <address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Hewlett-Packard Company</span><span class="adr"><span class="street-address vcardline">HP Labs, Large Scale Systems Group</span><span class="street-address vcardline">1501 Page Mill Road, MS 1177</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">CA</span> <span class="postal-code">94304</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">JeffMogul@acm.org</span></a></span></address> |
|---|
| 826 | <address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span> <span class="postal-code">98052</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">henrikn@microsoft.com</span></a></span></address> |
|---|
| 827 | <address class="vcard"><span class="vcardline"><span class="fn">Larry Masinter</span><span class="n hidden"><span class="family-name">Masinter</span><span class="given-name">Larry</span></span></span><span class="org vcardline">Adobe Systems, Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span> <span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">LMM@acm.org</span></a></span><span class="vcardline">URI: <a href="http://larry.masinter.net/" class="url">http://larry.masinter.net/</a></span></address> |
|---|
| 828 | <address class="vcard"><span class="vcardline"><span class="fn">Paul J. Leach</span><span class="n hidden"><span class="family-name">Leach</span><span class="given-name">Paul J.</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span> <span class="postal-code">98052</span></span></span><span class="vcardline">EMail: <a><span class="email">paulle@microsoft.com</span></a></span></address> |
|---|
| 829 | <address class="vcard"><span class="vcardline"><span class="fn">Tim Berners-Lee</span><span class="n hidden"><span class="family-name">Berners-Lee</span><span class="given-name">Tim</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Computer Science and Artificial Intelligence Laboratory</span><span class="street-address vcardline">The Stata Center, Building 32</span><span class="street-address vcardline">32 Vassar Street</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span> <span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">timbl@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.w3.org/People/Berners-Lee/" class="url">http://www.w3.org/People/Berners-Lee/</a></span></address> |
|---|
| 830 | <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span> |
|---|
| 831 | (editor) |
|---|
| 832 | <span class="n hidden"><span class="family-name">Lafon</span><span class="given-name">Yves</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">W3C / ERCIM</span><span class="street-address vcardline">2004, rte des Lucioles</span><span class="vcardline"><span class="locality">Sophia-Antipolis</span>, <span class="region">AM</span> <span class="postal-code">06902</span></span><span class="country-name vcardline">France</span></span><span class="vcardline">EMail: <a><span class="email">ylafon@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.raubacapeu.net/people/yves/" class="url">http://www.raubacapeu.net/people/yves/</a></span></address> |
|---|
| 833 | <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span> |
|---|
| 834 | (editor) |
|---|
| 835 | <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span> <span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">EMail: <a><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address> |
|---|
| 836 | <div id="rfc.iref.m.1"></div> |
|---|
| 837 | <div id="rfc.iref.m.2"></div> |
|---|
| 838 | <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a> <a id="internet.media.type.multipart.byteranges" href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></h1> |
|---|
| 839 | <p id="rfc.section.A.p.1">When an HTTP 206 (Partial Content) response message includes the content of multiple ranges (a response to a request for multiple |
|---|
| 840 | non-overlapping ranges), these are transmitted as a multipart message-body. The media type for this purpose is called "multipart/byteranges". |
|---|
| 841 | </p> |
|---|
| 842 | <p id="rfc.section.A.p.2">The multipart/byteranges media type includes two or more parts, each with its own Content-Type and Content-Range fields. The |
|---|
| 843 | required boundary parameter specifies the boundary string used to separate each body-part. |
|---|
| 844 | </p> |
|---|
| 845 | <p id="rfc.section.A.p.3"> </p> |
|---|
| 846 | <dl> |
|---|
| 847 | <dt>Media Type name:</dt> |
|---|
| 848 | <dd>multipart</dd> |
|---|
| 849 | <dt>Media subtype name:</dt> |
|---|
| 850 | <dd>byteranges</dd> |
|---|
| 851 | <dt>Required parameters:</dt> |
|---|
| 852 | <dd>boundary</dd> |
|---|
| 853 | <dt>Optional parameters:</dt> |
|---|
| 854 | <dd>none</dd> |
|---|
| 855 | <dt>Encoding considerations:</dt> |
|---|
| 856 | <dd>only "7bit", "8bit", or "binary" are permitted</dd> |
|---|
| 857 | <dt>Security considerations:</dt> |
|---|
| 858 | <dd>none</dd> |
|---|
| 859 | </dl> |
|---|
| 860 | <div id="rfc.figure.u.15"></div> |
|---|
| 861 | <p>For example:</p><pre class="text"> HTTP/1.1 206 Partial Content |
|---|
| 862 | Date: Wed, 15 Nov 1995 06:25:24 GMT |
|---|
| 863 | Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT |
|---|
| 864 | Content-type: multipart/byteranges; boundary=THIS_STRING_SEPARATES |
|---|
| 865 | |
|---|
| 866 | --THIS_STRING_SEPARATES |
|---|
| 867 | Content-type: application/pdf |
|---|
| 868 | Content-range: bytes 500-999/8000 |
|---|
| 869 | |
|---|
| 870 | ...the first range... |
|---|
| 871 | --THIS_STRING_SEPARATES |
|---|
| 872 | Content-type: application/pdf |
|---|
| 873 | Content-range: bytes 7000-7999/8000 |
|---|
| 874 | |
|---|
| 875 | ...the second range |
|---|
| 876 | --THIS_STRING_SEPARATES-- |
|---|
| 877 | </pre><p id="rfc.section.A.p.5">Notes: </p> |
|---|
| 878 | <ol> |
|---|
| 879 | <li>Additional CRLFs may precede the first boundary string in the entity.</li> |
|---|
| 880 | <li>Although <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> permits the boundary string to be quoted, some existing implementations handle a quoted boundary string incorrectly. |
|---|
| 881 | </li> |
|---|
| 882 | <li>A number of browsers and servers were coded to an early draft of the byteranges specification to use a media type of multipart/x-byteranges<span id="rfc.iref.m.3"></span><span id="rfc.iref.m.4"></span>, which is almost, but not quite compatible with the version documented in HTTP/1.1. |
|---|
| 883 | </li> |
|---|
| 884 | </ol> |
|---|
| 885 | <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1> |
|---|
| 886 | <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a> <a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2> |
|---|
| 887 | <p id="rfc.section.B.1.p.1">There are situations where a server (especially a proxy) does not know the full length of a response but is capable of serving |
|---|
| 888 | a byterange request. We therefore need a mechanism to allow byteranges with a content-range not indicating the full length |
|---|
| 889 | of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section 5.2</a>) |
|---|
| 890 | </p> |
|---|
| 891 | <p id="rfc.section.B.1.p.2">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send |
|---|
| 892 | needed headers in a 206 response, this problem can be avoided. |
|---|
| 893 | </p> |
|---|
| 894 | <p id="rfc.section.B.1.p.3">Fix problem with unsatisfiable range requests; there are two cases: syntactic problems, and range doesn't exist in the document. |
|---|
| 895 | The 416 status code was needed to resolve this ambiguity needed to indicate an error for a byte range request that falls outside |
|---|
| 896 | of the actual contents of a document. (Section <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">3.2</a>, <a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">5.2</a>) |
|---|
| 897 | </p> |
|---|
| 898 | <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> |
|---|
| 899 | <p id="rfc.section.B.2.p.1">Clarify that it is not ok to use a weak cache validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section 3.1</a>) |
|---|
| 900 | </p> |
|---|
| 901 | <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> Change Log (to be removed by RFC Editor before publication) |
|---|
| 902 | </h1> |
|---|
| 903 | <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a> Since RFC2616 |
|---|
| 904 | </h2> |
|---|
| 905 | <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>. |
|---|
| 906 | </p> |
|---|
| 907 | <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a> Since draft-ietf-httpbis-p5-range-00 |
|---|
| 908 | </h2> |
|---|
| 909 | <p id="rfc.section.C.2.p.1">Closed issues: </p> |
|---|
| 910 | <ul> |
|---|
| 911 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/18">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/18</a>>: "Cache validators in 206 responses" (<<a href="http://purl.org/NET/http-errata#ifrange206">http://purl.org/NET/http-errata#ifrange206</a>>) |
|---|
| 912 | </li> |
|---|
| 913 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/86">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/86</a>>: "Normative up-to-date references" |
|---|
| 914 | </li> |
|---|
| 915 | </ul> |
|---|
| 916 | <p id="rfc.section.C.2.p.2">Other changes: </p> |
|---|
| 917 | <ul> |
|---|
| 918 | <li>Categorize references as "Normative" or "Informative".</li> |
|---|
| 919 | </ul> |
|---|
| 920 | <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> |
|---|
| 921 | <p>Copyright © The IETF Trust (2008).</p> |
|---|
| 922 | <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the |
|---|
| 923 | authors retain all their rights. |
|---|
| 924 | </p> |
|---|
| 925 | <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION |
|---|
| 926 | HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE |
|---|
| 927 | DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN |
|---|
| 928 | WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
|---|
| 929 | </p> |
|---|
| 930 | <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1> |
|---|
| 931 | <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might |
|---|
| 932 | be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any |
|---|
| 933 | license under such rights might or might not be available; nor does it represent that it has made any independent effort to |
|---|
| 934 | identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and |
|---|
| 935 | BCP 79. |
|---|
| 936 | </p> |
|---|
| 937 | <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result |
|---|
| 938 | of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users |
|---|
| 939 | of this specification can be obtained from the IETF on-line IPR repository at <<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>>. |
|---|
| 940 | </p> |
|---|
| 941 | <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary |
|---|
| 942 | rights that may cover technology that may be required to implement this standard. Please address the information to the IETF |
|---|
| 943 | at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>. |
|---|
| 944 | </p> |
|---|
| 945 | <h1>Acknowledgement</h1> |
|---|
| 946 | <p>Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).</p> |
|---|
| 947 | <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> |
|---|
| 948 | <p class="noprint"><a href="#rfc.index.2">2</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> |
|---|
| 949 | </p> |
|---|
| 950 | <div class="print2col"> |
|---|
| 951 | <ul class="ind"> |
|---|
| 952 | <li class="indline0"><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul class="ind"> |
|---|
| 953 | <li class="indline1">206 Partial Content (status code) <a class="iref" href="#rfc.iref.3"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">B.2</a></li> |
|---|
| 954 | </ul> |
|---|
| 955 | </li> |
|---|
| 956 | <li class="indline0"><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul class="ind"> |
|---|
| 957 | <li class="indline1">416 Requested Range Not Satisfiable (status code) <a class="iref" href="#rfc.iref.4"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.416.1">5.2</a>, <a class="iref" href="#rfc.xref.status.416.2">B.1</a></li> |
|---|
| 958 | </ul> |
|---|
| 959 | </li> |
|---|
| 960 | <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind"> |
|---|
| 961 | <li class="indline1">Accept-Ranges header <a class="iref" href="#rfc.iref.a.1"><b>5.1</b></a></li> |
|---|
| 962 | </ul> |
|---|
| 963 | </li> |
|---|
| 964 | <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind"> |
|---|
| 965 | <li class="indline1">Content-Range header <a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.c.1"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a></li> |
|---|
| 966 | </ul> |
|---|
| 967 | </li> |
|---|
| 968 | <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind"> |
|---|
| 969 | <li class="indline1"><tt>Grammar</tt> |
|---|
| 970 | <ul class="ind"> |
|---|
| 971 | <li class="indline1"><tt>Accept-Ranges</tt> <a class="iref" href="#rfc.iref.g.4"><b>5.1</b></a></li> |
|---|
| 972 | <li class="indline1"><tt>acceptable-ranges</tt> <a class="iref" href="#rfc.iref.g.5"><b>5.1</b></a></li> |
|---|
| 973 | <li class="indline1"><tt>byte-content-range-spec</tt> <a class="iref" href="#rfc.iref.g.8"><b>5.2</b></a></li> |
|---|
| 974 | <li class="indline1"><tt>byte-range-resp-spec</tt> <a class="iref" href="#rfc.iref.g.9"><b>5.2</b></a></li> |
|---|
| 975 | <li class="indline1"><tt>byte-range-set</tt> <a class="iref" href="#rfc.iref.g.14"><b>5.4.1</b></a></li> |
|---|
| 976 | <li class="indline1"><tt>byte-range-spec</tt> <a class="iref" href="#rfc.iref.g.15"><b>5.4.1</b></a></li> |
|---|
| 977 | <li class="indline1"><tt>byte-ranges-specifier</tt> <a class="iref" href="#rfc.iref.g.13"><b>5.4.1</b></a></li> |
|---|
| 978 | <li class="indline1"><tt>bytes-unit</tt> <a class="iref" href="#rfc.iref.g.2"><b>2</b></a></li> |
|---|
| 979 | <li class="indline1"><tt>Content-Range</tt> <a class="iref" href="#rfc.iref.g.6"><b>5.2</b></a></li> |
|---|
| 980 | <li class="indline1"><tt>content-range-spec</tt> <a class="iref" href="#rfc.iref.g.7"><b>5.2</b></a></li> |
|---|
| 981 | <li class="indline1"><tt>first-byte-pos</tt> <a class="iref" href="#rfc.iref.g.16"><b>5.4.1</b></a></li> |
|---|
| 982 | <li class="indline1"><tt>If-Range</tt> <a class="iref" href="#rfc.iref.g.11"><b>5.3</b></a></li> |
|---|
| 983 | <li class="indline1"><tt>instance-length</tt> <a class="iref" href="#rfc.iref.g.10"><b>5.2</b></a></li> |
|---|
| 984 | <li class="indline1"><tt>last-byte-pos</tt> <a class="iref" href="#rfc.iref.g.17"><b>5.4.1</b></a></li> |
|---|
| 985 | <li class="indline1"><tt>other-range-unit</tt> <a class="iref" href="#rfc.iref.g.3"><b>2</b></a></li> |
|---|
| 986 | <li class="indline1"><tt>Range</tt> <a class="iref" href="#rfc.iref.g.20"><b>5.4.2</b></a></li> |
|---|
| 987 | <li class="indline1"><tt>range-unit</tt> <a class="iref" href="#rfc.iref.g.1"><b>2</b></a></li> |
|---|
| 988 | <li class="indline1"><tt>ranges-specifier</tt> <a class="iref" href="#rfc.iref.g.12"><b>5.4.1</b></a></li> |
|---|
| 989 | <li class="indline1"><tt>suffix-byte-range-spec</tt> <a class="iref" href="#rfc.iref.g.18"><b>5.4.1</b></a></li> |
|---|
| 990 | <li class="indline1"><tt>suffix-length</tt> <a class="iref" href="#rfc.iref.g.19"><b>5.4.1</b></a></li> |
|---|
| 991 | </ul> |
|---|
| 992 | </li> |
|---|
| 993 | </ul> |
|---|
| 994 | </li> |
|---|
| 995 | <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind"> |
|---|
| 996 | <li class="indline1">Headers |
|---|
| 997 | <ul class="ind"> |
|---|
| 998 | <li class="indline1">Accept-Ranges <a class="iref" href="#rfc.iref.h.1"><b>5.1</b></a></li> |
|---|
| 999 | <li class="indline1">Content-Range <a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a></li> |
|---|
| 1000 | <li class="indline1">If-Range <a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.iref.h.3"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">5.4.2</a></li> |
|---|
| 1001 | <li class="indline1">Range <a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.range.3">3.2</a>, <a class="iref" href="#rfc.iref.h.4"><b>5.4</b></a></li> |
|---|
| 1002 | </ul> |
|---|
| 1003 | </li> |
|---|
| 1004 | </ul> |
|---|
| 1005 | </li> |
|---|
| 1006 | <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind"> |
|---|
| 1007 | <li class="indline1">If-Range header <a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.iref.i.1"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">5.4.2</a></li> |
|---|
| 1008 | </ul> |
|---|
| 1009 | </li> |
|---|
| 1010 | <li class="indline0"><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul class="ind"> |
|---|
| 1011 | <li class="indline1">Media Type |
|---|
| 1012 | <ul class="ind"> |
|---|
| 1013 | <li class="indline1">multipart/byteranges <a class="iref" href="#rfc.iref.m.1"><b>A</b></a></li> |
|---|
| 1014 | <li class="indline1">multipart/x-byteranges <a class="iref" href="#rfc.iref.m.4">A</a></li> |
|---|
| 1015 | </ul> |
|---|
| 1016 | </li> |
|---|
| 1017 | <li class="indline1">multipart/byteranges Media Type <a class="iref" href="#rfc.iref.m.2"><b>A</b></a></li> |
|---|
| 1018 | <li class="indline1">multipart/x-byteranges Media Type <a class="iref" href="#rfc.iref.m.3">A</a></li> |
|---|
| 1019 | </ul> |
|---|
| 1020 | </li> |
|---|
| 1021 | <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> |
|---|
| 1022 | <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">7</a>, <a class="iref" href="#Part1"><b>9.1</b></a></li> |
|---|
| 1023 | <li class="indline1"><em>Part4</em> <a class="iref" href="#rfc.xref.Part4.1">4</a>, <a class="iref" href="#Part4"><b>9.1</b></a><ul class="ind"> |
|---|
| 1024 | <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part4.1">4</a></li> |
|---|
| 1025 | </ul> |
|---|
| 1026 | </li> |
|---|
| 1027 | </ul> |
|---|
| 1028 | </li> |
|---|
| 1029 | <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind"> |
|---|
| 1030 | <li class="indline1">Range header <a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.range.3">3.2</a>, <a class="iref" href="#rfc.iref.r.1"><b>5.4</b></a></li> |
|---|
| 1031 | <li class="indline1"><em>RFC2046</em> <a class="iref" href="#RFC2046"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC2046.1">A</a></li> |
|---|
| 1032 | <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>9.1</b></a></li> |
|---|
| 1033 | <li class="indline1"><em>RFC2616</em> <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> |
|---|
| 1034 | </ul> |
|---|
| 1035 | </li> |
|---|
| 1036 | <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind"> |
|---|
| 1037 | <li class="indline1">Status Codes |
|---|
| 1038 | <ul class="ind"> |
|---|
| 1039 | <li class="indline1">206 Partial Content <a class="iref" href="#rfc.iref.s.1"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.206.1">B.2</a></li> |
|---|
| 1040 | <li class="indline1">416 Requested Range Not Satisfiable <a class="iref" href="#rfc.iref.s.2"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.416.1">5.2</a>, <a class="iref" href="#rfc.xref.status.416.2">B.1</a></li> |
|---|
| 1041 | </ul> |
|---|
| 1042 | </li> |
|---|
| 1043 | </ul> |
|---|
| 1044 | </li> |
|---|
| 1045 | </ul> |
|---|
| 1046 | </div> |
|---|
| 1047 | </body> |
|---|
| 1048 | </html> |
|---|
![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
