| 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 http://dublincore.org/documents/2008/08/04/dc-html/"> |
|---|
| 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 | div.note { |
|---|
| 33 | margin-left: 2em; |
|---|
| 34 | } |
|---|
| 35 | dd { |
|---|
| 36 | margin-right: 2em; |
|---|
| 37 | } |
|---|
| 38 | dl { |
|---|
| 39 | margin-left: 2em; |
|---|
| 40 | } |
|---|
| 41 | |
|---|
| 42 | ul.empty { |
|---|
| 43 | list-style-type: none; |
|---|
| 44 | } |
|---|
| 45 | ul.empty li { |
|---|
| 46 | margin-top: .5em; |
|---|
| 47 | } |
|---|
| 48 | dl p { |
|---|
| 49 | margin-left: 0em; |
|---|
| 50 | } |
|---|
| 51 | dt { |
|---|
| 52 | margin-top: .5em; |
|---|
| 53 | } |
|---|
| 54 | h1 { |
|---|
| 55 | font-size: 14pt; |
|---|
| 56 | line-height: 21pt; |
|---|
| 57 | page-break-after: avoid; |
|---|
| 58 | } |
|---|
| 59 | h1.np { |
|---|
| 60 | page-break-before: always; |
|---|
| 61 | } |
|---|
| 62 | h1 a { |
|---|
| 63 | color: #333333; |
|---|
| 64 | } |
|---|
| 65 | h2 { |
|---|
| 66 | font-size: 12pt; |
|---|
| 67 | line-height: 15pt; |
|---|
| 68 | page-break-after: avoid; |
|---|
| 69 | } |
|---|
| 70 | h3, h4, h5, h6 { |
|---|
| 71 | font-size: 10pt; |
|---|
| 72 | page-break-after: avoid; |
|---|
| 73 | } |
|---|
| 74 | h2 a, h3 a, h4 a, h5 a, h6 a { |
|---|
| 75 | color: black; |
|---|
| 76 | } |
|---|
| 77 | img { |
|---|
| 78 | margin-left: 3em; |
|---|
| 79 | } |
|---|
| 80 | li { |
|---|
| 81 | margin-left: 2em; |
|---|
| 82 | margin-right: 2em; |
|---|
| 83 | } |
|---|
| 84 | ol { |
|---|
| 85 | margin-left: 2em; |
|---|
| 86 | margin-right: 2em; |
|---|
| 87 | } |
|---|
| 88 | ol.la { |
|---|
| 89 | list-style-type: lower-alpha; |
|---|
| 90 | } |
|---|
| 91 | ol.ua { |
|---|
| 92 | list-style-type: upper-alpha; |
|---|
| 93 | } |
|---|
| 94 | ol p { |
|---|
| 95 | margin-left: 0em; |
|---|
| 96 | } |
|---|
| 97 | p { |
|---|
| 98 | margin-left: 2em; |
|---|
| 99 | margin-right: 2em; |
|---|
| 100 | } |
|---|
| 101 | pre { |
|---|
| 102 | margin-left: 3em; |
|---|
| 103 | background-color: lightyellow; |
|---|
| 104 | padding: .25em; |
|---|
| 105 | } |
|---|
| 106 | pre.text2 { |
|---|
| 107 | border-style: dotted; |
|---|
| 108 | border-width: 1px; |
|---|
| 109 | background-color: #f0f0f0; |
|---|
| 110 | width: 69em; |
|---|
| 111 | } |
|---|
| 112 | pre.inline { |
|---|
| 113 | background-color: white; |
|---|
| 114 | padding: 0em; |
|---|
| 115 | } |
|---|
| 116 | pre.text { |
|---|
| 117 | border-style: dotted; |
|---|
| 118 | border-width: 1px; |
|---|
| 119 | background-color: #f8f8f8; |
|---|
| 120 | width: 69em; |
|---|
| 121 | } |
|---|
| 122 | pre.drawing { |
|---|
| 123 | border-style: solid; |
|---|
| 124 | border-width: 1px; |
|---|
| 125 | background-color: #f8f8f8; |
|---|
| 126 | padding: 2em; |
|---|
| 127 | } |
|---|
| 128 | table { |
|---|
| 129 | margin-left: 2em; |
|---|
| 130 | } |
|---|
| 131 | table.tt { |
|---|
| 132 | vertical-align: top; |
|---|
| 133 | } |
|---|
| 134 | table.full { |
|---|
| 135 | border-style: outset; |
|---|
| 136 | border-width: 1px; |
|---|
| 137 | } |
|---|
| 138 | table.headers { |
|---|
| 139 | border-style: outset; |
|---|
| 140 | border-width: 1px; |
|---|
| 141 | } |
|---|
| 142 | table.tt td { |
|---|
| 143 | vertical-align: top; |
|---|
| 144 | } |
|---|
| 145 | table.full td { |
|---|
| 146 | border-style: inset; |
|---|
| 147 | border-width: 1px; |
|---|
| 148 | } |
|---|
| 149 | table.tt th { |
|---|
| 150 | vertical-align: top; |
|---|
| 151 | } |
|---|
| 152 | table.full th { |
|---|
| 153 | border-style: inset; |
|---|
| 154 | border-width: 1px; |
|---|
| 155 | } |
|---|
| 156 | table.headers th { |
|---|
| 157 | border-style: none none inset none; |
|---|
| 158 | border-width: 1px; |
|---|
| 159 | } |
|---|
| 160 | table.left { |
|---|
| 161 | margin-right: auto; |
|---|
| 162 | } |
|---|
| 163 | table.right { |
|---|
| 164 | margin-left: auto; |
|---|
| 165 | } |
|---|
| 166 | table.center { |
|---|
| 167 | margin-left: auto; |
|---|
| 168 | margin-right: auto; |
|---|
| 169 | } |
|---|
| 170 | caption { |
|---|
| 171 | caption-side: bottom; |
|---|
| 172 | font-weight: bold; |
|---|
| 173 | font-size: 9pt; |
|---|
| 174 | margin-top: .5em; |
|---|
| 175 | } |
|---|
| 176 | |
|---|
| 177 | table.header { |
|---|
| 178 | border-spacing: 1px; |
|---|
| 179 | width: 95%; |
|---|
| 180 | font-size: 10pt; |
|---|
| 181 | color: white; |
|---|
| 182 | } |
|---|
| 183 | td.top { |
|---|
| 184 | vertical-align: top; |
|---|
| 185 | } |
|---|
| 186 | td.topnowrap { |
|---|
| 187 | vertical-align: top; |
|---|
| 188 | white-space: nowrap; |
|---|
| 189 | } |
|---|
| 190 | table.header td { |
|---|
| 191 | background-color: gray; |
|---|
| 192 | width: 50%; |
|---|
| 193 | } |
|---|
| 194 | table.header a { |
|---|
| 195 | color: white; |
|---|
| 196 | } |
|---|
| 197 | td.reference { |
|---|
| 198 | vertical-align: top; |
|---|
| 199 | white-space: nowrap; |
|---|
| 200 | padding-right: 1em; |
|---|
| 201 | } |
|---|
| 202 | thead { |
|---|
| 203 | display:table-header-group; |
|---|
| 204 | } |
|---|
| 205 | ul.toc, ul.toc ul { |
|---|
| 206 | list-style: none; |
|---|
| 207 | margin-left: 1.5em; |
|---|
| 208 | margin-right: 0em; |
|---|
| 209 | padding-left: 0em; |
|---|
| 210 | } |
|---|
| 211 | ul.toc li { |
|---|
| 212 | line-height: 150%; |
|---|
| 213 | font-weight: bold; |
|---|
| 214 | font-size: 10pt; |
|---|
| 215 | margin-left: 0em; |
|---|
| 216 | margin-right: 0em; |
|---|
| 217 | } |
|---|
| 218 | ul.toc li li { |
|---|
| 219 | line-height: normal; |
|---|
| 220 | font-weight: normal; |
|---|
| 221 | font-size: 9pt; |
|---|
| 222 | margin-left: 0em; |
|---|
| 223 | margin-right: 0em; |
|---|
| 224 | } |
|---|
| 225 | li.excluded { |
|---|
| 226 | font-size: 0pt; |
|---|
| 227 | } |
|---|
| 228 | ul p { |
|---|
| 229 | margin-left: 0em; |
|---|
| 230 | } |
|---|
| 231 | ul.ind, ul.ind ul { |
|---|
| 232 | list-style: none; |
|---|
| 233 | margin-left: 1.5em; |
|---|
| 234 | margin-right: 0em; |
|---|
| 235 | padding-left: 0em; |
|---|
| 236 | page-break-before: avoid; |
|---|
| 237 | } |
|---|
| 238 | ul.ind li { |
|---|
| 239 | font-weight: bold; |
|---|
| 240 | line-height: 200%; |
|---|
| 241 | margin-left: 0em; |
|---|
| 242 | margin-right: 0em; |
|---|
| 243 | } |
|---|
| 244 | ul.ind li li { |
|---|
| 245 | font-weight: normal; |
|---|
| 246 | line-height: 150%; |
|---|
| 247 | margin-left: 0em; |
|---|
| 248 | margin-right: 0em; |
|---|
| 249 | } |
|---|
| 250 | .avoidbreak { |
|---|
| 251 | page-break-inside: avoid; |
|---|
| 252 | } |
|---|
| 253 | .bcp14 { |
|---|
| 254 | font-style: normal; |
|---|
| 255 | text-transform: lowercase; |
|---|
| 256 | font-variant: small-caps; |
|---|
| 257 | } |
|---|
| 258 | .comment { |
|---|
| 259 | background-color: yellow; |
|---|
| 260 | } |
|---|
| 261 | .center { |
|---|
| 262 | text-align: center; |
|---|
| 263 | } |
|---|
| 264 | .error { |
|---|
| 265 | color: red; |
|---|
| 266 | font-style: italic; |
|---|
| 267 | font-weight: bold; |
|---|
| 268 | } |
|---|
| 269 | .figure { |
|---|
| 270 | font-weight: bold; |
|---|
| 271 | text-align: center; |
|---|
| 272 | font-size: 9pt; |
|---|
| 273 | } |
|---|
| 274 | .filename { |
|---|
| 275 | color: #333333; |
|---|
| 276 | font-weight: bold; |
|---|
| 277 | font-size: 12pt; |
|---|
| 278 | line-height: 21pt; |
|---|
| 279 | text-align: center; |
|---|
| 280 | } |
|---|
| 281 | .fn { |
|---|
| 282 | font-weight: bold; |
|---|
| 283 | } |
|---|
| 284 | .hidden { |
|---|
| 285 | display: none; |
|---|
| 286 | } |
|---|
| 287 | .left { |
|---|
| 288 | text-align: left; |
|---|
| 289 | } |
|---|
| 290 | .right { |
|---|
| 291 | text-align: right; |
|---|
| 292 | } |
|---|
| 293 | .title { |
|---|
| 294 | color: #990000; |
|---|
| 295 | font-size: 18pt; |
|---|
| 296 | line-height: 18pt; |
|---|
| 297 | font-weight: bold; |
|---|
| 298 | text-align: center; |
|---|
| 299 | margin-top: 36pt; |
|---|
| 300 | } |
|---|
| 301 | .vcardline { |
|---|
| 302 | display: block; |
|---|
| 303 | } |
|---|
| 304 | .warning { |
|---|
| 305 | font-size: 14pt; |
|---|
| 306 | background-color: yellow; |
|---|
| 307 | } |
|---|
| 308 | |
|---|
| 309 | |
|---|
| 310 | @media print { |
|---|
| 311 | .noprint { |
|---|
| 312 | display: none; |
|---|
| 313 | } |
|---|
| 314 | |
|---|
| 315 | a { |
|---|
| 316 | color: black; |
|---|
| 317 | text-decoration: none; |
|---|
| 318 | } |
|---|
| 319 | |
|---|
| 320 | table.header { |
|---|
| 321 | width: 90%; |
|---|
| 322 | } |
|---|
| 323 | |
|---|
| 324 | td.header { |
|---|
| 325 | width: 50%; |
|---|
| 326 | color: black; |
|---|
| 327 | background-color: white; |
|---|
| 328 | vertical-align: top; |
|---|
| 329 | font-size: 12pt; |
|---|
| 330 | } |
|---|
| 331 | |
|---|
| 332 | ul.toc a::after { |
|---|
| 333 | content: leader('.') target-counter(attr(href), page); |
|---|
| 334 | } |
|---|
| 335 | |
|---|
| 336 | ul.ind li li a { |
|---|
| 337 | content: target-counter(attr(href), page); |
|---|
| 338 | } |
|---|
| 339 | |
|---|
| 340 | .print2col { |
|---|
| 341 | column-count: 2; |
|---|
| 342 | -moz-column-count: 2; |
|---|
| 343 | column-fill: auto; |
|---|
| 344 | } |
|---|
| 345 | } |
|---|
| 346 | |
|---|
| 347 | @page { |
|---|
| 348 | @top-left { |
|---|
| 349 | content: "Internet-Draft"; |
|---|
| 350 | } |
|---|
| 351 | @top-right { |
|---|
| 352 | content: "August 2011"; |
|---|
| 353 | } |
|---|
| 354 | @top-center { |
|---|
| 355 | content: "HTTP/1.1, Part 5"; |
|---|
| 356 | } |
|---|
| 357 | @bottom-left { |
|---|
| 358 | content: "Fielding, et al."; |
|---|
| 359 | } |
|---|
| 360 | @bottom-center { |
|---|
| 361 | content: "Expires February 25, 2012"; |
|---|
| 362 | } |
|---|
| 363 | @bottom-right { |
|---|
| 364 | content: "[Page " counter(page) "]"; |
|---|
| 365 | } |
|---|
| 366 | } |
|---|
| 367 | |
|---|
| 368 | @page:first { |
|---|
| 369 | @top-left { |
|---|
| 370 | content: normal; |
|---|
| 371 | } |
|---|
| 372 | @top-right { |
|---|
| 373 | content: normal; |
|---|
| 374 | } |
|---|
| 375 | @top-center { |
|---|
| 376 | content: normal; |
|---|
| 377 | } |
|---|
| 378 | } |
|---|
| 379 | </style><link rel="Contents" href="#rfc.toc"> |
|---|
| 380 | <link rel="Author" href="#rfc.authors"> |
|---|
| 381 | <link rel="Copyright" href="#rfc.copyrightnotice"> |
|---|
| 382 | <link rel="Index" href="#rfc.index"> |
|---|
| 383 | <link rel="Chapter" title="1 Introduction" href="#rfc.section.1"> |
|---|
| 384 | <link rel="Chapter" title="2 Range Units" href="#rfc.section.2"> |
|---|
| 385 | <link rel="Chapter" title="3 Status Code Definitions" href="#rfc.section.3"> |
|---|
| 386 | <link rel="Chapter" title="4 Combining Ranges" href="#rfc.section.4"> |
|---|
| 387 | <link rel="Chapter" title="5 Header Field Definitions" href="#rfc.section.5"> |
|---|
| 388 | <link rel="Chapter" title="6 IANA Considerations" href="#rfc.section.6"> |
|---|
| 389 | <link rel="Chapter" title="7 Security Considerations" href="#rfc.section.7"> |
|---|
| 390 | <link rel="Chapter" title="8 Acknowledgments" href="#rfc.section.8"> |
|---|
| 391 | <link rel="Chapter" href="#rfc.section.9" title="9 References"> |
|---|
| 392 | <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A"> |
|---|
| 393 | <link rel="Appendix" title="B Compatibility with Previous Versions" href="#rfc.section.B"> |
|---|
| 394 | <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C"> |
|---|
| 395 | <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> |
|---|
| 396 | <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.553, 2011-07-27 17:45:31, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> |
|---|
| 397 | <link rel="schema.dct" href="http://purl.org/dc/terms/"> |
|---|
| 398 | <meta name="dct.creator" content="Fielding, R."> |
|---|
| 399 | <meta name="dct.creator" content="Gettys, J."> |
|---|
| 400 | <meta name="dct.creator" content="Mogul, J."> |
|---|
| 401 | <meta name="dct.creator" content="Frystyk, H."> |
|---|
| 402 | <meta name="dct.creator" content="Masinter, L."> |
|---|
| 403 | <meta name="dct.creator" content="Leach, P."> |
|---|
| 404 | <meta name="dct.creator" content="Berners-Lee, T."> |
|---|
| 405 | <meta name="dct.creator" content="Lafon, Y."> |
|---|
| 406 | <meta name="dct.creator" content="Reschke, J. F."> |
|---|
| 407 | <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-16"> |
|---|
| 408 | <meta name="dct.issued" scheme="ISO8601" content="2011-08-24"> |
|---|
| 409 | <meta name="dct.replaces" content="urn:ietf:rfc:2616"> |
|---|
| 410 | <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext 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."> |
|---|
| 411 | <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext 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."> |
|---|
| 412 | </head> |
|---|
| 413 | <body> |
|---|
| 414 | <table class="header"> |
|---|
| 415 | <tbody> |
|---|
| 416 | <tr> |
|---|
| 417 | <td class="left">HTTPbis Working Group</td> |
|---|
| 418 | <td class="right">R. Fielding, Editor</td> |
|---|
| 419 | </tr> |
|---|
| 420 | <tr> |
|---|
| 421 | <td class="left">Internet-Draft</td> |
|---|
| 422 | <td class="right">Adobe</td> |
|---|
| 423 | </tr> |
|---|
| 424 | <tr> |
|---|
| 425 | <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) |
|---|
| 426 | </td> |
|---|
| 427 | <td class="right">J. Gettys</td> |
|---|
| 428 | </tr> |
|---|
| 429 | <tr> |
|---|
| 430 | <td class="left">Intended status: Standards Track</td> |
|---|
| 431 | <td class="right">Alcatel-Lucent</td> |
|---|
| 432 | </tr> |
|---|
| 433 | <tr> |
|---|
| 434 | <td class="left">Expires: February 25, 2012</td> |
|---|
| 435 | <td class="right">J. Mogul</td> |
|---|
| 436 | </tr> |
|---|
| 437 | <tr> |
|---|
| 438 | <td class="left"></td> |
|---|
| 439 | <td class="right">HP</td> |
|---|
| 440 | </tr> |
|---|
| 441 | <tr> |
|---|
| 442 | <td class="left"></td> |
|---|
| 443 | <td class="right">H. Frystyk</td> |
|---|
| 444 | </tr> |
|---|
| 445 | <tr> |
|---|
| 446 | <td class="left"></td> |
|---|
| 447 | <td class="right">Microsoft</td> |
|---|
| 448 | </tr> |
|---|
| 449 | <tr> |
|---|
| 450 | <td class="left"></td> |
|---|
| 451 | <td class="right">L. Masinter</td> |
|---|
| 452 | </tr> |
|---|
| 453 | <tr> |
|---|
| 454 | <td class="left"></td> |
|---|
| 455 | <td class="right">Adobe</td> |
|---|
| 456 | </tr> |
|---|
| 457 | <tr> |
|---|
| 458 | <td class="left"></td> |
|---|
| 459 | <td class="right">P. Leach</td> |
|---|
| 460 | </tr> |
|---|
| 461 | <tr> |
|---|
| 462 | <td class="left"></td> |
|---|
| 463 | <td class="right">Microsoft</td> |
|---|
| 464 | </tr> |
|---|
| 465 | <tr> |
|---|
| 466 | <td class="left"></td> |
|---|
| 467 | <td class="right">T. Berners-Lee</td> |
|---|
| 468 | </tr> |
|---|
| 469 | <tr> |
|---|
| 470 | <td class="left"></td> |
|---|
| 471 | <td class="right">W3C/MIT</td> |
|---|
| 472 | </tr> |
|---|
| 473 | <tr> |
|---|
| 474 | <td class="left"></td> |
|---|
| 475 | <td class="right">Y. Lafon, Editor</td> |
|---|
| 476 | </tr> |
|---|
| 477 | <tr> |
|---|
| 478 | <td class="left"></td> |
|---|
| 479 | <td class="right">W3C</td> |
|---|
| 480 | </tr> |
|---|
| 481 | <tr> |
|---|
| 482 | <td class="left"></td> |
|---|
| 483 | <td class="right">J. Reschke, Editor</td> |
|---|
| 484 | </tr> |
|---|
| 485 | <tr> |
|---|
| 486 | <td class="left"></td> |
|---|
| 487 | <td class="right">greenbytes</td> |
|---|
| 488 | </tr> |
|---|
| 489 | <tr> |
|---|
| 490 | <td class="left"></td> |
|---|
| 491 | <td class="right">August 24, 2011</td> |
|---|
| 492 | </tr> |
|---|
| 493 | </tbody> |
|---|
| 494 | </table> |
|---|
| 495 | <p class="title">HTTP/1.1, part 5: Range Requests and Partial Responses<br><span class="filename">draft-ietf-httpbis-p5-range-16</span></p> |
|---|
| 496 | <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> |
|---|
| 497 | <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information |
|---|
| 498 | systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the |
|---|
| 499 | seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. |
|---|
| 500 | </p> |
|---|
| 501 | <p>Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.</p> |
|---|
| 502 | <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> |
|---|
| 503 | <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived |
|---|
| 504 | at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. |
|---|
| 505 | </p> |
|---|
| 506 | <p>The current issues list is at <<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>> and related documents (including fancy diffs) can be found at <<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>>. |
|---|
| 507 | </p> |
|---|
| 508 | <p>The changes in this draft are summarized in <a href="#changes.since.15" title="Since draft-ietf-httpbis-p5-range-15">Appendix D.17</a>. |
|---|
| 509 | </p> |
|---|
| 510 | <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1> |
|---|
| 511 | <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p> |
|---|
| 512 | <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute |
|---|
| 513 | working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>. |
|---|
| 514 | </p> |
|---|
| 515 | <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other |
|---|
| 516 | documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work |
|---|
| 517 | in progress”. |
|---|
| 518 | </p> |
|---|
| 519 | <p>This Internet-Draft will expire on February 25, 2012.</p> |
|---|
| 520 | <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> |
|---|
| 521 | <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> |
|---|
| 522 | <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights |
|---|
| 523 | and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License |
|---|
| 524 | text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified |
|---|
| 525 | BSD License. |
|---|
| 526 | </p> |
|---|
| 527 | <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November |
|---|
| 528 | 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to |
|---|
| 529 | allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) |
|---|
| 530 | controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative |
|---|
| 531 | works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate |
|---|
| 532 | it into languages other than English. |
|---|
| 533 | </p> |
|---|
| 534 | <hr class="noprint"> |
|---|
| 535 | <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1> |
|---|
| 536 | <ul class="toc"> |
|---|
| 537 | <li>1. <a href="#introduction">Introduction</a><ul> |
|---|
| 538 | <li>1.1 <a href="#intro.requirements">Requirements</a></li> |
|---|
| 539 | <li>1.2 <a href="#notation">Syntax Notation</a><ul> |
|---|
| 540 | <li>1.2.1 <a href="#core.rules">Core Rules</a></li> |
|---|
| 541 | <li>1.2.2 <a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li> |
|---|
| 542 | </ul> |
|---|
| 543 | </li> |
|---|
| 544 | </ul> |
|---|
| 545 | </li> |
|---|
| 546 | <li>2. <a href="#range.units">Range Units</a><ul> |
|---|
| 547 | <li>2.1 <a href="#range.specifier.registry">Range Specifier Registry</a></li> |
|---|
| 548 | </ul> |
|---|
| 549 | </li> |
|---|
| 550 | <li>3. <a href="#status.code.definitions">Status Code Definitions</a><ul> |
|---|
| 551 | <li>3.1 <a href="#status.206">206 Partial Content</a></li> |
|---|
| 552 | <li>3.2 <a href="#status.416">416 Requested Range Not Satisfiable</a></li> |
|---|
| 553 | </ul> |
|---|
| 554 | </li> |
|---|
| 555 | <li>4. <a href="#combining.byte.ranges">Combining Ranges</a></li> |
|---|
| 556 | <li>5. <a href="#header.fields">Header Field Definitions</a><ul> |
|---|
| 557 | <li>5.1 <a href="#header.accept-ranges">Accept-Ranges</a></li> |
|---|
| 558 | <li>5.2 <a href="#header.content-range">Content-Range</a></li> |
|---|
| 559 | <li>5.3 <a href="#header.if-range">If-Range</a></li> |
|---|
| 560 | <li>5.4 <a href="#header.range">Range</a><ul> |
|---|
| 561 | <li>5.4.1 <a href="#byte.ranges">Byte Ranges</a></li> |
|---|
| 562 | <li>5.4.2 <a href="#range.retrieval.requests">Range Retrieval Requests</a></li> |
|---|
| 563 | </ul> |
|---|
| 564 | </li> |
|---|
| 565 | </ul> |
|---|
| 566 | </li> |
|---|
| 567 | <li>6. <a href="#IANA.considerations">IANA Considerations</a><ul> |
|---|
| 568 | <li>6.1 <a href="#status.code.registration">Status Code Registration</a></li> |
|---|
| 569 | <li>6.2 <a href="#header.field.registration">Header Field Registration</a></li> |
|---|
| 570 | <li>6.3 <a href="#range.specifier.registration">Range Specifier Registration</a></li> |
|---|
| 571 | </ul> |
|---|
| 572 | </li> |
|---|
| 573 | <li>7. <a href="#security.considerations">Security Considerations</a><ul> |
|---|
| 574 | <li>7.1 <a href="#overlapping.ranges">Overlapping Ranges</a></li> |
|---|
| 575 | </ul> |
|---|
| 576 | </li> |
|---|
| 577 | <li>8. <a href="#acks">Acknowledgments</a></li> |
|---|
| 578 | <li>9. <a href="#rfc.references">References</a><ul> |
|---|
| 579 | <li>9.1 <a href="#rfc.references.1">Normative References</a></li> |
|---|
| 580 | <li>9.2 <a href="#rfc.references.2">Informative References</a></li> |
|---|
| 581 | </ul> |
|---|
| 582 | </li> |
|---|
| 583 | <li><a href="#rfc.authors">Authors' Addresses</a></li> |
|---|
| 584 | <li>A. <a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li> |
|---|
| 585 | <li>B. <a href="#compatibility">Compatibility with Previous Versions</a><ul> |
|---|
| 586 | <li>B.1 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> |
|---|
| 587 | </ul> |
|---|
| 588 | </li> |
|---|
| 589 | <li>C. <a href="#collected.abnf">Collected ABNF</a></li> |
|---|
| 590 | <li>D. <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul> |
|---|
| 591 | <li>D.1 <a href="#rfc.section.D.1">Since RFC 2616</a></li> |
|---|
| 592 | <li>D.2 <a href="#rfc.section.D.2">Since draft-ietf-httpbis-p5-range-00</a></li> |
|---|
| 593 | <li>D.3 <a href="#rfc.section.D.3">Since draft-ietf-httpbis-p5-range-01</a></li> |
|---|
| 594 | <li>D.4 <a href="#changes.since.02">Since draft-ietf-httpbis-p5-range-02</a></li> |
|---|
| 595 | <li>D.5 <a href="#changes.since.03">Since draft-ietf-httpbis-p5-range-03</a></li> |
|---|
| 596 | <li>D.6 <a href="#changes.since.04">Since draft-ietf-httpbis-p5-range-04</a></li> |
|---|
| 597 | <li>D.7 <a href="#changes.since.05">Since draft-ietf-httpbis-p5-range-05</a></li> |
|---|
| 598 | <li>D.8 <a href="#changes.since.06">Since draft-ietf-httpbis-p5-range-06</a></li> |
|---|
| 599 | <li>D.9 <a href="#changes.since.07">Since draft-ietf-httpbis-p5-range-07</a></li> |
|---|
| 600 | <li>D.10 <a href="#changes.since.08">Since draft-ietf-httpbis-p5-range-08</a></li> |
|---|
| 601 | <li>D.11 <a href="#changes.since.09">Since draft-ietf-httpbis-p5-range-09</a></li> |
|---|
| 602 | <li>D.12 <a href="#changes.since.10">Since draft-ietf-httpbis-p5-range-10</a></li> |
|---|
| 603 | <li>D.13 <a href="#changes.since.11">Since draft-ietf-httpbis-p5-range-11</a></li> |
|---|
| 604 | <li>D.14 <a href="#changes.since.12">Since draft-ietf-httpbis-p5-range-12</a></li> |
|---|
| 605 | <li>D.15 <a href="#changes.since.13">Since draft-ietf-httpbis-p5-range-13</a></li> |
|---|
| 606 | <li>D.16 <a href="#changes.since.14">Since draft-ietf-httpbis-p5-range-14</a></li> |
|---|
| 607 | <li>D.17 <a href="#changes.since.15">Since draft-ietf-httpbis-p5-range-15</a></li> |
|---|
| 608 | </ul> |
|---|
| 609 | </li> |
|---|
| 610 | <li><a href="#rfc.index">Index</a></li> |
|---|
| 611 | </ul> |
|---|
| 612 | <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> <a id="introduction" href="#introduction">Introduction</a></h1> |
|---|
| 613 | <p id="rfc.section.1.p.1">HTTP clients often encounter interrupted data transfers as a result of cancelled requests or dropped connections. When a client |
|---|
| 614 | has stored a partial representation, it is desirable to request the remainder of that representation in a subsequent request |
|---|
| 615 | rather than transfer the entire representation. There are also a number of Web applications that benefit from being able to |
|---|
| 616 | request only a subset of a larger representation, such as a single page of a very large document or only part of an image |
|---|
| 617 | to be rendered by a device with limited local storage. |
|---|
| 618 | </p> |
|---|
| 619 | <p id="rfc.section.1.p.2">This document defines HTTP/1.1 range requests, partial responses, and the multipart/byteranges media type. The protocol for |
|---|
| 620 | range requests is an <em class="bcp14">OPTIONAL</em> feature of HTTP, designed so resources or recipients that do not implement this feature can respond as if it is a normal GET |
|---|
| 621 | request without impacting interoperability. Partial responses are indicated by a distinct status code to not be mistaken for |
|---|
| 622 | full responses by intermediate caches that might not implement the feature. |
|---|
| 623 | </p> |
|---|
| 624 | <p id="rfc.section.1.p.3">Although the HTTP range request mechanism is designed to allow for extensible range types, this specification only defines |
|---|
| 625 | requests for byte ranges. |
|---|
| 626 | </p> |
|---|
| 627 | <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> |
|---|
| 628 | <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" |
|---|
| 629 | 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>. |
|---|
| 630 | </p> |
|---|
| 631 | <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the |
|---|
| 632 | protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements |
|---|
| 633 | for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not |
|---|
| 634 | all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant". |
|---|
| 635 | </p> |
|---|
| 636 | <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a> <a id="notation" href="#notation">Syntax Notation</a></h2> |
|---|
| 637 | <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix C</a> shows the collected ABNF, with the list rule expanded. |
|---|
| 638 | </p> |
|---|
| 639 | <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG |
|---|
| 640 | (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character), |
|---|
| 641 | and WSP (whitespace). |
|---|
| 642 | </p> |
|---|
| 643 | <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a> <a id="core.rules" href="#core.rules">Core Rules</a></h3> |
|---|
| 644 | <p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>: |
|---|
| 645 | </p> |
|---|
| 646 | <div id="rfc.figure.u.1"></div><pre class="inline"> <a href="#core.rules" class="smpl">OWS</a> = <OWS, defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>> |
|---|
| 647 | <a href="#core.rules" class="smpl">token</a> = <token, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#field.rules" title="Common Field ABNF Rules">Section 3.2.3</a>> |
|---|
| 648 | <a href="#core.rules" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a>> |
|---|
| 649 | </pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a> <a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3> |
|---|
| 650 | <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p> |
|---|
| 651 | <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">entity-tag</a> = <entity-tag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a>> |
|---|
| 652 | </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="range.units" href="#range.units">Range Units</a></h1> |
|---|
| 653 | <p id="rfc.section.2.p.1">HTTP/1.1 allows a client to request that only part (a range) of the representation be included within the response. HTTP/1.1 |
|---|
| 654 | 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. A representation can be broken down into subranges according to various structural units. |
|---|
| 655 | </p> |
|---|
| 656 | <div id="rfc.figure.u.3"></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> <a href="#range.units" class="smpl">range-unit</a> = <a href="#range.units" class="smpl">bytes-unit</a> / <a href="#range.units" class="smpl">other-range-unit</a> |
|---|
| 657 | <a href="#range.units" class="smpl">bytes-unit</a> = "bytes" |
|---|
| 658 | <a href="#range.units" class="smpl">other-range-unit</a> = <a href="#core.rules" class="smpl">token</a> |
|---|
| 659 | </pre><p id="rfc.section.2.p.3">HTTP/1.1 has been designed to allow implementations of applications that do not depend on knowledge of ranges. The only range |
|---|
| 660 | unit defined by HTTP/1.1 is "bytes". Additional specifiers can be defined as described in <a href="#range.specifier.registry" title="Range Specifier Registry">Section 2.1</a>. |
|---|
| 661 | </p> |
|---|
| 662 | <p id="rfc.section.2.p.4">If a range unit is not understood in a request, a server <em class="bcp14">MUST</em> ignore the whole Range header field (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section 5.4</a>). If a range unit is not understood in a response, an intermediary <em class="bcp14">SHOULD</em> pass the response to the client; a client <em class="bcp14">MUST</em> fail. |
|---|
| 663 | </p> |
|---|
| 664 | <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> <a id="range.specifier.registry" href="#range.specifier.registry">Range Specifier Registry</a></h2> |
|---|
| 665 | <p id="rfc.section.2.1.p.1">The HTTP Range Specifier Registry defines the name space for the range specifier names.</p> |
|---|
| 666 | <p id="rfc.section.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields: |
|---|
| 667 | </p> |
|---|
| 668 | <ul> |
|---|
| 669 | <li>Name</li> |
|---|
| 670 | <li>Description</li> |
|---|
| 671 | <li>Pointer to specification text</li> |
|---|
| 672 | </ul> |
|---|
| 673 | <p id="rfc.section.2.1.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). |
|---|
| 674 | </p> |
|---|
| 675 | <p id="rfc.section.2.1.p.4">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-range-specifiers">http://www.iana.org/assignments/http-range-specifiers</a>>. |
|---|
| 676 | </p> |
|---|
| 677 | <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="status.code.definitions" href="#status.code.definitions">Status Code Definitions</a></h1> |
|---|
| 678 | <div id="rfc.iref.3"></div> |
|---|
| 679 | <div id="rfc.iref.s.1"></div> |
|---|
| 680 | <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> |
|---|
| 681 | <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.3" 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. |
|---|
| 682 | </p> |
|---|
| 683 | <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields: |
|---|
| 684 | </p> |
|---|
| 685 | <ul> |
|---|
| 686 | <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 |
|---|
| 687 | 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. |
|---|
| 688 | </li> |
|---|
| 689 | <li>Date</li> |
|---|
| 690 | <li>Cache-Control, ETag, Expires, Content-Location, Last-Modified, and/or Vary, if the header field would have been sent in a |
|---|
| 691 | 200 response to the same request |
|---|
| 692 | </li> |
|---|
| 693 | </ul> |
|---|
| 694 | <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 representation header fields. Otherwise, the response <em class="bcp14">MUST</em> include all of the representation header fields that would have been returned with a 200 (OK) response to the same request. |
|---|
| 695 | </p> |
|---|
| 696 | <div id="rfc.iref.4"></div> |
|---|
| 697 | <div id="rfc.iref.s.2"></div> |
|---|
| 698 | <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> |
|---|
| 699 | <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 header field (<a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section 5.4</a>), and none of the ranges-specifier values in this field overlap the current extent of the selected resource, and the request |
|---|
| 700 | did not include an If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section 5.3</a>). (For byte-ranges, this means that the first-byte-pos of all of the byte-range-spec values were greater than the current |
|---|
| 701 | length of the selected resource.) |
|---|
| 702 | </p> |
|---|
| 703 | <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 header field specifying the current length of the representation (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. |
|---|
| 704 | </p> |
|---|
| 705 | <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="combining.byte.ranges" href="#combining.byte.ranges">Combining Ranges</a></h1> |
|---|
| 706 | <p id="rfc.section.4.p.1">A response might transfer only a subrange of a representation if the connection closed prematurely or if the request used |
|---|
| 707 | one or more Range specifications. After several such transfers, a client might have received several ranges of the same representation. |
|---|
| 708 | These ranges can only be safely combined if they all have in common the same strong validator, where "strong validator" is |
|---|
| 709 | defined to be either an entity-tag that is not marked as weak (<a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>) or, if no entity-tag is provided, a Last-Modified value that is strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. |
|---|
| 710 | </p> |
|---|
| 711 | <p id="rfc.section.4.p.2">When a client receives an incomplete 200 (OK) or 206 (Partial Content) response and already has one or more stored responses |
|---|
| 712 | for the same method and effective request URI, all of the stored responses with the same strong validator <em class="bcp14">MAY</em> be combined with the partial content in this new response. If none of the stored responses contain the same strong validator, |
|---|
| 713 | then this new response corresponds to a new representation and <em class="bcp14">MUST NOT</em> be combined with the existing stored responses. |
|---|
| 714 | </p> |
|---|
| 715 | <p id="rfc.section.4.p.3">If the new response is an incomplete 200 (OK) response, then the header fields of that new response are used for any combined |
|---|
| 716 | response and replace those of the matching stored responses. |
|---|
| 717 | </p> |
|---|
| 718 | <p id="rfc.section.4.p.4">If the new response is a 206 (Partial Content) response and at least one of the matching stored responses is a 200 (OK), then |
|---|
| 719 | the combined response header fields consist of the most recent 200 response's header fields. If all of the matching stored |
|---|
| 720 | responses are 206 responses, then the stored response with the most header fields is used as the source of header fields for |
|---|
| 721 | the combined response, except that the client <em class="bcp14">MUST</em> use other header fields provided in the new response, aside from Content-Range, to replace all instances of the corresponding |
|---|
| 722 | header fields in the stored response. |
|---|
| 723 | </p> |
|---|
| 724 | <p id="rfc.section.4.p.5">The combined response message-body consists of the union of partial content ranges in the new response and each of the selected |
|---|
| 725 | responses. If the union consists of the entire range of the representation, then the combined response <em class="bcp14">MUST</em> be recorded as a complete 200 (OK) response with a Content-Length header field that reflects the complete length. Otherwise, |
|---|
| 726 | the combined response(s) <em class="bcp14">MUST</em> include a Content-Range header field describing the included range(s) and be recorded as incomplete. If the union consists |
|---|
| 727 | of a discontinuous range of the representation, then the client <em class="bcp14">MAY</em> store it as either a multipart range response or as multiple 206 responses with one continuous range each. |
|---|
| 728 | </p> |
|---|
| 729 | <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="header.fields" href="#header.fields">Header Field Definitions</a></h1> |
|---|
| 730 | <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> |
|---|
| 731 | <div id="rfc.iref.a.1"></div> |
|---|
| 732 | <div id="rfc.iref.h.1"></div> |
|---|
| 733 | <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> |
|---|
| 734 | <p id="rfc.section.5.1.p.1">The "Accept-Ranges" header field allows a resource to indicate its acceptance of range requests.</p> |
|---|
| 735 | <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span> <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> |
|---|
| 736 | <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none" |
|---|
| 737 | </pre><p id="rfc.section.5.1.p.3">Origin servers that accept byte-range requests <em class="bcp14">MAY</em> send |
|---|
| 738 | </p> |
|---|
| 739 | <div id="rfc.figure.u.5"></div><pre class="text"> Accept-Ranges: bytes |
|---|
| 740 | </pre><p id="rfc.section.5.1.p.5">but are not required to do so. Clients <em class="bcp14">MAY</em> generate range requests without having received this header field for the resource involved. Range units are defined in <a href="#range.units" title="Range Units">Section 2</a>. |
|---|
| 741 | </p> |
|---|
| 742 | <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 |
|---|
| 743 | </p> |
|---|
| 744 | <div id="rfc.figure.u.6"></div><pre class="text"> Accept-Ranges: none |
|---|
| 745 | </pre><p id="rfc.section.5.1.p.8">to advise the client not to attempt a range request.</p> |
|---|
| 746 | <div id="rfc.iref.c.1"></div> |
|---|
| 747 | <div id="rfc.iref.h.2"></div> |
|---|
| 748 | <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> |
|---|
| 749 | <p id="rfc.section.5.2.p.1">The "Content-Range" header field is sent with a partial representation to specify where in the full representation the payload |
|---|
| 750 | body is intended to be applied. |
|---|
| 751 | </p> |
|---|
| 752 | <p id="rfc.section.5.2.p.2">Range units are defined in <a href="#range.units" title="Range Units">Section 2</a>. |
|---|
| 753 | </p> |
|---|
| 754 | <div id="rfc.figure.u.7"></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> <a href="#header.content-range" class="smpl">Content-Range</a> = <a href="#header.content-range" class="smpl">byte-content-range-spec</a> |
|---|
| 755 | / <a href="#header.content-range" class="smpl">other-content-range-spec</a> |
|---|
| 756 | |
|---|
| 757 | <a href="#header.content-range" class="smpl">byte-content-range-spec</a> = <a href="#range.units" class="smpl">bytes-unit</a> <a href="#notation" class="smpl">SP</a> |
|---|
| 758 | <a href="#header.content-range" class="smpl">byte-range-resp-spec</a> "/" |
|---|
| 759 | ( <a href="#header.content-range" class="smpl">instance-length</a> / "*" ) |
|---|
| 760 | |
|---|
| 761 | <a href="#header.content-range" class="smpl">byte-range-resp-spec</a> = (<a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> "-" <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>) |
|---|
| 762 | / "*" |
|---|
| 763 | |
|---|
| 764 | <a href="#header.content-range" class="smpl">instance-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a> |
|---|
| 765 | |
|---|
| 766 | <a href="#header.content-range" class="smpl">other-content-range-spec</a> = <a href="#range.units" class="smpl">other-range-unit</a> <a href="#notation" class="smpl">SP</a> |
|---|
| 767 | <a href="#header.content-range" class="smpl">other-range-resp-spec</a> |
|---|
| 768 | <a href="#header.content-range" class="smpl">other-range-resp-spec</a> = *<a href="#notation" class="smpl">CHAR</a> |
|---|
| 769 | </pre><p id="rfc.section.5.2.p.4">The header field <em class="bcp14">SHOULD</em> indicate the total length of the full representation, unless this length is unknown or difficult to determine. The asterisk |
|---|
| 770 | "*" character means that the instance-length is unknown at the time when the response was generated. |
|---|
| 771 | </p> |
|---|
| 772 | <p id="rfc.section.5.2.p.5">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. |
|---|
| 773 | </p> |
|---|
| 774 | <p id="rfc.section.5.2.p.6">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 |
|---|
| 775 | 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. |
|---|
| 776 | </p> |
|---|
| 777 | <p id="rfc.section.5.2.p.7">In the case of a byte range request: 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 |
|---|
| 778 | 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 "*". |
|---|
| 779 | </p> |
|---|
| 780 | <p id="rfc.section.5.2.p.8">Examples of byte-content-range-spec values, assuming that the representation contains a total of 1234 bytes: </p> |
|---|
| 781 | <ul> |
|---|
| 782 | <li>The first 500 bytes: |
|---|
| 783 | <div id="rfc.figure.u.8"></div><pre class="text"> bytes 0-499/1234 |
|---|
| 784 | </pre> </li> |
|---|
| 785 | <li>The second 500 bytes: |
|---|
| 786 | <div id="rfc.figure.u.9"></div><pre class="text"> bytes 500-999/1234 |
|---|
| 787 | </pre> </li> |
|---|
| 788 | <li>All except for the first 500 bytes: |
|---|
| 789 | <div id="rfc.figure.u.10"></div><pre class="text"> bytes 500-1233/1234 |
|---|
| 790 | </pre> </li> |
|---|
| 791 | <li>The last 500 bytes: |
|---|
| 792 | <div id="rfc.figure.u.11"></div><pre class="text"> bytes 734-1233/1234 |
|---|
| 793 | </pre> </li> |
|---|
| 794 | </ul> |
|---|
| 795 | <p id="rfc.section.5.2.p.9">When an HTTP message includes the content of a single range (for example, a response to a request for a single range, or to |
|---|
| 796 | a request for a set of ranges that overlap without any holes), this content is transmitted with a Content-Range header field, |
|---|
| 797 | and a Content-Length header field showing the number of bytes actually transferred. For example, |
|---|
| 798 | </p> |
|---|
| 799 | <div id="rfc.figure.u.12"></div><pre class="text"> HTTP/1.1 206 Partial Content |
|---|
| 800 | Date: Wed, 15 Nov 1995 06:25:24 GMT |
|---|
| 801 | Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT |
|---|
| 802 | Content-Range: bytes 21010-47021/47022 |
|---|
| 803 | Content-Length: 26012 |
|---|
| 804 | Content-Type: image/gif |
|---|
| 805 | </pre><p id="rfc.section.5.2.p.11">When an HTTP message includes the content of multiple ranges (for example, a response to a request for multiple non-overlapping |
|---|
| 806 | ranges), these are transmitted as a multipart message. The multipart media type used for this purpose is "multipart/byteranges" |
|---|
| 807 | as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>. |
|---|
| 808 | </p> |
|---|
| 809 | <p id="rfc.section.5.2.p.12">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 ranges in a single request. |
|---|
| 810 | </p> |
|---|
| 811 | <p id="rfc.section.5.2.p.13">When a client requests multiple ranges in one request, the server <em class="bcp14">SHOULD</em> return them in the order that they appeared in the request. |
|---|
| 812 | </p> |
|---|
| 813 | <p id="rfc.section.5.2.p.14">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 |
|---|
| 814 | the full representation). |
|---|
| 815 | </p> |
|---|
| 816 | <p id="rfc.section.5.2.p.15">If the server receives a request (other than one including an If-Range header field) with an unsatisfiable Range header field |
|---|
| 817 | (that is, all of whose byte-range-spec values have a first-byte-pos value greater than the current length of the selected |
|---|
| 818 | 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>). |
|---|
| 819 | </p> |
|---|
| 820 | <div class="note" id="rfc.section.5.2.p.16"> |
|---|
| 821 | <p> <b>Note:</b> Clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for |
|---|
| 822 | an unsatisfiable Range header field, since not all servers implement this header field. |
|---|
| 823 | </p> |
|---|
| 824 | </div> |
|---|
| 825 | <div id="rfc.iref.i.1"></div> |
|---|
| 826 | <div id="rfc.iref.h.3"></div> |
|---|
| 827 | <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> |
|---|
| 828 | <p id="rfc.section.5.3.p.1">If a client has a partial copy of a representation and wishes to have an up-to-date copy of the entire representation, it |
|---|
| 829 | could use the Range header field with a conditional GET (using either or both of If-Unmodified-Since and If-Match.) However, |
|---|
| 830 | if the condition fails because the representation has been modified, the client would then have to make a second request to |
|---|
| 831 | obtain the entire current representation. |
|---|
| 832 | </p> |
|---|
| 833 | <p id="rfc.section.5.3.p.2">The "If-Range" header field allows a client to "short-circuit" the second request. Informally, its meaning is "if the representation |
|---|
| 834 | is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new representation". |
|---|
| 835 | </p> |
|---|
| 836 | <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.10"></span> <a href="#header.if-range" class="smpl">If-Range</a> = <a href="#abnf.dependencies" class="smpl">entity-tag</a> / <a href="#core.rules" class="smpl">HTTP-date</a> |
|---|
| 837 | </pre><p id="rfc.section.5.3.p.4">Clients <em class="bcp14">MUST NOT</em> use an entity-tag marked as weak in an If-Range field value and <em class="bcp14">MUST NOT</em> use a Last-Modified date in an If-Range field value unless it has no entity-tag for the representation and the Last-Modified |
|---|
| 838 | date it does have for the representation is strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. |
|---|
| 839 | </p> |
|---|
| 840 | <p id="rfc.section.5.3.p.5">A server that evaluates a conditional range request that is applicable to one of its representations <em class="bcp14">MUST</em> evaluate the condition as false if the entity-tag used as a validator is marked as weak or, when an HTTP-date is used as the |
|---|
| 841 | validator, if the date value is not strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.5"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. (A server can distinguish between a valid HTTP-date and any form of entity-tag by examining the first two characters.) |
|---|
| 842 | </p> |
|---|
| 843 | <p id="rfc.section.5.3.p.6">The If-Range header field <em class="bcp14">SHOULD</em> only be sent by clients together with a Range header field. The If-Range header field <em class="bcp14">MUST</em> be ignored if it is received in a request that does not include a Range header field. The If-Range header field <em class="bcp14">MUST</em> be ignored by a server that does not support the sub-range operation. |
|---|
| 844 | </p> |
|---|
| 845 | <p id="rfc.section.5.3.p.7">If the validator given in the If-Range header field matches the current validator for the selected representation of the target |
|---|
| 846 | resource, then the server <em class="bcp14">SHOULD</em> send the specified sub-range of the representation using a 206 (Partial Content) response. If the validator does not match, |
|---|
| 847 | then the server <em class="bcp14">SHOULD</em> send the entire representation using a 200 (OK) response. |
|---|
| 848 | </p> |
|---|
| 849 | <div id="rfc.iref.r.1"></div> |
|---|
| 850 | <div id="rfc.iref.h.4"></div> |
|---|
| 851 | <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> |
|---|
| 852 | <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> |
|---|
| 853 | <p id="rfc.section.5.4.1.p.1">Since all HTTP representations are transferred as sequences of bytes, the concept of a byte range is meaningful for any HTTP |
|---|
| 854 | representation. (However, not all clients and servers need to support byte-range operations.) |
|---|
| 855 | </p> |
|---|
| 856 | <p id="rfc.section.5.4.1.p.2">Byte range specifications in HTTP apply to the sequence of bytes in the representation body (not necessarily the same as the |
|---|
| 857 | message-body). |
|---|
| 858 | </p> |
|---|
| 859 | <div id="rule.ranges-specifier"> |
|---|
| 860 | <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 representation. |
|---|
| 861 | </p> |
|---|
| 862 | </div> |
|---|
| 863 | <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.11"></span><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> <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#range.units" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> |
|---|
| 864 | <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = 1#( <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> / <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> ) |
|---|
| 865 | <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> "-" [ <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> ] |
|---|
| 866 | <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> = 1*<a href="#notation" class="smpl">DIGIT</a> |
|---|
| 867 | <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> = 1*<a href="#notation" class="smpl">DIGIT</a> |
|---|
| 868 | </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 |
|---|
| 869 | gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets start |
|---|
| 870 | at zero. |
|---|
| 871 | </p> |
|---|
| 872 | <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 |
|---|
| 873 | 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. |
|---|
| 874 | </p> |
|---|
| 875 | <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 representation |
|---|
| 876 | body, last-byte-pos is taken to be equal to one less than the current length of the representation in bytes. |
|---|
| 877 | </p> |
|---|
| 878 | <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 representation.</p> |
|---|
| 879 | <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span> <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> |
|---|
| 880 | <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#notation" class="smpl">DIGIT</a> |
|---|
| 881 | </pre><p id="rfc.section.5.4.1.p.10">A suffix-byte-range-spec is used to specify the suffix of the representation body, of a length given by the suffix-length |
|---|
| 882 | value. (That is, this form specifies the last N bytes of a representation.) If the representation is shorter than the specified |
|---|
| 883 | suffix-length, the entire representation is used. |
|---|
| 884 | </p> |
|---|
| 885 | <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 |
|---|
| 886 | length of the representation, or at least one suffix-byte-range-spec with a non-zero suffix-length, then the byte-range-set |
|---|
| 887 | is 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 416 (Requested range not satisfiable) status code. Otherwise, the server <em class="bcp14">SHOULD</em> return a response with a 206 (Partial Content) status code containing the satisfiable ranges of the representation. |
|---|
| 888 | </p> |
|---|
| 889 | <p id="rfc.section.5.4.1.p.12">Examples of byte-ranges-specifier values (assuming a representation of length 10000): </p> |
|---|
| 890 | <ul> |
|---|
| 891 | <li>The first 500 bytes (byte offsets 0-499, inclusive): |
|---|
| 892 | <div id="rfc.figure.u.16"></div><pre class="text"> bytes=0-499 |
|---|
| 893 | </pre> </li> |
|---|
| 894 | <li>The second 500 bytes (byte offsets 500-999, inclusive): |
|---|
| 895 | <div id="rfc.figure.u.17"></div><pre class="text"> bytes=500-999 |
|---|
| 896 | </pre> </li> |
|---|
| 897 | <li>The final 500 bytes (byte offsets 9500-9999, inclusive): |
|---|
| 898 | <div id="rfc.figure.u.18"></div><pre class="text"> bytes=-500 |
|---|
| 899 | </pre> Or: <div id="rfc.figure.u.19"></div><pre class="text"> bytes=9500- |
|---|
| 900 | </pre> </li> |
|---|
| 901 | <li>The first and last bytes only (bytes 0 and 9999): |
|---|
| 902 | <div id="rfc.figure.u.20"></div><pre class="text"> bytes=0-0,-1 |
|---|
| 903 | </pre> </li> |
|---|
| 904 | <li>Several legal but not canonical specifications of the second 500 bytes (byte offsets 500-999, inclusive): |
|---|
| 905 | <div id="rfc.figure.u.21"></div><pre class="text"> bytes=500-600,601-999 |
|---|
| 906 | bytes=500-700,601-999 |
|---|
| 907 | </pre> </li> |
|---|
| 908 | </ul> |
|---|
| 909 | <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> |
|---|
| 910 | <p id="rfc.section.5.4.2.p.1">The "Range" header field defines the GET method (conditional or not) to request one or more sub-ranges of the response representation |
|---|
| 911 | body, instead of the entire representation body. |
|---|
| 912 | </p> |
|---|
| 913 | <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.19"></span> <a href="#range.retrieval.requests" class="smpl">Range</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> / <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> |
|---|
| 914 | <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = <a href="#range.units" class="smpl">other-range-unit</a> "=" <a href="#range.retrieval.requests" class="smpl">other-range-set</a> |
|---|
| 915 | <a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*<a href="#notation" class="smpl">CHAR</a> |
|---|
| 916 | </pre><p id="rfc.section.5.4.2.p.3">A server <em class="bcp14">MAY</em> ignore the Range header field. However, origin servers and intermediate caches ought to support byte ranges when possible, |
|---|
| 917 | since Range supports efficient recovery from partially failed transfers, and supports efficient partial retrieval of large |
|---|
| 918 | representations. |
|---|
| 919 | </p> |
|---|
| 920 | <p id="rfc.section.5.4.2.p.4">If the server supports the Range header field and the specified range or ranges are appropriate for the representation: </p> |
|---|
| 921 | <ul> |
|---|
| 922 | <li>The presence of a Range header field in an unconditional GET modifies what is returned if the GET is otherwise successful. |
|---|
| 923 | In other words, the response carries a status code of 206 (Partial Content) instead of 200 (OK). |
|---|
| 924 | </li> |
|---|
| 925 | <li>The presence of a Range header field in a conditional GET (a request using one or both of If-Modified-Since and If-None-Match, |
|---|
| 926 | or one or both of If-Unmodified-Since and If-Match) modifies what is returned if the GET is otherwise successful and the condition |
|---|
| 927 | is true. It does not affect the 304 (Not Modified) response returned if the conditional is false. |
|---|
| 928 | </li> |
|---|
| 929 | </ul> |
|---|
| 930 | <p id="rfc.section.5.4.2.p.5">In some cases, it might be more appropriate to use the If-Range header field (see <a href="#header.if-range" id="rfc.xref.header.if-range.3" title="If-Range">Section 5.3</a>) in addition to the Range header field. |
|---|
| 931 | </p> |
|---|
| 932 | <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 |
|---|
| 933 | representation in reply, it <em class="bcp14">MAY</em> only return the requested range to its client. |
|---|
| 934 | </p> |
|---|
| 935 | <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> |
|---|
| 936 | <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a> <a id="status.code.registration" href="#status.code.registration">Status Code Registration</a></h2> |
|---|
| 937 | <p id="rfc.section.6.1.p.1">The HTTP Status Code Registry located at <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>> shall be updated with the registrations below: |
|---|
| 938 | </p> |
|---|
| 939 | <div id="rfc.table.1"> |
|---|
| 940 | <div id="iana.status.code.registration.table"></div> |
|---|
| 941 | <table class="tt full left" cellpadding="3" cellspacing="0"> |
|---|
| 942 | <thead> |
|---|
| 943 | <tr> |
|---|
| 944 | <th>Value</th> |
|---|
| 945 | <th>Description</th> |
|---|
| 946 | <th>Reference</th> |
|---|
| 947 | </tr> |
|---|
| 948 | </thead> |
|---|
| 949 | <tbody> |
|---|
| 950 | <tr> |
|---|
| 951 | <td class="left">206</td> |
|---|
| 952 | <td class="left">Partial Content</td> |
|---|
| 953 | <td class="left"> <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section 3.1</a> |
|---|
| 954 | </td> |
|---|
| 955 | </tr> |
|---|
| 956 | <tr> |
|---|
| 957 | <td class="left">416</td> |
|---|
| 958 | <td class="left">Requested Range Not Satisfiable</td> |
|---|
| 959 | <td class="left"> <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">Section 3.2</a> |
|---|
| 960 | </td> |
|---|
| 961 | </tr> |
|---|
| 962 | </tbody> |
|---|
| 963 | </table> |
|---|
| 964 | </div> |
|---|
| 965 | <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a> <a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2> |
|---|
| 966 | <p id="rfc.section.6.2.p.1">The Message Header Field Registry located at <<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>> shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>): |
|---|
| 967 | </p> |
|---|
| 968 | <div id="rfc.table.2"> |
|---|
| 969 | <div id="iana.header.registration.table"></div> |
|---|
| 970 | <table class="tt full left" cellpadding="3" cellspacing="0"> |
|---|
| 971 | <thead> |
|---|
| 972 | <tr> |
|---|
| 973 | <th>Header Field Name</th> |
|---|
| 974 | <th>Protocol</th> |
|---|
| 975 | <th>Status</th> |
|---|
| 976 | <th>Reference</th> |
|---|
| 977 | </tr> |
|---|
| 978 | </thead> |
|---|
| 979 | <tbody> |
|---|
| 980 | <tr> |
|---|
| 981 | <td class="left">Accept-Ranges</td> |
|---|
| 982 | <td class="left">http</td> |
|---|
| 983 | <td class="left">standard</td> |
|---|
| 984 | <td class="left"> <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section 5.1</a> |
|---|
| 985 | </td> |
|---|
| 986 | </tr> |
|---|
| 987 | <tr> |
|---|
| 988 | <td class="left">Content-Range</td> |
|---|
| 989 | <td class="left">http</td> |
|---|
| 990 | <td class="left">standard</td> |
|---|
| 991 | <td class="left"> <a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section 5.2</a> |
|---|
| 992 | </td> |
|---|
| 993 | </tr> |
|---|
| 994 | <tr> |
|---|
| 995 | <td class="left">If-Range</td> |
|---|
| 996 | <td class="left">http</td> |
|---|
| 997 | <td class="left">standard</td> |
|---|
| 998 | <td class="left"> <a href="#header.if-range" id="rfc.xref.header.if-range.4" title="If-Range">Section 5.3</a> |
|---|
| 999 | </td> |
|---|
| 1000 | </tr> |
|---|
| 1001 | <tr> |
|---|
| 1002 | <td class="left">Range</td> |
|---|
| 1003 | <td class="left">http</td> |
|---|
| 1004 | <td class="left">standard</td> |
|---|
| 1005 | <td class="left"> <a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section 5.4</a> |
|---|
| 1006 | </td> |
|---|
| 1007 | </tr> |
|---|
| 1008 | </tbody> |
|---|
| 1009 | </table> |
|---|
| 1010 | </div> |
|---|
| 1011 | <p id="rfc.section.6.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> |
|---|
| 1012 | <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a> <a id="range.specifier.registration" href="#range.specifier.registration">Range Specifier Registration</a></h2> |
|---|
| 1013 | <p id="rfc.section.6.3.p.1">The registration procedure for HTTP Range Specifiers is defined by <a href="#range.specifier.registry" title="Range Specifier Registry">Section 2.1</a> of this document. |
|---|
| 1014 | </p> |
|---|
| 1015 | <p id="rfc.section.6.3.p.2">The HTTP Range Specifier Registry shall be created at <<a href="http://www.iana.org/assignments/http-range-specifiers">http://www.iana.org/assignments/http-range-specifiers</a>> and be populated with the registrations below: |
|---|
| 1016 | </p> |
|---|
| 1017 | <div id="rfc.table.3"> |
|---|
| 1018 | <div id="iana.range.specifiers.table"></div> |
|---|
| 1019 | <table class="tt full left" cellpadding="3" cellspacing="0"> |
|---|
| 1020 | <thead> |
|---|
| 1021 | <tr> |
|---|
| 1022 | <th>Range Specifier Name</th> |
|---|
| 1023 | <th>Description</th> |
|---|
| 1024 | <th>Reference</th> |
|---|
| 1025 | </tr> |
|---|
| 1026 | </thead> |
|---|
| 1027 | <tbody> |
|---|
| 1028 | <tr> |
|---|
| 1029 | <td class="left">bytes</td> |
|---|
| 1030 | <td class="left">a range of octets</td> |
|---|
| 1031 | <td class="left">(this specification)</td> |
|---|
| 1032 | </tr> |
|---|
| 1033 | </tbody> |
|---|
| 1034 | </table> |
|---|
| 1035 | </div> |
|---|
| 1036 | <p id="rfc.section.6.3.p.3">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> |
|---|
| 1037 | <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> |
|---|
| 1038 | <p id="rfc.section.7.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1 |
|---|
| 1039 | as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does |
|---|
| 1040 | make some suggestions for reducing security risks. |
|---|
| 1041 | </p> |
|---|
| 1042 | <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a> <a id="overlapping.ranges" href="#overlapping.ranges">Overlapping Ranges</a></h2> |
|---|
| 1043 | <p id="rfc.section.7.1.p.1">Range requests containing overlapping ranges may lead to the situation where a server is sending far more data than the size |
|---|
| 1044 | of the complete resource representation. |
|---|
| 1045 | </p> |
|---|
| 1046 | <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> <a id="acks" href="#acks">Acknowledgments</a></h1> |
|---|
| 1047 | <p id="rfc.section.8.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 12</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. |
|---|
| 1048 | </p> |
|---|
| 1049 | <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References |
|---|
| 1050 | </h1> |
|---|
| 1051 | <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References |
|---|
| 1052 | </h2> |
|---|
| 1053 | <table> |
|---|
| 1054 | <tr> |
|---|
| 1055 | <td class="reference"><b id="Part1">[Part1]</b></td> |
|---|
| 1056 | <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-16">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-16 (work in progress), August 2011. |
|---|
| 1057 | </td> |
|---|
| 1058 | </tr> |
|---|
| 1059 | <tr> |
|---|
| 1060 | <td class="reference"><b id="Part4">[Part4]</b></td> |
|---|
| 1061 | <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-16">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-16 (work in progress), August 2011. |
|---|
| 1062 | </td> |
|---|
| 1063 | </tr> |
|---|
| 1064 | <tr> |
|---|
| 1065 | <td class="reference"><b id="RFC2046">[RFC2046]</b></td> |
|---|
| 1066 | <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" 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. |
|---|
| 1067 | </td> |
|---|
| 1068 | </tr> |
|---|
| 1069 | <tr> |
|---|
| 1070 | <td class="reference"><b id="RFC2119">[RFC2119]</b></td> |
|---|
| 1071 | <td class="top"><a href="mailto:sob@harvard.edu" 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. |
|---|
| 1072 | </td> |
|---|
| 1073 | </tr> |
|---|
| 1074 | <tr> |
|---|
| 1075 | <td class="reference"><b id="RFC5234">[RFC5234]</b></td> |
|---|
| 1076 | <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD 68, RFC 5234, January 2008. |
|---|
| 1077 | </td> |
|---|
| 1078 | </tr> |
|---|
| 1079 | </table> |
|---|
| 1080 | <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References |
|---|
| 1081 | </h2> |
|---|
| 1082 | <table> |
|---|
| 1083 | <tr> |
|---|
| 1084 | <td class="reference"><b id="RFC2616">[RFC2616]</b></td> |
|---|
| 1085 | <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" 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. |
|---|
| 1086 | </td> |
|---|
| 1087 | </tr> |
|---|
| 1088 | <tr> |
|---|
| 1089 | <td class="reference"><b id="RFC3864">[RFC3864]</b></td> |
|---|
| 1090 | <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP 90, RFC 3864, September 2004. |
|---|
| 1091 | </td> |
|---|
| 1092 | </tr> |
|---|
| 1093 | <tr> |
|---|
| 1094 | <td class="reference"><b id="RFC4288">[RFC4288]</b></td> |
|---|
| 1095 | <td class="top"><a href="mailto:ned.freed@mrochek.com" title="Sun Microsystems">Freed, N.</a> and <a href="mailto:klensin+ietf@jck.com">J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP 13, RFC 4288, December 2005. |
|---|
| 1096 | </td> |
|---|
| 1097 | </tr> |
|---|
| 1098 | <tr> |
|---|
| 1099 | <td class="reference"><b id="RFC5226">[RFC5226]</b></td> |
|---|
| 1100 | <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP 26, RFC 5226, May 2008. |
|---|
| 1101 | </td> |
|---|
| 1102 | </tr> |
|---|
| 1103 | </table> |
|---|
| 1104 | <div class="avoidbreak"> |
|---|
| 1105 | <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1> |
|---|
| 1106 | <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span> |
|---|
| 1107 | (editor) |
|---|
| 1108 | <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</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 href="mailto:fielding@gbiv.com"><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> |
|---|
| 1109 | <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">Alcatel-Lucent Bell Labs</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 href="mailto:jg@freedesktop.org"><span class="email">jg@freedesktop.org</span></a></span><span class="vcardline">URI: <a href="http://gettys.wordpress.com/" class="url">http://gettys.wordpress.com/</a></span></address> |
|---|
| 1110 | <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 href="mailto:JeffMogul@acm.org"><span class="email">JeffMogul@acm.org</span></a></span></address> |
|---|
| 1111 | <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 href="mailto:henrikn@microsoft.com"><span class="email">henrikn@microsoft.com</span></a></span></address> |
|---|
| 1112 | <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 href="mailto:LMM@acm.org"><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> |
|---|
| 1113 | <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 href="mailto:paulle@microsoft.com"><span class="email">paulle@microsoft.com</span></a></span></address> |
|---|
| 1114 | <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 href="mailto:timbl@w3.org"><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> |
|---|
| 1115 | <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span> |
|---|
| 1116 | (editor) |
|---|
| 1117 | <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 href="mailto:ylafon@w3.org"><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> |
|---|
| 1118 | <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span> |
|---|
| 1119 | (editor) |
|---|
| 1120 | <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 href="mailto:julian.reschke@greenbytes.de"><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> |
|---|
| 1121 | </div> |
|---|
| 1122 | <div id="rfc.iref.m.1"></div> |
|---|
| 1123 | <div id="rfc.iref.m.2"></div> |
|---|
| 1124 | <h1 id="rfc.section.A" class="np"><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> |
|---|
| 1125 | <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 |
|---|
| 1126 | non-overlapping ranges), these are transmitted as a multipart message-body (<a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="http://tools.ietf.org/html/rfc2046#section-5.1">Section 5.1</a>). The media type for this purpose is called "multipart/byteranges". The following is to be registered with IANA <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>. |
|---|
| 1127 | </p> |
|---|
| 1128 | <div class="note" id="rfc.section.A.p.2"> |
|---|
| 1129 | <p> <b>Note:</b> Despite the name "multipart/byteranges" is not limited to the byte ranges only. |
|---|
| 1130 | </p> |
|---|
| 1131 | </div> |
|---|
| 1132 | <p id="rfc.section.A.p.3">The multipart/byteranges media type includes one or more parts, each with its own Content-Type and Content-Range fields. The |
|---|
| 1133 | required boundary parameter specifies the boundary string used to separate each body-part. |
|---|
| 1134 | </p> |
|---|
| 1135 | <p id="rfc.section.A.p.4"> </p> |
|---|
| 1136 | <dl> |
|---|
| 1137 | <dt>Type name:</dt> |
|---|
| 1138 | <dd>multipart</dd> |
|---|
| 1139 | <dt>Subtype name:</dt> |
|---|
| 1140 | <dd>byteranges</dd> |
|---|
| 1141 | <dt>Required parameters:</dt> |
|---|
| 1142 | <dd>boundary</dd> |
|---|
| 1143 | <dt>Optional parameters:</dt> |
|---|
| 1144 | <dd>none</dd> |
|---|
| 1145 | <dt>Encoding considerations:</dt> |
|---|
| 1146 | <dd>only "7bit", "8bit", or "binary" are permitted</dd> |
|---|
| 1147 | <dt>Security considerations:</dt> |
|---|
| 1148 | <dd>none</dd> |
|---|
| 1149 | <dt>Interoperability considerations:</dt> |
|---|
| 1150 | <dd>none</dd> |
|---|
| 1151 | <dt>Published specification:</dt> |
|---|
| 1152 | <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>). |
|---|
| 1153 | </dd> |
|---|
| 1154 | <dt>Applications that use this media type:</dt> |
|---|
| 1155 | <dt>Additional information:</dt> |
|---|
| 1156 | <dd> |
|---|
| 1157 | <dl> |
|---|
| 1158 | <dt>Magic number(s):</dt> |
|---|
| 1159 | <dd>none</dd> |
|---|
| 1160 | <dt>File extension(s):</dt> |
|---|
| 1161 | <dd>none</dd> |
|---|
| 1162 | <dt>Macintosh file type code(s):</dt> |
|---|
| 1163 | <dd>none</dd> |
|---|
| 1164 | </dl> |
|---|
| 1165 | </dd> |
|---|
| 1166 | <dt>Person and email address to contact for further information:</dt> |
|---|
| 1167 | <dd>See Authors Section.</dd> |
|---|
| 1168 | <dt>Intended usage:</dt> |
|---|
| 1169 | <dd>COMMON</dd> |
|---|
| 1170 | <dt>Restrictions on usage:</dt> |
|---|
| 1171 | <dd>none</dd> |
|---|
| 1172 | <dt>Author/Change controller:</dt> |
|---|
| 1173 | <dd>IESG</dd> |
|---|
| 1174 | </dl> |
|---|
| 1175 | <div id="rfc.figure.u.23"></div> |
|---|
| 1176 | <p>For example:</p><pre class="text"> HTTP/1.1 206 Partial Content |
|---|
| 1177 | Date: Wed, 15 Nov 1995 06:25:24 GMT |
|---|
| 1178 | Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT |
|---|
| 1179 | Content-type: multipart/byteranges; boundary=THIS_STRING_SEPARATES |
|---|
| 1180 | |
|---|
| 1181 | --THIS_STRING_SEPARATES |
|---|
| 1182 | Content-type: application/pdf |
|---|
| 1183 | Content-range: bytes 500-999/8000 |
|---|
| 1184 | |
|---|
| 1185 | ...the first range... |
|---|
| 1186 | --THIS_STRING_SEPARATES |
|---|
| 1187 | Content-type: application/pdf |
|---|
| 1188 | Content-range: bytes 7000-7999/8000 |
|---|
| 1189 | |
|---|
| 1190 | ...the second range |
|---|
| 1191 | --THIS_STRING_SEPARATES-- |
|---|
| 1192 | </pre><div id="rfc.figure.u.24"></div> |
|---|
| 1193 | <p>Other example:</p> <pre class="text"> HTTP/1.1 206 Partial Content |
|---|
| 1194 | Date: Tue, 14 Nov 1995 06:25:24 GMT |
|---|
| 1195 | Last-Modified: Tue, 14 July 04:58:08 GMT |
|---|
| 1196 | Content-type: multipart/byteranges; boundary=THIS_STRING_SEPARATES |
|---|
| 1197 | |
|---|
| 1198 | --THIS_STRING_SEPARATES |
|---|
| 1199 | Content-type: video/example |
|---|
| 1200 | Content-range: exampleunit 1.2-4.3/25 |
|---|
| 1201 | |
|---|
| 1202 | ...the first range... |
|---|
| 1203 | --THIS_STRING_SEPARATES |
|---|
| 1204 | Content-type: video/example |
|---|
| 1205 | Content-range: exampleunit 11.2-14.3/25 |
|---|
| 1206 | |
|---|
| 1207 | ...the second range |
|---|
| 1208 | --THIS_STRING_SEPARATES-- |
|---|
| 1209 | </pre> <p id="rfc.section.A.p.7">Notes: </p> |
|---|
| 1210 | <ol> |
|---|
| 1211 | <li>Additional CRLFs <em class="bcp14">MAY</em> precede the first boundary string in the body. |
|---|
| 1212 | </li> |
|---|
| 1213 | <li>Although <a href="#RFC2046" id="rfc.xref.RFC2046.2"><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. |
|---|
| 1214 | </li> |
|---|
| 1215 | <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. |
|---|
| 1216 | </li> |
|---|
| 1217 | </ol> |
|---|
| 1218 | <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1> |
|---|
| 1219 | <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> |
|---|
| 1220 | <p id="rfc.section.B.1.p.1">Clarify that it is not ok to use a weak validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section 3.1</a>) |
|---|
| 1221 | </p> |
|---|
| 1222 | <p id="rfc.section.B.1.p.2">Change ABNF productions for header fields to only define the field value. (<a href="#header.fields" title="Header Field Definitions">Section 5</a>) |
|---|
| 1223 | </p> |
|---|
| 1224 | <p id="rfc.section.B.1.p.3">Clarify that multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>) |
|---|
| 1225 | </p> |
|---|
| 1226 | <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> |
|---|
| 1227 | <div id="rfc.figure.u.25"></div> <pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = acceptable-ranges |
|---|
| 1228 | |
|---|
| 1229 | <a href="#header.content-range" class="smpl">Content-Range</a> = byte-content-range-spec / other-content-range-spec |
|---|
| 1230 | |
|---|
| 1231 | <a href="#core.rules" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 6.1> |
|---|
| 1232 | |
|---|
| 1233 | <a href="#header.if-range" class="smpl">If-Range</a> = entity-tag / HTTP-date |
|---|
| 1234 | |
|---|
| 1235 | <a href="#core.rules" class="smpl">OWS</a> = <OWS, defined in [Part1], Section 1.2.2> |
|---|
| 1236 | |
|---|
| 1237 | <a href="#range.retrieval.requests" class="smpl">Range</a> = byte-ranges-specifier / other-ranges-specifier |
|---|
| 1238 | |
|---|
| 1239 | <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = ( *( "," OWS ) range-unit *( OWS "," [ OWS |
|---|
| 1240 | range-unit ] ) ) / "none" |
|---|
| 1241 | |
|---|
| 1242 | <a href="#header.content-range" class="smpl">byte-content-range-spec</a> = bytes-unit SP byte-range-resp-spec "/" ( |
|---|
| 1243 | instance-length / "*" ) |
|---|
| 1244 | <a href="#header.content-range" class="smpl">byte-range-resp-spec</a> = ( first-byte-pos "-" last-byte-pos ) / "*" |
|---|
| 1245 | <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = ( *( "," OWS ) byte-range-spec ) / ( |
|---|
| 1246 | suffix-byte-range-spec *( OWS "," [ ( OWS byte-range-spec ) / |
|---|
| 1247 | suffix-byte-range-spec ] ) ) |
|---|
| 1248 | <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = first-byte-pos "-" [ last-byte-pos ] |
|---|
| 1249 | <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = bytes-unit "=" byte-range-set |
|---|
| 1250 | <a href="#range.units" class="smpl">bytes-unit</a> = "bytes" |
|---|
| 1251 | |
|---|
| 1252 | <a href="#abnf.dependencies" class="smpl">entity-tag</a> = <entity-tag, defined in [Part4], Section 2.3> |
|---|
| 1253 | |
|---|
| 1254 | <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> = 1*DIGIT |
|---|
| 1255 | |
|---|
| 1256 | <a href="#header.content-range" class="smpl">instance-length</a> = 1*DIGIT |
|---|
| 1257 | |
|---|
| 1258 | <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> = 1*DIGIT |
|---|
| 1259 | |
|---|
| 1260 | <a href="#header.content-range" class="smpl">other-content-range-spec</a> = other-range-unit SP other-range-resp-spec |
|---|
| 1261 | <a href="#header.content-range" class="smpl">other-range-resp-spec</a> = *CHAR |
|---|
| 1262 | <a href="#range.retrieval.requests" class="smpl">other-range-set</a> = 1*CHAR |
|---|
| 1263 | <a href="#range.units" class="smpl">other-range-unit</a> = token |
|---|
| 1264 | <a href="#range.retrieval.requests" class="smpl">other-ranges-specifier</a> = other-range-unit "=" other-range-set |
|---|
| 1265 | |
|---|
| 1266 | <a href="#range.units" class="smpl">range-unit</a> = bytes-unit / other-range-unit |
|---|
| 1267 | |
|---|
| 1268 | <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" suffix-length |
|---|
| 1269 | <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*DIGIT |
|---|
| 1270 | |
|---|
| 1271 | <a href="#core.rules" class="smpl">token</a> = <token, defined in [Part1], Section 3.2.3> |
|---|
| 1272 | </pre> <div id="rfc.figure.u.26"></div> |
|---|
| 1273 | <p>ABNF diagnostics:</p><pre class="inline">; Accept-Ranges defined but not used |
|---|
| 1274 | ; Content-Range defined but not used |
|---|
| 1275 | ; If-Range defined but not used |
|---|
| 1276 | ; Range defined but not used |
|---|
| 1277 | </pre><h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> |
|---|
| 1278 | <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a> Since RFC 2616 |
|---|
| 1279 | </h2> |
|---|
| 1280 | <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. |
|---|
| 1281 | </p> |
|---|
| 1282 | <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a> Since draft-ietf-httpbis-p5-range-00 |
|---|
| 1283 | </h2> |
|---|
| 1284 | <p id="rfc.section.D.2.p.1">Closed issues: </p> |
|---|
| 1285 | <ul> |
|---|
| 1286 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/18">http://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>>) |
|---|
| 1287 | </li> |
|---|
| 1288 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/35">http://tools.ietf.org/wg/httpbis/trac/ticket/35</a>>: "Normative and Informative references" |
|---|
| 1289 | </li> |
|---|
| 1290 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/86">http://tools.ietf.org/wg/httpbis/trac/ticket/86</a>>: "Normative up-to-date references" |
|---|
| 1291 | </li> |
|---|
| 1292 | </ul> |
|---|
| 1293 | <h2 id="rfc.section.D.3"><a href="#rfc.section.D.3">D.3</a> Since draft-ietf-httpbis-p5-range-01 |
|---|
| 1294 | </h2> |
|---|
| 1295 | <p id="rfc.section.D.3.p.1">Closed issues: </p> |
|---|
| 1296 | <ul> |
|---|
| 1297 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/55">http://tools.ietf.org/wg/httpbis/trac/ticket/55</a>>: "Updating to RFC4288" |
|---|
| 1298 | </li> |
|---|
| 1299 | </ul> |
|---|
| 1300 | <p id="rfc.section.D.3.p.2">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): |
|---|
| 1301 | </p> |
|---|
| 1302 | <ul> |
|---|
| 1303 | <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li> |
|---|
| 1304 | </ul> |
|---|
| 1305 | <h2 id="rfc.section.D.4"><a href="#rfc.section.D.4">D.4</a> <a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p5-range-02</a></h2> |
|---|
| 1306 | <p id="rfc.section.D.4.p.1">Ongoing work on IANA Message Header Field Registration (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>>): |
|---|
| 1307 | </p> |
|---|
| 1308 | <ul> |
|---|
| 1309 | <li>Reference RFC 3984, and update header field registrations for headers defined in this document.</li> |
|---|
| 1310 | </ul> |
|---|
| 1311 | <h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a> <a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p5-range-03</a></h2> |
|---|
| 1312 | <p id="rfc.section.D.5.p.1">None.</p> |
|---|
| 1313 | <h2 id="rfc.section.D.6"><a href="#rfc.section.D.6">D.6</a> <a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p5-range-04</a></h2> |
|---|
| 1314 | <p id="rfc.section.D.6.p.1">Closed issues: </p> |
|---|
| 1315 | <ul> |
|---|
| 1316 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/133">http://tools.ietf.org/wg/httpbis/trac/ticket/133</a>>: "multipart/byteranges minimum number of parts" |
|---|
| 1317 | </li> |
|---|
| 1318 | </ul> |
|---|
| 1319 | <p id="rfc.section.D.6.p.2">Ongoing work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): |
|---|
| 1320 | </p> |
|---|
| 1321 | <ul> |
|---|
| 1322 | <li>Use "/" instead of "|" for alternatives.</li> |
|---|
| 1323 | <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li> |
|---|
| 1324 | <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li> |
|---|
| 1325 | </ul> |
|---|
| 1326 | <h2 id="rfc.section.D.7"><a href="#rfc.section.D.7">D.7</a> <a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p5-range-05</a></h2> |
|---|
| 1327 | <p id="rfc.section.D.7.p.1">Closed issues: </p> |
|---|
| 1328 | <ul> |
|---|
| 1329 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/142">http://tools.ietf.org/wg/httpbis/trac/ticket/142</a>>: "State base for *-byte-pos and suffix-length" |
|---|
| 1330 | </li> |
|---|
| 1331 | </ul> |
|---|
| 1332 | <p id="rfc.section.D.7.p.2">Ongoing work on Custom Ranges (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/85">http://tools.ietf.org/wg/httpbis/trac/ticket/85</a>>): |
|---|
| 1333 | </p> |
|---|
| 1334 | <ul> |
|---|
| 1335 | <li>Remove bias in favor of byte ranges; allow custom ranges in ABNF.</li> |
|---|
| 1336 | </ul> |
|---|
| 1337 | <p id="rfc.section.D.7.p.3">Final work on ABNF conversion (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>): |
|---|
| 1338 | </p> |
|---|
| 1339 | <ul> |
|---|
| 1340 | <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li> |
|---|
| 1341 | </ul> |
|---|
| 1342 | <h2 id="rfc.section.D.8"><a href="#rfc.section.D.8">D.8</a> <a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p5-range-06</a></h2> |
|---|
| 1343 | <p id="rfc.section.D.8.p.1">Closed issues: </p> |
|---|
| 1344 | <ul> |
|---|
| 1345 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/161">http://tools.ietf.org/wg/httpbis/trac/ticket/161</a>>: "base for numeric protocol elements" |
|---|
| 1346 | </li> |
|---|
| 1347 | </ul> |
|---|
| 1348 | <h2 id="rfc.section.D.9"><a href="#rfc.section.D.9">D.9</a> <a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p5-range-07</a></h2> |
|---|
| 1349 | <p id="rfc.section.D.9.p.1">Closed issues: </p> |
|---|
| 1350 | <ul> |
|---|
| 1351 | <li>Fixed discrepancy in the If-Range definition about allowed validators.</li> |
|---|
| 1352 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/150">http://tools.ietf.org/wg/httpbis/trac/ticket/150</a>>: "multipart/byteranges for custom range units" |
|---|
| 1353 | </li> |
|---|
| 1354 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/151">http://tools.ietf.org/wg/httpbis/trac/ticket/151</a>>: "range unit missing from other-ranges-specifier in Range header" |
|---|
| 1355 | </li> |
|---|
| 1356 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/198">http://tools.ietf.org/wg/httpbis/trac/ticket/198</a>>: "move IANA registrations for optional status codes" |
|---|
| 1357 | </li> |
|---|
| 1358 | </ul> |
|---|
| 1359 | <h2 id="rfc.section.D.10"><a href="#rfc.section.D.10">D.10</a> <a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p5-range-08</a></h2> |
|---|
| 1360 | <p id="rfc.section.D.10.p.1">No significant changes.</p> |
|---|
| 1361 | <h2 id="rfc.section.D.11"><a href="#rfc.section.D.11">D.11</a> <a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p5-range-09</a></h2> |
|---|
| 1362 | <p id="rfc.section.D.11.p.1">No significant changes.</p> |
|---|
| 1363 | <h2 id="rfc.section.D.12"><a href="#rfc.section.D.12">D.12</a> <a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p5-range-10</a></h2> |
|---|
| 1364 | <p id="rfc.section.D.12.p.1">Closed issues: </p> |
|---|
| 1365 | <ul> |
|---|
| 1366 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/69">http://tools.ietf.org/wg/httpbis/trac/ticket/69</a>>: "Clarify 'Requested Variant'" |
|---|
| 1367 | </li> |
|---|
| 1368 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/109">http://tools.ietf.org/wg/httpbis/trac/ticket/109</a>>: "Clarify entity / representation / variant terminology" |
|---|
| 1369 | </li> |
|---|
| 1370 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>>: "consider removing the 'changes from 2068' sections" |
|---|
| 1371 | </li> |
|---|
| 1372 | </ul> |
|---|
| 1373 | <p id="rfc.section.D.12.p.2">Ongoing work on Custom Ranges (<<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/85">http://tools.ietf.org/wg/httpbis/trac/ticket/85</a>>): |
|---|
| 1374 | </p> |
|---|
| 1375 | <ul> |
|---|
| 1376 | <li>Add IANA registry.</li> |
|---|
| 1377 | </ul> |
|---|
| 1378 | <h2 id="rfc.section.D.13"><a href="#rfc.section.D.13">D.13</a> <a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p5-range-11</a></h2> |
|---|
| 1379 | <p id="rfc.section.D.13.p.1">Closed issues: </p> |
|---|
| 1380 | <ul> |
|---|
| 1381 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/217">http://tools.ietf.org/wg/httpbis/trac/ticket/217</a>>: "Caches can't be required to serve ranges" |
|---|
| 1382 | </li> |
|---|
| 1383 | </ul> |
|---|
| 1384 | <h2 id="rfc.section.D.14"><a href="#rfc.section.D.14">D.14</a> <a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p5-range-12</a></h2> |
|---|
| 1385 | <p id="rfc.section.D.14.p.1">Closed issues: </p> |
|---|
| 1386 | <ul> |
|---|
| 1387 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>>: "Header Classification" |
|---|
| 1388 | </li> |
|---|
| 1389 | </ul> |
|---|
| 1390 | <h2 id="rfc.section.D.15"><a href="#rfc.section.D.15">D.15</a> <a id="changes.since.13" href="#changes.since.13">Since draft-ietf-httpbis-p5-range-13</a></h2> |
|---|
| 1391 | <p id="rfc.section.D.15.p.1">Closed issues: </p> |
|---|
| 1392 | <ul> |
|---|
| 1393 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>>: "untangle ABNFs for header fields" |
|---|
| 1394 | </li> |
|---|
| 1395 | </ul> |
|---|
| 1396 | <h2 id="rfc.section.D.16"><a href="#rfc.section.D.16">D.16</a> <a id="changes.since.14" href="#changes.since.14">Since draft-ietf-httpbis-p5-range-14</a></h2> |
|---|
| 1397 | <p id="rfc.section.D.16.p.1">None.</p> |
|---|
| 1398 | <h2 id="rfc.section.D.17"><a href="#rfc.section.D.17">D.17</a> <a id="changes.since.15" href="#changes.since.15">Since draft-ietf-httpbis-p5-range-15</a></h2> |
|---|
| 1399 | <p id="rfc.section.D.17.p.1">Closed issues: </p> |
|---|
| 1400 | <ul> |
|---|
| 1401 | <li> <<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/175">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/175</a>>: "Security consideration: range flooding" |
|---|
| 1402 | </li> |
|---|
| 1403 | </ul> |
|---|
| 1404 | <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> |
|---|
| 1405 | <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> |
|---|
| 1406 | </p> |
|---|
| 1407 | <div class="print2col"> |
|---|
| 1408 | <ul class="ind"> |
|---|
| 1409 | <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul> |
|---|
| 1410 | <li>206 Partial Content (status code) <a href="#rfc.iref.3"><b>3.1</b></a>, <a href="#rfc.xref.status.206.1">6.1</a>, <a href="#rfc.xref.status.206.2">B.1</a></li> |
|---|
| 1411 | </ul> |
|---|
| 1412 | </li> |
|---|
| 1413 | <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul> |
|---|
| 1414 | <li>416 Requested Range Not Satisfiable (status code) <a href="#rfc.iref.4"><b>3.2</b></a>, <a href="#rfc.xref.status.416.1">5.2</a>, <a href="#rfc.xref.status.416.2">6.1</a></li> |
|---|
| 1415 | </ul> |
|---|
| 1416 | </li> |
|---|
| 1417 | <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul> |
|---|
| 1418 | <li>Accept-Ranges header field <a href="#rfc.iref.a.1"><b>5.1</b></a>, <a href="#rfc.xref.header.accept-ranges.1">6.2</a></li> |
|---|
| 1419 | </ul> |
|---|
| 1420 | </li> |
|---|
| 1421 | <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul> |
|---|
| 1422 | <li>Content-Range header field <a href="#rfc.xref.header.content-range.1">2</a>, <a href="#rfc.xref.header.content-range.2">3.1</a>, <a href="#rfc.xref.header.content-range.3">3.2</a>, <a href="#rfc.iref.c.1"><b>5.2</b></a>, <a href="#rfc.xref.header.content-range.4">6.2</a></li> |
|---|
| 1423 | </ul> |
|---|
| 1424 | </li> |
|---|
| 1425 | <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul> |
|---|
| 1426 | <li><tt>Grammar</tt> |
|---|
| 1427 | <ul> |
|---|
| 1428 | <li><tt>Accept-Ranges</tt> <a href="#rfc.iref.g.4"><b>5.1</b></a></li> |
|---|
| 1429 | <li><tt>acceptable-ranges</tt> <a href="#rfc.iref.g.5"><b>5.1</b></a></li> |
|---|
| 1430 | <li><tt>byte-content-range-spec</tt> <a href="#rfc.iref.g.7"><b>5.2</b></a></li> |
|---|
| 1431 | <li><tt>byte-range-resp-spec</tt> <a href="#rfc.iref.g.8"><b>5.2</b></a></li> |
|---|
| 1432 | <li><tt>byte-range-set</tt> <a href="#rfc.iref.g.13"><b>5.4.1</b></a></li> |
|---|
| 1433 | <li><tt>byte-range-spec</tt> <a href="#rfc.iref.g.14"><b>5.4.1</b></a></li> |
|---|
| 1434 | <li><tt>byte-ranges-specifier</tt> <a href="#rfc.iref.g.12"><b>5.4.1</b></a></li> |
|---|
| 1435 | <li><tt>bytes-unit</tt> <a href="#rfc.iref.g.2"><b>2</b></a></li> |
|---|
| 1436 | <li><tt>Content-Range</tt> <a href="#rfc.iref.g.6"><b>5.2</b></a></li> |
|---|
| 1437 | <li><tt>first-byte-pos</tt> <a href="#rfc.iref.g.15"><b>5.4.1</b></a></li> |
|---|
| 1438 | <li><tt>If-Range</tt> <a href="#rfc.iref.g.10"><b>5.3</b></a></li> |
|---|
| 1439 | <li><tt>instance-length</tt> <a href="#rfc.iref.g.9"><b>5.2</b></a></li> |
|---|
| 1440 | <li><tt>last-byte-pos</tt> <a href="#rfc.iref.g.16"><b>5.4.1</b></a></li> |
|---|
| 1441 | <li><tt>other-range-unit</tt> <a href="#rfc.iref.g.3"><b>2</b></a></li> |
|---|
| 1442 | <li><tt>Range</tt> <a href="#rfc.iref.g.19"><b>5.4.2</b></a></li> |
|---|
| 1443 | <li><tt>range-unit</tt> <a href="#rfc.iref.g.1"><b>2</b></a></li> |
|---|
| 1444 | <li><tt>ranges-specifier</tt> <a href="#rfc.iref.g.11"><b>5.4.1</b></a></li> |
|---|
| 1445 | <li><tt>suffix-byte-range-spec</tt> <a href="#rfc.iref.g.17"><b>5.4.1</b></a></li> |
|---|
| 1446 | <li><tt>suffix-length</tt> <a href="#rfc.iref.g.18"><b>5.4.1</b></a></li> |
|---|
| 1447 | </ul> |
|---|
| 1448 | </li> |
|---|
| 1449 | </ul> |
|---|
| 1450 | </li> |
|---|
| 1451 | <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul> |
|---|
| 1452 | <li>Header Fields |
|---|
| 1453 | <ul> |
|---|
| 1454 | <li>Accept-Ranges <a href="#rfc.iref.h.1"><b>5.1</b></a>, <a href="#rfc.xref.header.accept-ranges.1">6.2</a></li> |
|---|
| 1455 | <li>Content-Range <a href="#rfc.xref.header.content-range.1">2</a>, <a href="#rfc.xref.header.content-range.2">3.1</a>, <a href="#rfc.xref.header.content-range.3">3.2</a>, <a href="#rfc.iref.h.2"><b>5.2</b></a>, <a href="#rfc.xref.header.content-range.4">6.2</a></li> |
|---|
| 1456 | <li>If-Range <a href="#rfc.xref.header.if-range.1">3.1</a>, <a href="#rfc.xref.header.if-range.2">3.2</a>, <a href="#rfc.iref.h.3"><b>5.3</b></a>, <a href="#rfc.xref.header.if-range.3">5.4.2</a>, <a href="#rfc.xref.header.if-range.4">6.2</a></li> |
|---|
| 1457 | <li>Range <a href="#rfc.xref.header.range.1">2</a>, <a href="#rfc.xref.header.range.2">2</a>, <a href="#rfc.xref.header.range.3">3.1</a>, <a href="#rfc.xref.header.range.4">3.2</a>, <a href="#rfc.iref.h.4"><b>5.4</b></a>, <a href="#rfc.xref.header.range.5">6.2</a></li> |
|---|
| 1458 | </ul> |
|---|
| 1459 | </li> |
|---|
| 1460 | </ul> |
|---|
| 1461 | </li> |
|---|
| 1462 | <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul> |
|---|
| 1463 | <li>If-Range header field <a href="#rfc.xref.header.if-range.1">3.1</a>, <a href="#rfc.xref.header.if-range.2">3.2</a>, <a href="#rfc.iref.i.1"><b>5.3</b></a>, <a href="#rfc.xref.header.if-range.3">5.4.2</a>, <a href="#rfc.xref.header.if-range.4">6.2</a></li> |
|---|
| 1464 | </ul> |
|---|
| 1465 | </li> |
|---|
| 1466 | <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul> |
|---|
| 1467 | <li>Media Type |
|---|
| 1468 | <ul> |
|---|
| 1469 | <li>multipart/byteranges <a href="#rfc.iref.m.1"><b>A</b></a></li> |
|---|
| 1470 | <li>multipart/x-byteranges <a href="#rfc.iref.m.4">A</a></li> |
|---|
| 1471 | </ul> |
|---|
| 1472 | </li> |
|---|
| 1473 | <li>multipart/byteranges Media Type <a href="#rfc.iref.m.2"><b>A</b></a></li> |
|---|
| 1474 | <li>multipart/x-byteranges Media Type <a href="#rfc.iref.m.3">A</a></li> |
|---|
| 1475 | </ul> |
|---|
| 1476 | </li> |
|---|
| 1477 | <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> |
|---|
| 1478 | <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1.2</a>, <a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a>, <a href="#rfc.xref.Part1.6">8</a>, <a href="#Part1"><b>9.1</b></a><ul> |
|---|
| 1479 | <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.1">1.2</a></li> |
|---|
| 1480 | <li><em>Section 1.2.2</em> <a href="#rfc.xref.Part1.3">1.2.1</a></li> |
|---|
| 1481 | <li><em>Section 3.2.3</em> <a href="#rfc.xref.Part1.4">1.2.1</a></li> |
|---|
| 1482 | <li><em>Section 6.1</em> <a href="#rfc.xref.Part1.5">1.2.1</a></li> |
|---|
| 1483 | <li><em>Section 12</em> <a href="#rfc.xref.Part1.6">8</a></li> |
|---|
| 1484 | </ul> |
|---|
| 1485 | </li> |
|---|
| 1486 | <li><em>Part4</em> <a href="#rfc.xref.Part4.1">1.2.2</a>, <a href="#rfc.xref.Part4.2">4</a>, <a href="#rfc.xref.Part4.3">4</a>, <a href="#rfc.xref.Part4.4">5.3</a>, <a href="#rfc.xref.Part4.5">5.3</a>, <a href="#Part4"><b>9.1</b></a><ul> |
|---|
| 1487 | <li><em>Section 2.2.2</em> <a href="#rfc.xref.Part4.3">4</a>, <a href="#rfc.xref.Part4.4">5.3</a>, <a href="#rfc.xref.Part4.5">5.3</a></li> |
|---|
| 1488 | <li><em>Section 2.3</em> <a href="#rfc.xref.Part4.1">1.2.2</a>, <a href="#rfc.xref.Part4.2">4</a></li> |
|---|
| 1489 | </ul> |
|---|
| 1490 | </li> |
|---|
| 1491 | </ul> |
|---|
| 1492 | </li> |
|---|
| 1493 | <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul> |
|---|
| 1494 | <li>Range header field <a href="#rfc.xref.header.range.1">2</a>, <a href="#rfc.xref.header.range.2">2</a>, <a href="#rfc.xref.header.range.3">3.1</a>, <a href="#rfc.xref.header.range.4">3.2</a>, <a href="#rfc.iref.r.1"><b>5.4</b></a>, <a href="#rfc.xref.header.range.5">6.2</a></li> |
|---|
| 1495 | <li><em>RFC2046</em> <a href="#RFC2046"><b>9.1</b></a>, <a href="#rfc.xref.RFC2046.1">A</a>, <a href="#rfc.xref.RFC2046.2">A</a><ul> |
|---|
| 1496 | <li><em>Section 5.1</em> <a href="#rfc.xref.RFC2046.1">A</a></li> |
|---|
| 1497 | </ul> |
|---|
| 1498 | </li> |
|---|
| 1499 | <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>9.1</b></a></li> |
|---|
| 1500 | <li><em>RFC2616</em> <a href="#RFC2616"><b>9.2</b></a>, <a href="#rfc.xref.RFC2616.1">D.1</a></li> |
|---|
| 1501 | <li><em>RFC3864</em> <a href="#rfc.xref.RFC3864.1">6.2</a>, <a href="#RFC3864"><b>9.2</b></a></li> |
|---|
| 1502 | <li><em>RFC4288</em> <a href="#RFC4288"><b>9.2</b></a>, <a href="#rfc.xref.RFC4288.1">A</a></li> |
|---|
| 1503 | <li><em>RFC5226</em> <a href="#rfc.xref.RFC5226.1">2.1</a>, <a href="#RFC5226"><b>9.2</b></a><ul> |
|---|
| 1504 | <li><em>Section 4.1</em> <a href="#rfc.xref.RFC5226.1">2.1</a></li> |
|---|
| 1505 | </ul> |
|---|
| 1506 | </li> |
|---|
| 1507 | <li><em>RFC5234</em> <a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">1.2</a>, <a href="#RFC5234"><b>9.1</b></a><ul> |
|---|
| 1508 | <li><em>Appendix B.1</em> <a href="#rfc.xref.RFC5234.2">1.2</a></li> |
|---|
| 1509 | </ul> |
|---|
| 1510 | </li> |
|---|
| 1511 | </ul> |
|---|
| 1512 | </li> |
|---|
| 1513 | <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul> |
|---|
| 1514 | <li>Status Codes |
|---|
| 1515 | <ul> |
|---|
| 1516 | <li>206 Partial Content <a href="#rfc.iref.s.1"><b>3.1</b></a>, <a href="#rfc.xref.status.206.1">6.1</a>, <a href="#rfc.xref.status.206.2">B.1</a></li> |
|---|
| 1517 | <li>416 Requested Range Not Satisfiable <a href="#rfc.iref.s.2"><b>3.2</b></a>, <a href="#rfc.xref.status.416.1">5.2</a>, <a href="#rfc.xref.status.416.2">6.1</a></li> |
|---|
| 1518 | </ul> |
|---|
| 1519 | </li> |
|---|
| 1520 | </ul> |
|---|
| 1521 | </li> |
|---|
| 1522 | </ul> |
|---|
| 1523 | </div> |
|---|
| 1524 | </body> |
|---|
| 1525 | </html> |
|---|
![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
