| 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>Hypertext Transfer Protocol (HTTP/1.1): Range Requests</title><script> |
|---|
| 7 | var buttonsAdded = false; |
|---|
| 8 | |
|---|
| 9 | function init() { |
|---|
| 10 | var fb = document.createElement("div"); |
|---|
| 11 | fb.className = "feedback noprint"; |
|---|
| 12 | fb.setAttribute("onclick", "feedback();"); |
|---|
| 13 | fb.appendChild(document.createTextNode("feedback")); |
|---|
| 14 | |
|---|
| 15 | var bodyl = document.getElementsByTagName("body"); |
|---|
| 16 | bodyl.item(0).appendChild(fb); |
|---|
| 17 | } |
|---|
| 18 | |
|---|
| 19 | function feedback() { |
|---|
| 20 | toggleButtonsToElementsByName("h1"); |
|---|
| 21 | toggleButtonsToElementsByName("h2"); |
|---|
| 22 | toggleButtonsToElementsByName("h3"); |
|---|
| 23 | toggleButtonsToElementsByName("h4"); |
|---|
| 24 | |
|---|
| 25 | buttonsAdded = !buttonsAdded; |
|---|
| 26 | } |
|---|
| 27 | |
|---|
| 28 | function toggleButtonsToElementsByName(name) { |
|---|
| 29 | var list = document.getElementsByTagName(name); |
|---|
| 30 | for (var i = 0; i < list.length; i++) { |
|---|
| 31 | toggleButton(list.item(i)); |
|---|
| 32 | } |
|---|
| 33 | } |
|---|
| 34 | |
|---|
| 35 | function toggleButton(node) { |
|---|
| 36 | if (! buttonsAdded) { |
|---|
| 37 | |
|---|
| 38 | // docname |
|---|
| 39 | var template = "mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&body=<{ref}>:"; |
|---|
| 40 | |
|---|
| 41 | var id = node.getAttribute("id"); |
|---|
| 42 | // better id available? |
|---|
| 43 | var titlelinks = node.getElementsByTagName("a"); |
|---|
| 44 | for (var i = 0; i < titlelinks.length; i++) { |
|---|
| 45 | var tl = titlelinks.item(i); |
|---|
| 46 | if (tl.getAttribute("id")) { |
|---|
| 47 | id = tl.getAttribute("id"); |
|---|
| 48 | } |
|---|
| 49 | } |
|---|
| 50 | |
|---|
| 51 | // ref |
|---|
| 52 | var ref = window.location.toString(); |
|---|
| 53 | var hash = ref.indexOf("#"); |
|---|
| 54 | if (hash != -1) { |
|---|
| 55 | ref = ref.substring(0, hash); |
|---|
| 56 | } |
|---|
| 57 | if (id != "") { |
|---|
| 58 | ref += "#" + id; |
|---|
| 59 | } |
|---|
| 60 | |
|---|
| 61 | // docname |
|---|
| 62 | var docname = "draft-ietf-httpbis-p5-range-latest"; |
|---|
| 63 | |
|---|
| 64 | // section |
|---|
| 65 | var section = node.textContent; |
|---|
| 66 | section = section.replace("\u00a0", " "); |
|---|
| 67 | |
|---|
| 68 | // build URI from template |
|---|
| 69 | var uri = template.replace("{docname}", encodeURIComponent(docname)); |
|---|
| 70 | uri = uri.replace("{section}", encodeURIComponent(section)); |
|---|
| 71 | uri = uri.replace("{ref}", encodeURIComponent(ref)); |
|---|
| 72 | |
|---|
| 73 | var button = document.createElement("a"); |
|---|
| 74 | button.className = "fbbutton noprint"; |
|---|
| 75 | button.setAttribute("href", uri); |
|---|
| 76 | button.appendChild(document.createTextNode("send feedback")); |
|---|
| 77 | node.appendChild(button); |
|---|
| 78 | } |
|---|
| 79 | else { |
|---|
| 80 | var buttons = node.getElementsByTagName("a"); |
|---|
| 81 | for (var i = 0; i < buttons.length; i++) { |
|---|
| 82 | var b = buttons.item(i); |
|---|
| 83 | if (b.className == "fbbutton noprint") { |
|---|
| 84 | node.removeChild(b); |
|---|
| 85 | } |
|---|
| 86 | } |
|---|
| 87 | } |
|---|
| 88 | }</script><style type="text/css" title="Xml2Rfc (sans serif)"> |
|---|
| 89 | a { |
|---|
| 90 | text-decoration: none; |
|---|
| 91 | } |
|---|
| 92 | a.smpl { |
|---|
| 93 | color: black; |
|---|
| 94 | } |
|---|
| 95 | a:hover { |
|---|
| 96 | text-decoration: underline; |
|---|
| 97 | } |
|---|
| 98 | a:active { |
|---|
| 99 | text-decoration: underline; |
|---|
| 100 | } |
|---|
| 101 | address { |
|---|
| 102 | margin-top: 1em; |
|---|
| 103 | margin-left: 2em; |
|---|
| 104 | font-style: normal; |
|---|
| 105 | } |
|---|
| 106 | body { |
|---|
| 107 | color: black; |
|---|
| 108 | font-family: verdana, helvetica, arial, sans-serif; |
|---|
| 109 | font-size: 10pt; |
|---|
| 110 | margin-right: 2em; |
|---|
| 111 | } |
|---|
| 112 | cite { |
|---|
| 113 | font-style: normal; |
|---|
| 114 | } |
|---|
| 115 | div.note { |
|---|
| 116 | margin-left: 2em; |
|---|
| 117 | } |
|---|
| 118 | dl { |
|---|
| 119 | margin-left: 2em; |
|---|
| 120 | } |
|---|
| 121 | ul.empty { |
|---|
| 122 | list-style-type: none; |
|---|
| 123 | } |
|---|
| 124 | ul.empty li { |
|---|
| 125 | margin-top: .5em; |
|---|
| 126 | } |
|---|
| 127 | dl p { |
|---|
| 128 | margin-left: 0em; |
|---|
| 129 | } |
|---|
| 130 | dt { |
|---|
| 131 | margin-top: .5em; |
|---|
| 132 | } |
|---|
| 133 | h1 { |
|---|
| 134 | font-size: 14pt; |
|---|
| 135 | line-height: 21pt; |
|---|
| 136 | page-break-after: avoid; |
|---|
| 137 | } |
|---|
| 138 | h1.np { |
|---|
| 139 | page-break-before: always; |
|---|
| 140 | } |
|---|
| 141 | h1 a { |
|---|
| 142 | color: #333333; |
|---|
| 143 | } |
|---|
| 144 | h2 { |
|---|
| 145 | font-size: 12pt; |
|---|
| 146 | line-height: 15pt; |
|---|
| 147 | page-break-after: avoid; |
|---|
| 148 | } |
|---|
| 149 | h3, h4, h5, h6 { |
|---|
| 150 | font-size: 10pt; |
|---|
| 151 | page-break-after: avoid; |
|---|
| 152 | } |
|---|
| 153 | h2 a, h3 a, h4 a, h5 a, h6 a { |
|---|
| 154 | color: black; |
|---|
| 155 | } |
|---|
| 156 | img { |
|---|
| 157 | margin-left: 3em; |
|---|
| 158 | } |
|---|
| 159 | li { |
|---|
| 160 | margin-left: 2em; |
|---|
| 161 | } |
|---|
| 162 | ol { |
|---|
| 163 | margin-left: 2em; |
|---|
| 164 | } |
|---|
| 165 | ol.la { |
|---|
| 166 | list-style-type: lower-alpha; |
|---|
| 167 | } |
|---|
| 168 | ol.ua { |
|---|
| 169 | list-style-type: upper-alpha; |
|---|
| 170 | } |
|---|
| 171 | ol p { |
|---|
| 172 | margin-left: 0em; |
|---|
| 173 | } |
|---|
| 174 | p { |
|---|
| 175 | margin-left: 2em; |
|---|
| 176 | } |
|---|
| 177 | pre { |
|---|
| 178 | margin-left: 3em; |
|---|
| 179 | background-color: lightyellow; |
|---|
| 180 | padding: .25em; |
|---|
| 181 | page-break-inside: avoid; |
|---|
| 182 | } |
|---|
| 183 | pre.text2 { |
|---|
| 184 | border-style: dotted; |
|---|
| 185 | border-width: 1px; |
|---|
| 186 | background-color: #f0f0f0; |
|---|
| 187 | width: 69em; |
|---|
| 188 | } |
|---|
| 189 | pre.inline { |
|---|
| 190 | background-color: white; |
|---|
| 191 | padding: 0em; |
|---|
| 192 | } |
|---|
| 193 | pre.text { |
|---|
| 194 | border-style: dotted; |
|---|
| 195 | border-width: 1px; |
|---|
| 196 | background-color: #f8f8f8; |
|---|
| 197 | width: 69em; |
|---|
| 198 | } |
|---|
| 199 | pre.drawing { |
|---|
| 200 | border-style: solid; |
|---|
| 201 | border-width: 1px; |
|---|
| 202 | background-color: #f8f8f8; |
|---|
| 203 | padding: 2em; |
|---|
| 204 | } |
|---|
| 205 | table { |
|---|
| 206 | margin-left: 2em; |
|---|
| 207 | } |
|---|
| 208 | table.tt { |
|---|
| 209 | vertical-align: top; |
|---|
| 210 | } |
|---|
| 211 | table.full { |
|---|
| 212 | border-style: outset; |
|---|
| 213 | border-width: 1px; |
|---|
| 214 | } |
|---|
| 215 | table.headers { |
|---|
| 216 | border-style: outset; |
|---|
| 217 | border-width: 1px; |
|---|
| 218 | } |
|---|
| 219 | table.tt td { |
|---|
| 220 | vertical-align: top; |
|---|
| 221 | } |
|---|
| 222 | table.full td { |
|---|
| 223 | border-style: inset; |
|---|
| 224 | border-width: 1px; |
|---|
| 225 | } |
|---|
| 226 | table.tt th { |
|---|
| 227 | vertical-align: top; |
|---|
| 228 | } |
|---|
| 229 | table.full th { |
|---|
| 230 | border-style: inset; |
|---|
| 231 | border-width: 1px; |
|---|
| 232 | } |
|---|
| 233 | table.headers th { |
|---|
| 234 | border-style: none none inset none; |
|---|
| 235 | border-width: 1px; |
|---|
| 236 | } |
|---|
| 237 | table.left { |
|---|
| 238 | margin-right: auto; |
|---|
| 239 | } |
|---|
| 240 | table.right { |
|---|
| 241 | margin-left: auto; |
|---|
| 242 | } |
|---|
| 243 | table.center { |
|---|
| 244 | margin-left: auto; |
|---|
| 245 | margin-right: auto; |
|---|
| 246 | } |
|---|
| 247 | caption { |
|---|
| 248 | caption-side: bottom; |
|---|
| 249 | font-weight: bold; |
|---|
| 250 | font-size: 9pt; |
|---|
| 251 | margin-top: .5em; |
|---|
| 252 | } |
|---|
| 253 | |
|---|
| 254 | table.header { |
|---|
| 255 | border-spacing: 1px; |
|---|
| 256 | width: 95%; |
|---|
| 257 | font-size: 10pt; |
|---|
| 258 | color: white; |
|---|
| 259 | } |
|---|
| 260 | td.top { |
|---|
| 261 | vertical-align: top; |
|---|
| 262 | } |
|---|
| 263 | td.topnowrap { |
|---|
| 264 | vertical-align: top; |
|---|
| 265 | white-space: nowrap; |
|---|
| 266 | } |
|---|
| 267 | table.header td { |
|---|
| 268 | background-color: gray; |
|---|
| 269 | width: 50%; |
|---|
| 270 | } |
|---|
| 271 | table.header a { |
|---|
| 272 | color: white; |
|---|
| 273 | } |
|---|
| 274 | td.reference { |
|---|
| 275 | vertical-align: top; |
|---|
| 276 | white-space: nowrap; |
|---|
| 277 | padding-right: 1em; |
|---|
| 278 | } |
|---|
| 279 | thead { |
|---|
| 280 | display:table-header-group; |
|---|
| 281 | } |
|---|
| 282 | ul.toc, ul.toc ul { |
|---|
| 283 | list-style: none; |
|---|
| 284 | margin-left: 1.5em; |
|---|
| 285 | padding-left: 0em; |
|---|
| 286 | } |
|---|
| 287 | ul.toc li { |
|---|
| 288 | line-height: 150%; |
|---|
| 289 | font-weight: bold; |
|---|
| 290 | font-size: 10pt; |
|---|
| 291 | margin-left: 0em; |
|---|
| 292 | } |
|---|
| 293 | ul.toc li li { |
|---|
| 294 | line-height: normal; |
|---|
| 295 | font-weight: normal; |
|---|
| 296 | font-size: 9pt; |
|---|
| 297 | margin-left: 0em; |
|---|
| 298 | } |
|---|
| 299 | li.excluded { |
|---|
| 300 | font-size: 0pt; |
|---|
| 301 | } |
|---|
| 302 | ul p { |
|---|
| 303 | margin-left: 0em; |
|---|
| 304 | } |
|---|
| 305 | ul.ind, ul.ind ul { |
|---|
| 306 | list-style: none; |
|---|
| 307 | margin-left: 1.5em; |
|---|
| 308 | padding-left: 0em; |
|---|
| 309 | page-break-before: avoid; |
|---|
| 310 | } |
|---|
| 311 | ul.ind li { |
|---|
| 312 | font-weight: bold; |
|---|
| 313 | line-height: 200%; |
|---|
| 314 | margin-left: 0em; |
|---|
| 315 | } |
|---|
| 316 | ul.ind li li { |
|---|
| 317 | font-weight: normal; |
|---|
| 318 | line-height: 150%; |
|---|
| 319 | margin-left: 0em; |
|---|
| 320 | } |
|---|
| 321 | .avoidbreak { |
|---|
| 322 | page-break-inside: avoid; |
|---|
| 323 | } |
|---|
| 324 | .bcp14 { |
|---|
| 325 | font-style: normal; |
|---|
| 326 | text-transform: lowercase; |
|---|
| 327 | font-variant: small-caps; |
|---|
| 328 | } |
|---|
| 329 | .comment { |
|---|
| 330 | background-color: yellow; |
|---|
| 331 | } |
|---|
| 332 | .center { |
|---|
| 333 | text-align: center; |
|---|
| 334 | } |
|---|
| 335 | .error { |
|---|
| 336 | color: red; |
|---|
| 337 | font-style: italic; |
|---|
| 338 | font-weight: bold; |
|---|
| 339 | } |
|---|
| 340 | .figure { |
|---|
| 341 | font-weight: bold; |
|---|
| 342 | text-align: center; |
|---|
| 343 | font-size: 9pt; |
|---|
| 344 | } |
|---|
| 345 | .filename { |
|---|
| 346 | color: #333333; |
|---|
| 347 | font-weight: bold; |
|---|
| 348 | font-size: 12pt; |
|---|
| 349 | line-height: 21pt; |
|---|
| 350 | text-align: center; |
|---|
| 351 | } |
|---|
| 352 | .fn { |
|---|
| 353 | font-weight: bold; |
|---|
| 354 | } |
|---|
| 355 | .hidden { |
|---|
| 356 | display: none; |
|---|
| 357 | } |
|---|
| 358 | .left { |
|---|
| 359 | text-align: left; |
|---|
| 360 | } |
|---|
| 361 | .right { |
|---|
| 362 | text-align: right; |
|---|
| 363 | } |
|---|
| 364 | .title { |
|---|
| 365 | color: #990000; |
|---|
| 366 | font-size: 18pt; |
|---|
| 367 | line-height: 18pt; |
|---|
| 368 | font-weight: bold; |
|---|
| 369 | text-align: center; |
|---|
| 370 | margin-top: 36pt; |
|---|
| 371 | } |
|---|
| 372 | .vcardline { |
|---|
| 373 | display: block; |
|---|
| 374 | } |
|---|
| 375 | .warning { |
|---|
| 376 | font-size: 14pt; |
|---|
| 377 | background-color: yellow; |
|---|
| 378 | } |
|---|
| 379 | .feedback { |
|---|
| 380 | position: fixed; |
|---|
| 381 | bottom: 1%; |
|---|
| 382 | right: 1%; |
|---|
| 383 | padding: 3px 5px; |
|---|
| 384 | color: white; |
|---|
| 385 | border-radius: 5px; |
|---|
| 386 | background: #a00000; |
|---|
| 387 | border: 1px solid silver; |
|---|
| 388 | } |
|---|
| 389 | .fbbutton { |
|---|
| 390 | margin-left: 1em; |
|---|
| 391 | color: #303030; |
|---|
| 392 | font-size: small; |
|---|
| 393 | font-weight: normal; |
|---|
| 394 | background: #d0d000; |
|---|
| 395 | padding: 1px 4px; |
|---|
| 396 | border: 1px solid silver; |
|---|
| 397 | border-radius: 5px; |
|---|
| 398 | } |
|---|
| 399 | |
|---|
| 400 | @media print { |
|---|
| 401 | .noprint { |
|---|
| 402 | display: none; |
|---|
| 403 | } |
|---|
| 404 | |
|---|
| 405 | a { |
|---|
| 406 | color: black; |
|---|
| 407 | text-decoration: none; |
|---|
| 408 | } |
|---|
| 409 | |
|---|
| 410 | table.header { |
|---|
| 411 | width: 90%; |
|---|
| 412 | } |
|---|
| 413 | |
|---|
| 414 | td.header { |
|---|
| 415 | width: 50%; |
|---|
| 416 | color: black; |
|---|
| 417 | background-color: white; |
|---|
| 418 | vertical-align: top; |
|---|
| 419 | font-size: 12pt; |
|---|
| 420 | } |
|---|
| 421 | |
|---|
| 422 | ul.toc a:nth-child(2)::after { |
|---|
| 423 | content: leader('.') target-counter(attr(href), page); |
|---|
| 424 | } |
|---|
| 425 | |
|---|
| 426 | ul.ind li li a { |
|---|
| 427 | content: target-counter(attr(href), page); |
|---|
| 428 | } |
|---|
| 429 | |
|---|
| 430 | .print2col { |
|---|
| 431 | column-count: 2; |
|---|
| 432 | -moz-column-count: 2; |
|---|
| 433 | column-fill: auto; |
|---|
| 434 | } |
|---|
| 435 | } |
|---|
| 436 | |
|---|
| 437 | @page { |
|---|
| 438 | @top-left { |
|---|
| 439 | content: "Internet-Draft"; |
|---|
| 440 | } |
|---|
| 441 | @top-right { |
|---|
| 442 | content: "June 2013"; |
|---|
| 443 | } |
|---|
| 444 | @top-center { |
|---|
| 445 | content: "HTTP/1.1 Range Requests"; |
|---|
| 446 | } |
|---|
| 447 | @bottom-left { |
|---|
| 448 | content: "Fielding, et al."; |
|---|
| 449 | } |
|---|
| 450 | @bottom-center { |
|---|
| 451 | content: "Expires December 14, 2013"; |
|---|
| 452 | } |
|---|
| 453 | @bottom-right { |
|---|
| 454 | content: "[Page " counter(page) "]"; |
|---|
| 455 | } |
|---|
| 456 | } |
|---|
| 457 | |
|---|
| 458 | @page:first { |
|---|
| 459 | @top-left { |
|---|
| 460 | content: normal; |
|---|
| 461 | } |
|---|
| 462 | @top-right { |
|---|
| 463 | content: normal; |
|---|
| 464 | } |
|---|
| 465 | @top-center { |
|---|
| 466 | content: normal; |
|---|
| 467 | } |
|---|
| 468 | } |
|---|
| 469 | </style><link rel="Contents" href="#rfc.toc"> |
|---|
| 470 | <link rel="Author" href="#rfc.authors"> |
|---|
| 471 | <link rel="Copyright" href="#rfc.copyrightnotice"> |
|---|
| 472 | <link rel="Index" href="#rfc.index"> |
|---|
| 473 | <link rel="Chapter" title="1 Introduction" href="#rfc.section.1"> |
|---|
| 474 | <link rel="Chapter" title="2 Range Units" href="#rfc.section.2"> |
|---|
| 475 | <link rel="Chapter" title="3 Range Requests" href="#rfc.section.3"> |
|---|
| 476 | <link rel="Chapter" title="4 Responses to a Range Request" href="#rfc.section.4"> |
|---|
| 477 | <link rel="Chapter" title="5 IANA Considerations" href="#rfc.section.5"> |
|---|
| 478 | <link rel="Chapter" title="6 Security Considerations" href="#rfc.section.6"> |
|---|
| 479 | <link rel="Chapter" title="7 Acknowledgments" href="#rfc.section.7"> |
|---|
| 480 | <link rel="Chapter" href="#rfc.section.8" title="8 References"> |
|---|
| 481 | <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A"> |
|---|
| 482 | <link rel="Appendix" title="B Changes from RFC 2616" href="#rfc.section.B"> |
|---|
| 483 | <link rel="Appendix" title="C Imported ABNF" href="#rfc.section.C"> |
|---|
| 484 | <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D"> |
|---|
| 485 | <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E"> |
|---|
| 486 | <link href="p4-conditional.html" rel="prev"> |
|---|
| 487 | <link href="p6-cache.html" rel="next"> |
|---|
| 488 | <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.597, 2013/05/27 06:39:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> |
|---|
| 489 | <link rel="schema.dct" href="http://purl.org/dc/terms/"> |
|---|
| 490 | <meta name="dct.creator" content="Fielding, R."> |
|---|
| 491 | <meta name="dct.creator" content="Lafon, Y."> |
|---|
| 492 | <meta name="dct.creator" content="Reschke, J. F."> |
|---|
| 493 | <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> |
|---|
| 494 | <meta name="dct.issued" scheme="ISO8601" content="2013-06-12"> |
|---|
| 495 | <meta name="dct.replaces" content="urn:ietf:rfc:2616"> |
|---|
| 496 | <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests."> |
|---|
| 497 | <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests."> |
|---|
| 498 | </head> |
|---|
| 499 | <body onload="init();"> |
|---|
| 500 | <table class="header"> |
|---|
| 501 | <tbody> |
|---|
| 502 | <tr> |
|---|
| 503 | <td class="left">HTTPbis Working Group</td> |
|---|
| 504 | <td class="right">R. Fielding, Editor</td> |
|---|
| 505 | </tr> |
|---|
| 506 | <tr> |
|---|
| 507 | <td class="left">Internet-Draft</td> |
|---|
| 508 | <td class="right">Adobe</td> |
|---|
| 509 | </tr> |
|---|
| 510 | <tr> |
|---|
| 511 | <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) |
|---|
| 512 | </td> |
|---|
| 513 | <td class="right">Y. Lafon, Editor</td> |
|---|
| 514 | </tr> |
|---|
| 515 | <tr> |
|---|
| 516 | <td class="left">Intended status: Standards Track</td> |
|---|
| 517 | <td class="right">W3C</td> |
|---|
| 518 | </tr> |
|---|
| 519 | <tr> |
|---|
| 520 | <td class="left">Expires: December 14, 2013</td> |
|---|
| 521 | <td class="right">J. Reschke, Editor</td> |
|---|
| 522 | </tr> |
|---|
| 523 | <tr> |
|---|
| 524 | <td class="left"></td> |
|---|
| 525 | <td class="right">greenbytes</td> |
|---|
| 526 | </tr> |
|---|
| 527 | <tr> |
|---|
| 528 | <td class="left"></td> |
|---|
| 529 | <td class="right">June 12, 2013</td> |
|---|
| 530 | </tr> |
|---|
| 531 | </tbody> |
|---|
| 532 | </table> |
|---|
| 533 | <p class="title">Hypertext Transfer Protocol (HTTP/1.1): Range Requests<br><span class="filename">draft-ietf-httpbis-p5-range-latest</span></p> |
|---|
| 534 | <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> |
|---|
| 535 | <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information |
|---|
| 536 | systems. This document defines range requests and the rules for constructing and combining responses to those requests. |
|---|
| 537 | </p> |
|---|
| 538 | <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> |
|---|
| 539 | <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at <<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>>. |
|---|
| 540 | </p> |
|---|
| 541 | <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>>. |
|---|
| 542 | </p> |
|---|
| 543 | <p>The changes in this draft are summarized in <a href="#changes.since.22" title="Since draft-ietf-httpbis-p5-range-22">Appendix E.4</a>. |
|---|
| 544 | </p> |
|---|
| 545 | <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1> |
|---|
| 546 | <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p> |
|---|
| 547 | <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute |
|---|
| 548 | 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>. |
|---|
| 549 | </p> |
|---|
| 550 | <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other |
|---|
| 551 | documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work |
|---|
| 552 | in progress”. |
|---|
| 553 | </p> |
|---|
| 554 | <p>This Internet-Draft will expire on December 14, 2013.</p> |
|---|
| 555 | <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> |
|---|
| 556 | <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> |
|---|
| 557 | <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 |
|---|
| 558 | and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License |
|---|
| 559 | text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified |
|---|
| 560 | BSD License. |
|---|
| 561 | </p> |
|---|
| 562 | <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November |
|---|
| 563 | 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to |
|---|
| 564 | allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) |
|---|
| 565 | controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative |
|---|
| 566 | works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate |
|---|
| 567 | it into languages other than English. |
|---|
| 568 | </p> |
|---|
| 569 | <hr class="noprint"> |
|---|
| 570 | <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1> |
|---|
| 571 | <ul class="toc"> |
|---|
| 572 | <li><a href="#rfc.section.1">1.</a> <a href="#introduction">Introduction</a><ul> |
|---|
| 573 | <li><a href="#rfc.section.1.1">1.1</a> <a href="#conformance">Conformance and Error Handling</a></li> |
|---|
| 574 | <li><a href="#rfc.section.1.2">1.2</a> <a href="#notation">Syntax Notation</a></li> |
|---|
| 575 | </ul> |
|---|
| 576 | </li> |
|---|
| 577 | <li><a href="#rfc.section.2">2.</a> <a href="#range.units">Range Units</a><ul> |
|---|
| 578 | <li><a href="#rfc.section.2.1">2.1</a> <a href="#byte.ranges">Byte Ranges</a></li> |
|---|
| 579 | <li><a href="#rfc.section.2.2">2.2</a> <a href="#range.units.other">Other Range Units</a></li> |
|---|
| 580 | <li><a href="#rfc.section.2.3">2.3</a> <a href="#header.accept-ranges">Accept-Ranges</a></li> |
|---|
| 581 | </ul> |
|---|
| 582 | </li> |
|---|
| 583 | <li><a href="#rfc.section.3">3.</a> <a href="#range.requests">Range Requests</a><ul> |
|---|
| 584 | <li><a href="#rfc.section.3.1">3.1</a> <a href="#header.range">Range</a></li> |
|---|
| 585 | <li><a href="#rfc.section.3.2">3.2</a> <a href="#header.if-range">If-Range</a></li> |
|---|
| 586 | </ul> |
|---|
| 587 | </li> |
|---|
| 588 | <li><a href="#rfc.section.4">4.</a> <a href="#range.response">Responses to a Range Request</a><ul> |
|---|
| 589 | <li><a href="#rfc.section.4.1">4.1</a> <a href="#status.206">206 Partial Content</a></li> |
|---|
| 590 | <li><a href="#rfc.section.4.2">4.2</a> <a href="#header.content-range">Content-Range</a></li> |
|---|
| 591 | <li><a href="#rfc.section.4.3">4.3</a> <a href="#combining.byte.ranges">Combining Ranges</a></li> |
|---|
| 592 | <li><a href="#rfc.section.4.4">4.4</a> <a href="#status.416">416 Range Not Satisfiable</a></li> |
|---|
| 593 | </ul> |
|---|
| 594 | </li> |
|---|
| 595 | <li><a href="#rfc.section.5">5.</a> <a href="#IANA.considerations">IANA Considerations</a><ul> |
|---|
| 596 | <li><a href="#rfc.section.5.1">5.1</a> <a href="#range.unit.registry">Range Unit Registry</a><ul> |
|---|
| 597 | <li><a href="#rfc.section.5.1.1">5.1.1</a> <a href="#range.unit.registry.procedure">Procedure</a></li> |
|---|
| 598 | <li><a href="#rfc.section.5.1.2">5.1.2</a> <a href="#range.unit.registration">Registrations</a></li> |
|---|
| 599 | </ul> |
|---|
| 600 | </li> |
|---|
| 601 | <li><a href="#rfc.section.5.2">5.2</a> <a href="#status.code.registration">Status Code Registration</a></li> |
|---|
| 602 | <li><a href="#rfc.section.5.3">5.3</a> <a href="#header.field.registration">Header Field Registration</a></li> |
|---|
| 603 | </ul> |
|---|
| 604 | </li> |
|---|
| 605 | <li><a href="#rfc.section.6">6.</a> <a href="#security.considerations">Security Considerations</a><ul> |
|---|
| 606 | <li><a href="#rfc.section.6.1">6.1</a> <a href="#overlapping.ranges">Denial of Service Attacks using Range</a></li> |
|---|
| 607 | </ul> |
|---|
| 608 | </li> |
|---|
| 609 | <li><a href="#rfc.section.7">7.</a> <a href="#acks">Acknowledgments</a></li> |
|---|
| 610 | <li><a href="#rfc.section.8">8.</a> <a href="#rfc.references">References</a><ul> |
|---|
| 611 | <li><a href="#rfc.section.8.1">8.1</a> <a href="#rfc.references.1">Normative References</a></li> |
|---|
| 612 | <li><a href="#rfc.section.8.2">8.2</a> <a href="#rfc.references.2">Informative References</a></li> |
|---|
| 613 | </ul> |
|---|
| 614 | </li> |
|---|
| 615 | <li><a href="#rfc.authors">Authors' Addresses</a></li> |
|---|
| 616 | <li><a href="#rfc.section.A">A.</a> <a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li> |
|---|
| 617 | <li><a href="#rfc.section.B">B.</a> <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> |
|---|
| 618 | <li><a href="#rfc.section.C">C.</a> <a href="#imported.abnf">Imported ABNF</a></li> |
|---|
| 619 | <li><a href="#rfc.section.D">D.</a> <a href="#collected.abnf">Collected ABNF</a></li> |
|---|
| 620 | <li><a href="#rfc.section.E">E.</a> <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul> |
|---|
| 621 | <li><a href="#rfc.section.E.1">E.1</a> <a href="#changes.since.19">Since draft-ietf-httpbis-p5-range-19</a></li> |
|---|
| 622 | <li><a href="#rfc.section.E.2">E.2</a> <a href="#changes.since.20">Since draft-ietf-httpbis-p5-range-20</a></li> |
|---|
| 623 | <li><a href="#rfc.section.E.3">E.3</a> <a href="#changes.since.21">Since draft-ietf-httpbis-p5-range-21</a></li> |
|---|
| 624 | <li><a href="#rfc.section.E.4">E.4</a> <a href="#changes.since.22">Since draft-ietf-httpbis-p5-range-22</a></li> |
|---|
| 625 | </ul> |
|---|
| 626 | </li> |
|---|
| 627 | <li><a href="#rfc.index">Index</a></li> |
|---|
| 628 | </ul> |
|---|
| 629 | <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> <a id="introduction" href="#introduction">Introduction</a></h1> |
|---|
| 630 | <p id="rfc.section.1.p.1">Hypertext Transfer Protocol (HTTP) clients often encounter interrupted data transfers as a result of canceled requests or |
|---|
| 631 | dropped connections. When a client has stored a partial representation, it is desirable to request the remainder of that representation |
|---|
| 632 | in a subsequent request rather than transfer the entire representation. Likewise, devices with limited local storage might |
|---|
| 633 | benefit from being able to request only a subset of a larger representation, such as a single page of a very large document, |
|---|
| 634 | or the dimensions of an embedded image. |
|---|
| 635 | </p> |
|---|
| 636 | <p id="rfc.section.1.p.2">This document defines HTTP/1.1 range requests, partial responses, and the multipart/byteranges media type. Range requests |
|---|
| 637 | are an <em class="bcp14">OPTIONAL</em> feature of HTTP, designed so that recipients not implementing this feature (or not supporting it for the target resource) |
|---|
| 638 | can respond as if it is a normal GET request without impacting interoperability. Partial responses are indicated by a distinct |
|---|
| 639 | status code to not be mistaken for full responses by caches that might not implement the feature. |
|---|
| 640 | </p> |
|---|
| 641 | <p id="rfc.section.1.p.3">Although the range request mechanism is designed to allow for extensible range types, this specification only defines requests |
|---|
| 642 | for byte ranges. |
|---|
| 643 | </p> |
|---|
| 644 | <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a> <a id="conformance" href="#conformance">Conformance and Error Handling</a></h2> |
|---|
| 645 | <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" |
|---|
| 646 | 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>. |
|---|
| 647 | </p> |
|---|
| 648 | <p id="rfc.section.1.1.p.2">Conformance criteria and considerations regarding error handling are defined in <a href="p1-messaging.html#conformance" title="Conformance and Error Handling">Section 2.5</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. |
|---|
| 649 | </p> |
|---|
| 650 | <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a> <a id="notation" href="#notation">Syntax Notation</a></h2> |
|---|
| 651 | <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. <a href="#imported.abnf" title="Imported ABNF">Appendix C</a> describes rules imported from other documents. <a href="#collected.abnf" title="Collected ABNF">Appendix D</a> shows the collected ABNF with the list rule expanded. |
|---|
| 652 | </p> |
|---|
| 653 | <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="range.units" href="#range.units">Range Units</a></h1> |
|---|
| 654 | <p id="rfc.section.2.p.1">A representation can be partitioned into subranges according to various structural units, depending on the structure inherent |
|---|
| 655 | in the representation's media type. This "<dfn>range unit</dfn>" is used in the <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> (<a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section 2.3</a>) response header field to advertise support for range requests, the <a href="#header.range" class="smpl">Range</a> (<a href="#header.range" id="rfc.xref.header.range.1" title="Range">Section 3.1</a>) request header field to delineate the parts of a representation that are requested, and the <a href="#header.content-range" class="smpl">Content-Range</a> (<a href="#header.content-range" id="rfc.xref.header.content-range.1" title="Content-Range">Section 4.2</a>) payload header field to describe which part of a representation is being transferred. |
|---|
| 656 | </p> |
|---|
| 657 | <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span> <a href="#range.units" class="smpl">range-unit</a> = <a href="#byte.ranges" class="smpl">bytes-unit</a> / <a href="#range.units.other" class="smpl">other-range-unit</a> |
|---|
| 658 | </pre><h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> <a id="byte.ranges" href="#byte.ranges">Byte Ranges</a></h2> |
|---|
| 659 | <p id="rfc.section.2.1.p.1">Since representation data is transferred in payloads as a sequence of octets, a byte range is a meaningful substructure for |
|---|
| 660 | any representation transferable over HTTP (<a href="p2-semantics.html#representations" title="Representations">Section 3</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). We define the "bytes" range unit for expressing subranges of the data's octet sequence. |
|---|
| 661 | </p> |
|---|
| 662 | <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span> <a href="#byte.ranges" class="smpl">bytes-unit</a> = "bytes" |
|---|
| 663 | </pre><div id="rule.ranges-specifier"> |
|---|
| 664 | <p id="rfc.section.2.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. |
|---|
| 665 | </p> |
|---|
| 666 | </div> |
|---|
| 667 | <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span> <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#byte.ranges" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> |
|---|
| 668 | <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> ) |
|---|
| 669 | <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> ] |
|---|
| 670 | <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a> |
|---|
| 671 | <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a> |
|---|
| 672 | </pre><p id="rfc.section.2.1.p.5">The <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> value in a <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> gives the byte-offset of the first byte in a range. The <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value gives the byte-offset of the last byte in the range; that is, the byte positions specified are inclusive. Byte offsets |
|---|
| 673 | start at zero. |
|---|
| 674 | </p> |
|---|
| 675 | <p id="rfc.section.2.1.p.6">Examples of <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> values: |
|---|
| 676 | </p> |
|---|
| 677 | <ul> |
|---|
| 678 | <li>The first 500 bytes (byte offsets 0-499, inclusive): |
|---|
| 679 | <div id="rfc.figure.u.4"></div><pre class="text"> bytes=0-499 |
|---|
| 680 | </pre> </li> |
|---|
| 681 | <li>The second 500 bytes (byte offsets 500-999, inclusive): |
|---|
| 682 | <div id="rfc.figure.u.5"></div><pre class="text"> bytes=500-999 |
|---|
| 683 | </pre> </li> |
|---|
| 684 | </ul> |
|---|
| 685 | <p id="rfc.section.2.1.p.7">A <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> is invalid if the <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value is present and less than the <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>. |
|---|
| 686 | </p> |
|---|
| 687 | <p id="rfc.section.2.1.p.8">A client can limit the number of bytes requested without knowing the size of the selected representation. If the <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value is absent, or if the value is greater than or equal to the current length of the representation data, the byte range |
|---|
| 688 | is interpreted as the remainder of the representation (i.e., the server replaces the value of <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> with a value that is one less than the current length of the selected representation). |
|---|
| 689 | </p> |
|---|
| 690 | <p id="rfc.section.2.1.p.9">A client can request the last N bytes of the selected representation using a <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a>. |
|---|
| 691 | </p> |
|---|
| 692 | <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span> <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> |
|---|
| 693 | <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a> |
|---|
| 694 | </pre><p id="rfc.section.2.1.p.11">If the selected representation is shorter than the specified <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>, the entire representation is used. |
|---|
| 695 | </p> |
|---|
| 696 | <p id="rfc.section.2.1.p.12">Additional examples, assuming a representation of length 10000: </p> |
|---|
| 697 | <ul> |
|---|
| 698 | <li>The final 500 bytes (byte offsets 9500-9999, inclusive): |
|---|
| 699 | <div id="rfc.figure.u.7"></div><pre class="text"> bytes=-500 |
|---|
| 700 | </pre> Or: <div id="rfc.figure.u.8"></div><pre class="text"> bytes=9500- |
|---|
| 701 | </pre> </li> |
|---|
| 702 | <li>The first and last bytes only (bytes 0 and 9999): |
|---|
| 703 | <div id="rfc.figure.u.9"></div><pre class="text"> bytes=0-0,-1 |
|---|
| 704 | </pre> </li> |
|---|
| 705 | <li>Other valid (but not canonical) specifications of the second 500 bytes (byte offsets 500-999, inclusive): |
|---|
| 706 | <div id="rfc.figure.u.10"></div><pre class="text"> bytes=500-600,601-999 |
|---|
| 707 | bytes=500-700,601-999 |
|---|
| 708 | </pre> </li> |
|---|
| 709 | </ul> |
|---|
| 710 | <p id="rfc.section.2.1.p.13">If a valid <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> includes at least one <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> with a <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> that is less than the current length of the representation, or at least one <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> with a non-zero <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>, then the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is satisfiable. Otherwise, the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is unsatisfiable. |
|---|
| 711 | </p> |
|---|
| 712 | <p id="rfc.section.2.1.p.14">In the byte range syntax, <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>, <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>, and <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> are expressed as decimal number of octets. Since there is no predefined limit to the length of a payload, recipients ought |
|---|
| 713 | to anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows. |
|---|
| 714 | </p> |
|---|
| 715 | <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a> <a id="range.units.other" href="#range.units.other">Other Range Units</a></h2> |
|---|
| 716 | <p id="rfc.section.2.2.p.1">Range units are intended to be extensible. New range units ought to be registered with IANA, as defined in <a href="#range.unit.registry" title="Range Unit Registry">Section 5.1</a>. |
|---|
| 717 | </p> |
|---|
| 718 | <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.13"></span> <a href="#range.units.other" class="smpl">other-range-unit</a> = <a href="#imported.abnf" class="smpl">token</a> |
|---|
| 719 | </pre><div id="rfc.iref.a.1"></div> |
|---|
| 720 | <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a> <a id="header.accept-ranges" href="#header.accept-ranges">Accept-Ranges</a></h2> |
|---|
| 721 | <p id="rfc.section.2.3.p.1">The "Accept-Ranges" header field allows a server to indicate that it supports range requests for the target resource.</p> |
|---|
| 722 | <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span> <a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> |
|---|
| 723 | <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none" |
|---|
| 724 | </pre><p id="rfc.section.2.3.p.3">Origin servers that support byte-range requests <em class="bcp14">MAY</em> send |
|---|
| 725 | </p> |
|---|
| 726 | <div id="rfc.figure.u.13"></div><pre class="text"> Accept-Ranges: bytes |
|---|
| 727 | </pre><p id="rfc.section.2.3.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>. |
|---|
| 728 | </p> |
|---|
| 729 | <p id="rfc.section.2.3.p.6">Servers that do not support any kind of range request for the target resource resource <em class="bcp14">MAY</em> send |
|---|
| 730 | </p> |
|---|
| 731 | <div id="rfc.figure.u.14"></div><pre class="text"> Accept-Ranges: none |
|---|
| 732 | </pre><p id="rfc.section.2.3.p.8">to advise the client not to attempt a range request.</p> |
|---|
| 733 | <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="range.requests" href="#range.requests">Range Requests</a></h1> |
|---|
| 734 | <div id="rfc.iref.r.1"></div> |
|---|
| 735 | <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a> <a id="header.range" href="#header.range">Range</a></h2> |
|---|
| 736 | <p id="rfc.section.3.1.p.1">The "Range" header field on a GET request modifies the method semantics to request transfer of only one or more subranges |
|---|
| 737 | of the selected representation data, rather than the entire selected representation data. |
|---|
| 738 | </p> |
|---|
| 739 | <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.16"></span> <a href="#header.range" class="smpl">Range</a> = <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> / <a href="#header.range" class="smpl">other-ranges-specifier</a> |
|---|
| 740 | <a href="#header.range" class="smpl">other-ranges-specifier</a> = <a href="#range.units.other" class="smpl">other-range-unit</a> "=" <a href="#header.range" class="smpl">other-range-set</a> |
|---|
| 741 | <a href="#header.range" class="smpl">other-range-set</a> = 1*<a href="#imported.abnf" class="smpl">CHAR</a> |
|---|
| 742 | </pre><p id="rfc.section.3.1.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, |
|---|
| 743 | since Range supports efficient recovery from partially failed transfers and partial retrieval of large representations. A |
|---|
| 744 | server <em class="bcp14">MUST</em> ignore a Range header field received with a request method other than GET. |
|---|
| 745 | </p> |
|---|
| 746 | <p id="rfc.section.3.1.p.4">An origin server <em class="bcp14">MUST</em> ignore a Range header field that contains a range unit it does not understand. A proxy <em class="bcp14">MAY</em> either discard a Range header field that contains a range unit it does not understand or pass it to the next inbound server |
|---|
| 747 | when forwarding the request. |
|---|
| 748 | </p> |
|---|
| 749 | <p id="rfc.section.3.1.p.5">A server that supports range requests ought to ignore or reject a <a href="#header.range" class="smpl">Range</a> header field that consists of more than two overlapping ranges, or a set of many small ranges that are not listed in ascending |
|---|
| 750 | order, since both are indications of either a broken client or a deliberate denial of service attack (<a href="#overlapping.ranges" title="Denial of Service Attacks using Range">Section 6.1</a>). A client <em class="bcp14">SHOULD NOT</em> request multiple ranges that are inherently less efficient to process and transfer than a single range that encompasses the |
|---|
| 751 | same data. |
|---|
| 752 | </p> |
|---|
| 753 | <p id="rfc.section.3.1.p.6">A client that is requesting multiple ranges <em class="bcp14">SHOULD</em> list those ranges in ascending order (the order in which they would typically be received in a complete representation) unless |
|---|
| 754 | there is a specific need to request a later part earlier. For example, a user agent processing a large representation with |
|---|
| 755 | an internal catalog of parts might need to request later parts first, particularly if the representation consists of pages |
|---|
| 756 | stored in reverse order and the user agent wishes to transfer one page at a time. |
|---|
| 757 | </p> |
|---|
| 758 | <p id="rfc.section.3.1.p.7">The Range header field is evaluated after evaluating the preconditions of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a> and only if the result of their evaluation is leading toward a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response. In other words, Range is ignored when a conditional GET would result in a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response. |
|---|
| 759 | </p> |
|---|
| 760 | <p id="rfc.section.3.1.p.8">The If-Range header field (<a href="#header.if-range" id="rfc.xref.header.if-range.1" title="If-Range">Section 3.2</a>) can be used as a precondition to applying the Range header field. |
|---|
| 761 | </p> |
|---|
| 762 | <p id="rfc.section.3.1.p.9">If all of the preconditions are true, the server supports the Range header field for the target resource, and the specified |
|---|
| 763 | range(s) are valid and satisfiable (as defined in <a href="#byte.ranges" title="Byte Ranges">Section 2.1</a>), the server <em class="bcp14">SHOULD</em> send a <a href="#status.206" class="smpl">206 (Partial Content)</a> response with a payload containing one or more partial representations that correspond to the satisfiable ranges requested, |
|---|
| 764 | as defined in <a href="#range.response" title="Responses to a Range Request">Section 4</a>. |
|---|
| 765 | </p> |
|---|
| 766 | <p id="rfc.section.3.1.p.10">If all of the preconditions are true, the server supports the Range header field for the target resource, and the specified |
|---|
| 767 | range(s) are invalid or unsatisfiable, the server <em class="bcp14">SHOULD</em> send a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response. |
|---|
| 768 | </p> |
|---|
| 769 | <div id="rfc.iref.i.1"></div> |
|---|
| 770 | <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="header.if-range" href="#header.if-range">If-Range</a></h2> |
|---|
| 771 | <p id="rfc.section.3.2.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 |
|---|
| 772 | could use the <a href="#header.range" class="smpl">Range</a> header field with a conditional GET (using either or both of <a href="p4-conditional.html#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> and <a href="p4-conditional.html#header.if-match" class="smpl">If-Match</a>.) However, if the condition fails because the representation has been modified, the client would then have to make a second |
|---|
| 773 | request to obtain the entire current representation. |
|---|
| 774 | </p> |
|---|
| 775 | <p id="rfc.section.3.2.p.2">The "If-Range" header field allows a client to "short-circuit" the second request. Informally, its meaning is: if the representation |
|---|
| 776 | is unchanged, send me the part(s) that I am requesting in Range; otherwise, send me the entire representation. |
|---|
| 777 | </p> |
|---|
| 778 | <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.17"></span> <a href="#header.if-range" class="smpl">If-Range</a> = <a href="#imported.abnf" class="smpl">entity-tag</a> / <a href="#imported.abnf" class="smpl">HTTP-date</a> |
|---|
| 779 | </pre><p id="rfc.section.3.2.p.4">A client <em class="bcp14">MUST NOT</em> generate an If-Range header field containing an entity-tag that is marked as weak. A client <em class="bcp14">MUST NOT</em> generate an If-Range header field containing a <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> date unless the client has no entity-tag for the corresponding representation and the Last-Modified date is strong in the |
|---|
| 780 | 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.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>. |
|---|
| 781 | </p> |
|---|
| 782 | <p id="rfc.section.3.2.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 |
|---|
| 783 | 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.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): 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.) |
|---|
| 784 | </p> |
|---|
| 785 | <p id="rfc.section.3.2.p.6">A client <em class="bcp14">MUST NOT</em> generate an If-Range header field in a request that does not contain a <a href="#header.range" class="smpl">Range</a> header field. A server <em class="bcp14">MUST</em> ignore an If-Range header field received in a request that does not contain a <a href="#header.range" class="smpl">Range</a> header field. An origin server <em class="bcp14">MUST</em> ignore an If-Range header field received in a request for a target resource that does not support Range requests. |
|---|
| 786 | </p> |
|---|
| 787 | <p id="rfc.section.3.2.p.7">If the validator given in the If-Range header field matches the current validator for the selected representation of the target |
|---|
| 788 | resource, then the server <em class="bcp14">SHOULD</em> process the Range header field as requested. If the validator does not match, then the server <em class="bcp14">MUST</em> ignore the <a href="#header.range" class="smpl">Range</a> header field. |
|---|
| 789 | </p> |
|---|
| 790 | <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="range.response" href="#range.response">Responses to a Range Request</a></h1> |
|---|
| 791 | <div id="rfc.iref.20"></div> |
|---|
| 792 | <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a> <a id="status.206" href="#status.206">206 Partial Content</a></h2> |
|---|
| 793 | <p id="rfc.section.4.1.p.1">The <dfn>206 (Partial Content)</dfn> status code indicates that the server is successfully fulfilling a range request for the target resource by transferring one |
|---|
| 794 | or more parts of the selected representation that correspond to the satisfiable ranges found in the request's <a href="#header.range" class="smpl">Range</a> header field (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section 3.1</a>). |
|---|
| 795 | </p> |
|---|
| 796 | <p id="rfc.section.4.1.p.2">If a single part is being transferred, the server generating the 206 response <em class="bcp14">MUST</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field, describing what range of the selected representation is enclosed, and a payload consisting of the range. For |
|---|
| 797 | example: |
|---|
| 798 | </p> |
|---|
| 799 | <div id="rfc.figure.u.17"></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 | |
|---|
| 806 | ... 26012 bytes of partial image data ... |
|---|
| 807 | </pre><p id="rfc.section.4.1.p.4">If multiple parts are being transferred, the server generating the 206 response <em class="bcp14">MUST</em> generate a "multipart/byteranges" payload, as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>, and a <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> header field containing the multipart/byteranges media type and its required boundary parameter. To avoid confusion with single |
|---|
| 808 | part responses, a server <em class="bcp14">MUST NOT</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field in the HTTP header block of a multiple part response (this field will be sent in each part instead). |
|---|
| 809 | </p> |
|---|
| 810 | <p id="rfc.section.4.1.p.5">Within the header area of each body part in the multipart payload, the server <em class="bcp14">MUST</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field corresponding to the range being enclosed in that body part. If the selected representation would have had a <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> header field in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, the server <em class="bcp14">SHOULD</em> generate that same <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> field in the header area of each body part. For example: |
|---|
| 811 | </p> |
|---|
| 812 | <div id="rfc.figure.u.18"></div><pre class="text">HTTP/1.1 206 Partial Content |
|---|
| 813 | Date: Wed, 15 Nov 1995 06:25:24 GMT |
|---|
| 814 | Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT |
|---|
| 815 | Content-Length: 1741 |
|---|
| 816 | Content-Type: multipart/byteranges; boundary=THIS_STRING_SEPARATES |
|---|
| 817 | |
|---|
| 818 | --THIS_STRING_SEPARATES |
|---|
| 819 | Content-Type: application/pdf |
|---|
| 820 | Content-Range: bytes 500-999/8000 |
|---|
| 821 | |
|---|
| 822 | ...the first range... |
|---|
| 823 | --THIS_STRING_SEPARATES |
|---|
| 824 | Content-Type: application/pdf |
|---|
| 825 | Content-Range: bytes 7000-7999/8000 |
|---|
| 826 | |
|---|
| 827 | ...the second range |
|---|
| 828 | --THIS_STRING_SEPARATES-- |
|---|
| 829 | </pre><p id="rfc.section.4.1.p.7">When multiple ranges are requested, a server <em class="bcp14">MAY</em> coalesce any of the ranges that overlap or that are separated by a gap that is smaller than the overhead of sending multiple |
|---|
| 830 | parts, regardless of the order in which the corresponding byte-range-spec appeared in the received <a href="#header.range" class="smpl">Range</a> header field. Since the typical overhead between parts of a multipart/byteranges payload is around 80 bytes, depending on |
|---|
| 831 | the selected representation's media type and the chosen boundary parameter length, it can be less efficient to transfer many |
|---|
| 832 | small disjoint parts than it is to transfer the entire selected representation. |
|---|
| 833 | </p> |
|---|
| 834 | <p id="rfc.section.4.1.p.8">A server <em class="bcp14">MUST NOT</em> generate a multipart response to a request for a single range, since a client that does not request multiple parts might not |
|---|
| 835 | support multipart responses. However, a server <em class="bcp14">MAY</em> generate a multipart/byteranges payload with only a single body part if multiple ranges were requested and only one range |
|---|
| 836 | was found to be satisfiable or only one range remained after coalescing. A client that cannot process a multipart/byteranges |
|---|
| 837 | response <em class="bcp14">MUST NOT</em> generate a request that asks for multiple ranges. |
|---|
| 838 | </p> |
|---|
| 839 | <p id="rfc.section.4.1.p.9">When a multipart response payload is generated, the server <em class="bcp14">SHOULD</em> send the parts in the same order that the corresponding byte-range-spec appeared in the received <a href="#header.range" class="smpl">Range</a> header field, excluding those ranges that were deemed unsatisfiable or that were coalesced into other ranges. A client that |
|---|
| 840 | receives a multipart response <em class="bcp14">MUST</em> inspect the <a href="#header.content-range" class="smpl">Content-Range</a> header field present in each body part in order to determine which range is contained in that body part; a client cannot rely |
|---|
| 841 | on receiving the same ranges that it requested, nor the same order that it requested. |
|---|
| 842 | </p> |
|---|
| 843 | <p id="rfc.section.4.1.p.10">When a 206 response is generated, the server <em class="bcp14">MUST</em> generate the following header fields, in addition to those required above, if the field would have been sent in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response to the same request: <a href="p2-semantics.html#header.date" class="smpl">Date</a>, <a href="p6-cache.html#header.cache-control" class="smpl">Cache-Control</a>, <a href="p4-conditional.html#header.etag" class="smpl">ETag</a>, <a href="p6-cache.html#header.expires" class="smpl">Expires</a>, <a href="p2-semantics.html#header.content-location" class="smpl">Content-Location</a>, and <a href="p2-semantics.html#header.vary" class="smpl">Vary</a>. |
|---|
| 844 | </p> |
|---|
| 845 | <p id="rfc.section.4.1.p.11">If a 206 is generated in response to a request with an <a href="#header.if-range" class="smpl">If-Range</a> header field, the sender <em class="bcp14">SHOULD NOT</em> generate other representation header fields beyond those required above, because the client is understood to already have |
|---|
| 846 | a prior response containing those header fields. Otherwise, the sender <em class="bcp14">MUST</em> generate all of the representation header fields that would have been sent in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response to the same request. |
|---|
| 847 | </p> |
|---|
| 848 | <p id="rfc.section.4.1.p.12">A 206 response is cacheable unless otherwise indicated by explicit cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). |
|---|
| 849 | </p> |
|---|
| 850 | <div id="rfc.iref.c.1"></div> |
|---|
| 851 | <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a> <a id="header.content-range" href="#header.content-range">Content-Range</a></h2> |
|---|
| 852 | <p id="rfc.section.4.2.p.1">The "Content-Range" header field is sent in a single part <a href="#status.206" class="smpl">206 (Partial Content)</a> response to indicate the partial range of the selected representation enclosed as the message payload, sent in each part of |
|---|
| 853 | a multipart 206 response to indicate the range enclosed within each body part, and sent in <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> responses to provide information about the selected representation. |
|---|
| 854 | </p> |
|---|
| 855 | <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span> <a href="#header.content-range" class="smpl">Content-Range</a> = <a href="#header.content-range" class="smpl">byte-content-range</a> |
|---|
| 856 | / <a href="#header.content-range" class="smpl">other-content-range</a> |
|---|
| 857 | |
|---|
| 858 | <a href="#header.content-range" class="smpl">byte-content-range</a> = <a href="#byte.ranges" class="smpl">bytes-unit</a> <a href="#imported.abnf" class="smpl">SP</a> |
|---|
| 859 | ( <a href="#header.content-range" class="smpl">byte-range-resp</a> / <a href="#header.content-range" class="smpl">unsatisfied-range</a> ) |
|---|
| 860 | |
|---|
| 861 | <a href="#header.content-range" class="smpl">byte-range-resp</a> = <a href="#header.content-range" class="smpl">byte-range</a> "/" ( <a href="#header.content-range" class="smpl">complete-length</a> / "*" ) |
|---|
| 862 | <a href="#header.content-range" class="smpl">byte-range</a> = <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> "-" <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> |
|---|
| 863 | <a href="#header.content-range" class="smpl">unsatisfied-range</a> = "*/" <a href="#header.content-range" class="smpl">complete-length</a> |
|---|
| 864 | |
|---|
| 865 | <a href="#header.content-range" class="smpl">complete-length</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a> |
|---|
| 866 | |
|---|
| 867 | <a href="#header.content-range" class="smpl">other-content-range</a> = <a href="#range.units.other" class="smpl">other-range-unit</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#header.content-range" class="smpl">other-range-resp</a> |
|---|
| 868 | <a href="#header.content-range" class="smpl">other-range-resp</a> = *<a href="#imported.abnf" class="smpl">CHAR</a> |
|---|
| 869 | </pre><p id="rfc.section.4.2.p.3">If a <a href="#status.206" class="smpl">206 (Partial Content)</a> response contains a <a href="#header.content-range" class="smpl">Content-Range</a> header field with a <a href="#range.units" class="smpl">range unit</a> (<a href="#range.units" title="Range Units">Section 2</a>) that the recipient does not understand, the recipient <em class="bcp14">MUST NOT</em> attempt to recombine it with a stored representation. A proxy that receives such a message <em class="bcp14">SHOULD</em> forward it downstream. |
|---|
| 870 | </p> |
|---|
| 871 | <p id="rfc.section.4.2.p.4">For byte ranges, a sender <em class="bcp14">SHOULD</em> indicate the complete length of the representation from which the range has been extracted, unless the complete length is |
|---|
| 872 | unknown or difficult to determine. An asterisk character ("*") in place of the complete-length indicates that the representation |
|---|
| 873 | length was unknown when the header field was generated. |
|---|
| 874 | </p> |
|---|
| 875 | <p id="rfc.section.4.2.p.5">The following example illustrates when the complete length of the selected representation is known by the sender to be 1234 |
|---|
| 876 | bytes: |
|---|
| 877 | </p> |
|---|
| 878 | <div id="rfc.figure.u.20"></div><pre class="text"> Content-Range: bytes 42-1233/1234 |
|---|
| 879 | </pre><p id="rfc.section.4.2.p.7">and this second example illustrates when the complete length is unknown:</p> |
|---|
| 880 | <div id="rfc.figure.u.21"></div><pre class="text"> Content-Range: bytes 42-1233/* |
|---|
| 881 | </pre><p id="rfc.section.4.2.p.9">A Content-Range field value is invalid if it contains a <a href="#header.content-range" class="smpl">byte-range-resp</a> that has a <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value less than its <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> value, or a <a href="#header.content-range" class="smpl">complete-length</a> value less than or equal to its <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value. The recipient of an invalid <a href="#header.content-range" class="smpl">Content-Range</a> <em class="bcp14">MUST NOT</em> attempt to recombine the received content with a stored representation. |
|---|
| 882 | </p> |
|---|
| 883 | <p id="rfc.section.4.2.p.10">A server generating a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response to a byte range request <em class="bcp14">SHOULD</em> send a Content-Range header field with an <a href="#header.content-range" class="smpl">unsatisfied-range</a> value, as in the following example: |
|---|
| 884 | </p> |
|---|
| 885 | <div id="rfc.figure.u.22"></div><pre class="text"> Content-Range: bytes */1234 |
|---|
| 886 | </pre><p id="rfc.section.4.2.p.12">The complete-length in a 416 response indicates the current length of the selected representation.</p> |
|---|
| 887 | <p id="rfc.section.4.2.p.13">The "Content-Range" header field has no meaning for status codes that do not explicitly describe its semantic. For this specification, |
|---|
| 888 | only the <a href="#status.206" class="smpl">206 (Partial Content)</a> and <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> status codes describe a meaning for Content-Range. |
|---|
| 889 | </p> |
|---|
| 890 | <p id="rfc.section.4.2.p.14">The following are examples of Content-Range values in which the selected representation contains a total of 1234 bytes: </p> |
|---|
| 891 | <ul> |
|---|
| 892 | <li>The first 500 bytes: |
|---|
| 893 | <div id="rfc.figure.u.23"></div><pre class="text"> Content-Range: bytes 0-499/1234 |
|---|
| 894 | </pre> </li> |
|---|
| 895 | <li>The second 500 bytes: |
|---|
| 896 | <div id="rfc.figure.u.24"></div><pre class="text"> Content-Range: bytes 500-999/1234 |
|---|
| 897 | </pre> </li> |
|---|
| 898 | <li>All except for the first 500 bytes: |
|---|
| 899 | <div id="rfc.figure.u.25"></div><pre class="text"> Content-Range: bytes 500-1233/1234 |
|---|
| 900 | </pre> </li> |
|---|
| 901 | <li>The last 500 bytes: |
|---|
| 902 | <div id="rfc.figure.u.26"></div><pre class="text"> Content-Range: bytes 734-1233/1234 |
|---|
| 903 | </pre> </li> |
|---|
| 904 | </ul> |
|---|
| 905 | <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a> <a id="combining.byte.ranges" href="#combining.byte.ranges">Combining Ranges</a></h2> |
|---|
| 906 | <p id="rfc.section.4.3.p.1">A response might transfer only a subrange of a representation if the connection closed prematurely or if the request used |
|---|
| 907 | one or more Range specifications. After several such transfers, a client might have received several ranges of the same representation. |
|---|
| 908 | These ranges can only be safely combined if they all have in common the same strong validator, where "strong validator" is |
|---|
| 909 | 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.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>) or, if no entity-tag is provided, a <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> 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.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>. |
|---|
| 910 | </p> |
|---|
| 911 | <p id="rfc.section.4.3.p.2">A client that has received multiple partial responses to GET requests on a target resource <em class="bcp14">MAY</em> combine those responses into a larger continuous range if they share the same strong validator. |
|---|
| 912 | </p> |
|---|
| 913 | <p id="rfc.section.4.3.p.3">If the most recent response is an incomplete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, then the header fields of that response are used for any combined response and replace those of the matching stored |
|---|
| 914 | responses. |
|---|
| 915 | </p> |
|---|
| 916 | <p id="rfc.section.4.3.p.4">If the most recent response is a <a href="#status.206" class="smpl">206 (Partial Content)</a> response and at least one of the matching stored responses is a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a>, then the combined response header fields consist of the most recent 200 response's header fields. If all of the matching |
|---|
| 917 | stored responses are 206 responses, then the stored response with the most recent header fields is used as the source of header |
|---|
| 918 | fields for the combined response, except that the client <em class="bcp14">MUST</em> use other header fields provided in the new response, aside from <a href="#header.content-range" class="smpl">Content-Range</a>, to replace all instances of the corresponding header fields in the stored response. |
|---|
| 919 | </p> |
|---|
| 920 | <p id="rfc.section.4.3.p.5">The combined response message body consists of the union of partial content ranges in the new response and each of the selected |
|---|
| 921 | responses. If the union consists of the entire range of the representation, then the client <em class="bcp14">MUST</em> record the combined response as if it were a complete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, including a <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> header field that reflects the complete length. Otherwise, the client <em class="bcp14">MUST</em> record the set of continuous ranges as one of the following: an incomplete <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response if the combined response is a prefix of the representation, a single <a href="#status.206" class="smpl">206 (Partial Content)</a> response containing a multipart/byteranges body, or multiple <a href="#status.206" class="smpl">206 (Partial Content)</a> responses, each with one continuous range that is indicated by a <a href="#header.content-range" class="smpl">Content-Range</a> header field. |
|---|
| 922 | </p> |
|---|
| 923 | <div id="rfc.iref.29"></div> |
|---|
| 924 | <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a> <a id="status.416" href="#status.416">416 Range Not Satisfiable</a></h2> |
|---|
| 925 | <p id="rfc.section.4.4.p.1">The <dfn>416 (Range Not Satisfiable)</dfn> status code indicates that none of the ranges in the request's <a href="#header.range" class="smpl">Range</a> header field (<a href="#header.range" id="rfc.xref.header.range.3" title="Range">Section 3.1</a>) overlap the current extent of the selected resource or that the set of ranges requested has been rejected due to invalid |
|---|
| 926 | ranges or an excessive request of small or overlapping ranges. |
|---|
| 927 | </p> |
|---|
| 928 | <p id="rfc.section.4.4.p.2">For byte ranges, failing to overlap the current extent means that the <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> of all of the <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> values were greater than the current length of the selected representation. When this status code is generated in response |
|---|
| 929 | to a byte range request, the sender <em class="bcp14">SHOULD</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field specifying the current length of the selected representation (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section 4.2</a>). |
|---|
| 930 | </p> |
|---|
| 931 | <div id="rfc.figure.u.27"></div> |
|---|
| 932 | <p>For example:</p><pre class="text">HTTP/1.1 416 Range Not Satisfiable |
|---|
| 933 | Date: Fri, 20 Jan 2012 15:41:54 GMT |
|---|
| 934 | Content-Range: bytes */47022 |
|---|
| 935 | </pre><div class="note" id="rfc.section.4.4.p.4"> |
|---|
| 936 | <p> <b>Note:</b> Because servers are free to ignore <a href="#header.range" class="smpl">Range</a>, many implementations will simply respond with the entire selected representation in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response if the requested ranges are invalid or not satisfiable. That is partly because most clients are prepared to receive |
|---|
| 937 | a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> to complete the task (albeit less efficiently) and partly because clients might not stop making an invalid partial request |
|---|
| 938 | until they have received a complete representation. Thus, clients cannot depend on receiving a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response even when it is most appropriate. |
|---|
| 939 | </p> |
|---|
| 940 | </div> |
|---|
| 941 | <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> |
|---|
| 942 | <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a> <a id="range.unit.registry" href="#range.unit.registry">Range Unit Registry</a></h2> |
|---|
| 943 | <p id="rfc.section.5.1.p.1">The HTTP Range Unit Registry defines the name space for the range unit names and refers to their corresponding specifications. |
|---|
| 944 | The registry will be created and maintained at <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>>. |
|---|
| 945 | </p> |
|---|
| 946 | <h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a> <a id="range.unit.registry.procedure" href="#range.unit.registry.procedure">Procedure</a></h3> |
|---|
| 947 | <p id="rfc.section.5.1.1.p.1">Registration of an HTTP Range Unit <em class="bcp14">MUST</em> include the following fields: |
|---|
| 948 | </p> |
|---|
| 949 | <ul> |
|---|
| 950 | <li>Name</li> |
|---|
| 951 | <li>Description</li> |
|---|
| 952 | <li>Pointer to specification text</li> |
|---|
| 953 | </ul> |
|---|
| 954 | <p id="rfc.section.5.1.1.p.2">Values to be added to this name space require IETF Review (see <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>). |
|---|
| 955 | </p> |
|---|
| 956 | <h3 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a> <a id="range.unit.registration" href="#range.unit.registration">Registrations</a></h3> |
|---|
| 957 | <p id="rfc.section.5.1.2.p.1">The initial HTTP Range Unit Registry shall contain the registrations below:</p> |
|---|
| 958 | <div id="rfc.table.1"> |
|---|
| 959 | <div id="iana.range.units.table"></div> |
|---|
| 960 | <table class="tt full left" cellpadding="3" cellspacing="0"> |
|---|
| 961 | <thead> |
|---|
| 962 | <tr> |
|---|
| 963 | <th>Range Unit Name</th> |
|---|
| 964 | <th>Description</th> |
|---|
| 965 | <th>Reference</th> |
|---|
| 966 | </tr> |
|---|
| 967 | </thead> |
|---|
| 968 | <tbody> |
|---|
| 969 | <tr> |
|---|
| 970 | <td class="left">bytes</td> |
|---|
| 971 | <td class="left">a range of octets</td> |
|---|
| 972 | <td class="left"><a href="#byte.ranges" title="Byte Ranges">Section 2.1</a></td> |
|---|
| 973 | </tr> |
|---|
| 974 | <tr> |
|---|
| 975 | <td class="left">none</td> |
|---|
| 976 | <td class="left">reserved as keyword, indicating no ranges are supported</td> |
|---|
| 977 | <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.2" title="Accept-Ranges">Section 2.3</a></td> |
|---|
| 978 | </tr> |
|---|
| 979 | </tbody> |
|---|
| 980 | </table> |
|---|
| 981 | </div> |
|---|
| 982 | <p id="rfc.section.5.1.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> |
|---|
| 983 | <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a> <a id="status.code.registration" href="#status.code.registration">Status Code Registration</a></h2> |
|---|
| 984 | <p id="rfc.section.5.2.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: |
|---|
| 985 | </p> |
|---|
| 986 | <div id="rfc.table.2"> |
|---|
| 987 | <div id="iana.status.code.registration.table"></div> |
|---|
| 988 | <table class="tt full left" cellpadding="3" cellspacing="0"> |
|---|
| 989 | <thead> |
|---|
| 990 | <tr> |
|---|
| 991 | <th>Value</th> |
|---|
| 992 | <th>Description</th> |
|---|
| 993 | <th>Reference</th> |
|---|
| 994 | </tr> |
|---|
| 995 | </thead> |
|---|
| 996 | <tbody> |
|---|
| 997 | <tr> |
|---|
| 998 | <td class="left">206</td> |
|---|
| 999 | <td class="left">Partial Content</td> |
|---|
| 1000 | <td class="left"> <a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section 4.1</a> |
|---|
| 1001 | </td> |
|---|
| 1002 | </tr> |
|---|
| 1003 | <tr> |
|---|
| 1004 | <td class="left">416</td> |
|---|
| 1005 | <td class="left">Range Not Satisfiable</td> |
|---|
| 1006 | <td class="left"> <a href="#status.416" id="rfc.xref.status.416.1" title="416 Range Not Satisfiable">Section 4.4</a> |
|---|
| 1007 | </td> |
|---|
| 1008 | </tr> |
|---|
| 1009 | </tbody> |
|---|
| 1010 | </table> |
|---|
| 1011 | </div> |
|---|
| 1012 | <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a> <a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2> |
|---|
| 1013 | <p id="rfc.section.5.3.p.1">HTTP header fields are registered within the Message Header Field Registry maintained 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>>. |
|---|
| 1014 | </p> |
|---|
| 1015 | <p id="rfc.section.5.3.p.2">This document defines the following HTTP header fields, so their associated registry entries shall be updated according to |
|---|
| 1016 | the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>): |
|---|
| 1017 | </p> |
|---|
| 1018 | <div id="rfc.table.3"> |
|---|
| 1019 | <div id="iana.header.registration.table"></div> |
|---|
| 1020 | <table class="tt full left" cellpadding="3" cellspacing="0"> |
|---|
| 1021 | <thead> |
|---|
| 1022 | <tr> |
|---|
| 1023 | <th>Header Field Name</th> |
|---|
| 1024 | <th>Protocol</th> |
|---|
| 1025 | <th>Status</th> |
|---|
| 1026 | <th>Reference</th> |
|---|
| 1027 | </tr> |
|---|
| 1028 | </thead> |
|---|
| 1029 | <tbody> |
|---|
| 1030 | <tr> |
|---|
| 1031 | <td class="left">Accept-Ranges</td> |
|---|
| 1032 | <td class="left">http</td> |
|---|
| 1033 | <td class="left">standard</td> |
|---|
| 1034 | <td class="left"> <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.3" title="Accept-Ranges">Section 2.3</a> |
|---|
| 1035 | </td> |
|---|
| 1036 | </tr> |
|---|
| 1037 | <tr> |
|---|
| 1038 | <td class="left">Content-Range</td> |
|---|
| 1039 | <td class="left">http</td> |
|---|
| 1040 | <td class="left">standard</td> |
|---|
| 1041 | <td class="left"> <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section 4.2</a> |
|---|
| 1042 | </td> |
|---|
| 1043 | </tr> |
|---|
| 1044 | <tr> |
|---|
| 1045 | <td class="left">If-Range</td> |
|---|
| 1046 | <td class="left">http</td> |
|---|
| 1047 | <td class="left">standard</td> |
|---|
| 1048 | <td class="left"> <a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section 3.2</a> |
|---|
| 1049 | </td> |
|---|
| 1050 | </tr> |
|---|
| 1051 | <tr> |
|---|
| 1052 | <td class="left">Range</td> |
|---|
| 1053 | <td class="left">http</td> |
|---|
| 1054 | <td class="left">standard</td> |
|---|
| 1055 | <td class="left"> <a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section 3.1</a> |
|---|
| 1056 | </td> |
|---|
| 1057 | </tr> |
|---|
| 1058 | </tbody> |
|---|
| 1059 | </table> |
|---|
| 1060 | </div> |
|---|
| 1061 | <p id="rfc.section.5.3.p.3">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> |
|---|
| 1062 | <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> |
|---|
| 1063 | <p id="rfc.section.6.p.1">This section is meant to inform developers, information providers, and users of known security concerns specific to the HTTP/1.1 |
|---|
| 1064 | range request mechanisms. More general security considerations are addressed in HTTP messaging <a href="#Part1" id="rfc.xref.Part1.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> and semantics <a href="#Part2" id="rfc.xref.Part2.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>. |
|---|
| 1065 | </p> |
|---|
| 1066 | <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a> <a id="overlapping.ranges" href="#overlapping.ranges">Denial of Service Attacks using Range</a></h2> |
|---|
| 1067 | <p id="rfc.section.6.1.p.1">Unconstrained multiple range requests are susceptible to denial of service attacks because the effort required to request |
|---|
| 1068 | many overlapping ranges of the same data is tiny compared to the time, memory, and bandwidth consumed by attempting to serve |
|---|
| 1069 | the requested data in many parts. Servers ought to ignore, coalesce, or reject egregious range requests, such as requests |
|---|
| 1070 | for more than two overlapping ranges or for many small ranges in a single set, particularly when the ranges are requested |
|---|
| 1071 | out of order for no apparent reason. Multipart range requests are not designed to support random access. |
|---|
| 1072 | </p> |
|---|
| 1073 | <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="acks" href="#acks">Acknowledgments</a></h1> |
|---|
| 1074 | <p id="rfc.section.7.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. |
|---|
| 1075 | </p> |
|---|
| 1076 | <h1 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References |
|---|
| 1077 | </h1> |
|---|
| 1078 | <h2 id="rfc.references.1"><a href="#rfc.section.8.1" id="rfc.section.8.1">8.1</a> Normative References |
|---|
| 1079 | </h2> |
|---|
| 1080 | <table> |
|---|
| 1081 | <tr> |
|---|
| 1082 | <td class="reference"><b id="Part1">[Part1]</b></td> |
|---|
| 1083 | <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., 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-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), June 2013. |
|---|
| 1084 | </td> |
|---|
| 1085 | </tr> |
|---|
| 1086 | <tr> |
|---|
| 1087 | <td class="reference"><b id="Part2">[Part2]</b></td> |
|---|
| 1088 | <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., 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-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), June 2013. |
|---|
| 1089 | </td> |
|---|
| 1090 | </tr> |
|---|
| 1091 | <tr> |
|---|
| 1092 | <td class="reference"><b id="Part4">[Part4]</b></td> |
|---|
| 1093 | <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., 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-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), June 2013. |
|---|
| 1094 | </td> |
|---|
| 1095 | </tr> |
|---|
| 1096 | <tr> |
|---|
| 1097 | <td class="reference"><b id="Part6">[Part6]</b></td> |
|---|
| 1098 | <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., 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-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), June 2013. |
|---|
| 1099 | </td> |
|---|
| 1100 | </tr> |
|---|
| 1101 | <tr> |
|---|
| 1102 | <td class="reference"><b id="RFC2046">[RFC2046]</b></td> |
|---|
| 1103 | <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. |
|---|
| 1104 | </td> |
|---|
| 1105 | </tr> |
|---|
| 1106 | <tr> |
|---|
| 1107 | <td class="reference"><b id="RFC2119">[RFC2119]</b></td> |
|---|
| 1108 | <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. |
|---|
| 1109 | </td> |
|---|
| 1110 | </tr> |
|---|
| 1111 | <tr> |
|---|
| 1112 | <td class="reference"><b id="RFC5234">[RFC5234]</b></td> |
|---|
| 1113 | <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. |
|---|
| 1114 | </td> |
|---|
| 1115 | </tr> |
|---|
| 1116 | </table> |
|---|
| 1117 | <h2 id="rfc.references.2"><a href="#rfc.section.8.2" id="rfc.section.8.2">8.2</a> Informative References |
|---|
| 1118 | </h2> |
|---|
| 1119 | <table> |
|---|
| 1120 | <tr> |
|---|
| 1121 | <td class="reference"><b id="BCP13">[BCP13]</b></td> |
|---|
| 1122 | <td class="top"><a href="mailto:ned+ietf@mrochek.com" title="Oracle">Freed, N.</a>, <a href="mailto:john+ietf@jck.com">Klensin, J.</a>, and <a href="mailto:tony+mtsuffix@maillennium.att.com" title="AT&T Laboratories">T. Hansen</a>, “<a href="http://tools.ietf.org/html/rfc6838">Media Type Specifications and Registration Procedures</a>”, BCP 13, RFC 6838, January 2013. |
|---|
| 1123 | </td> |
|---|
| 1124 | </tr> |
|---|
| 1125 | <tr> |
|---|
| 1126 | <td class="reference"><b id="BCP90">[BCP90]</b></td> |
|---|
| 1127 | <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. |
|---|
| 1128 | </td> |
|---|
| 1129 | </tr> |
|---|
| 1130 | <tr> |
|---|
| 1131 | <td class="reference"><b id="RFC2616">[RFC2616]</b></td> |
|---|
| 1132 | <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. |
|---|
| 1133 | </td> |
|---|
| 1134 | </tr> |
|---|
| 1135 | <tr> |
|---|
| 1136 | <td class="reference"><b id="RFC5226">[RFC5226]</b></td> |
|---|
| 1137 | <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. |
|---|
| 1138 | </td> |
|---|
| 1139 | </tr> |
|---|
| 1140 | </table> |
|---|
| 1141 | <div class="avoidbreak"> |
|---|
| 1142 | <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1> |
|---|
| 1143 | <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span> |
|---|
| 1144 | (editor) |
|---|
| 1145 | <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> |
|---|
| 1146 | <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span> |
|---|
| 1147 | (editor) |
|---|
| 1148 | <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> |
|---|
| 1149 | <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span> |
|---|
| 1150 | (editor) |
|---|
| 1151 | <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">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> |
|---|
| 1152 | </div> |
|---|
| 1153 | <div id="rfc.iref.m.1"></div> |
|---|
| 1154 | <div id="rfc.iref.m.2"></div> |
|---|
| 1155 | <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> |
|---|
| 1156 | <p id="rfc.section.A.p.1">When a <a href="#status.206" class="smpl">206 (Partial Content)</a> response message includes the content of multiple ranges, they are transmitted as body parts in 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>) with the media type of "multipart/byteranges". The following definition is to be registered with IANA <a href="#BCP13" id="rfc.xref.BCP13.1"><cite title="Media Type Specifications and Registration Procedures">[BCP13]</cite></a>. |
|---|
| 1157 | </p> |
|---|
| 1158 | <p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more body parts, each with its own <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> and <a href="#header.content-range" class="smpl">Content-Range</a> fields. The required boundary parameter specifies the boundary string used to separate each body part. |
|---|
| 1159 | </p> |
|---|
| 1160 | <p id="rfc.section.A.p.3"> </p> |
|---|
| 1161 | <dl> |
|---|
| 1162 | <dt>Type name:</dt> |
|---|
| 1163 | <dd>multipart</dd> |
|---|
| 1164 | <dt>Subtype name:</dt> |
|---|
| 1165 | <dd>byteranges</dd> |
|---|
| 1166 | <dt>Required parameters:</dt> |
|---|
| 1167 | <dd>boundary</dd> |
|---|
| 1168 | <dt>Optional parameters:</dt> |
|---|
| 1169 | <dd>none</dd> |
|---|
| 1170 | <dt>Encoding considerations:</dt> |
|---|
| 1171 | <dd>only "7bit", "8bit", or "binary" are permitted</dd> |
|---|
| 1172 | <dt>Security considerations:</dt> |
|---|
| 1173 | <dd>none</dd> |
|---|
| 1174 | <dt>Interoperability considerations:</dt> |
|---|
| 1175 | <dd>none</dd> |
|---|
| 1176 | <dt>Published specification:</dt> |
|---|
| 1177 | <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>). |
|---|
| 1178 | </dd> |
|---|
| 1179 | <dt>Applications that use this media type:</dt> |
|---|
| 1180 | <dd>HTTP components supporting multiple ranges in a single request.</dd> |
|---|
| 1181 | <dt>Additional information:</dt> |
|---|
| 1182 | <dd> |
|---|
| 1183 | <dl> |
|---|
| 1184 | <dt>Magic number(s):</dt> |
|---|
| 1185 | <dd>none</dd> |
|---|
| 1186 | <dt>File extension(s):</dt> |
|---|
| 1187 | <dd>none</dd> |
|---|
| 1188 | <dt>Macintosh file type code(s):</dt> |
|---|
| 1189 | <dd>none</dd> |
|---|
| 1190 | </dl> |
|---|
| 1191 | </dd> |
|---|
| 1192 | <dt>Person and email address to contact for further information:</dt> |
|---|
| 1193 | <dd>See Authors Section.</dd> |
|---|
| 1194 | <dt>Intended usage:</dt> |
|---|
| 1195 | <dd>COMMON</dd> |
|---|
| 1196 | <dt>Restrictions on usage:</dt> |
|---|
| 1197 | <dd>none</dd> |
|---|
| 1198 | <dt>Author:</dt> |
|---|
| 1199 | <dd>See Authors Section.</dd> |
|---|
| 1200 | <dt>Change controller:</dt> |
|---|
| 1201 | <dd>IESG</dd> |
|---|
| 1202 | </dl> |
|---|
| 1203 | <p id="rfc.section.A.p.4">Implementation Notes: </p> |
|---|
| 1204 | <ol> |
|---|
| 1205 | <li>Additional CRLFs might precede the first boundary string in the body.</li> |
|---|
| 1206 | <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. |
|---|
| 1207 | </li> |
|---|
| 1208 | <li>A number of clients and servers were coded to an early draft of the byteranges specification that used 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 this type. |
|---|
| 1209 | </li> |
|---|
| 1210 | </ol> |
|---|
| 1211 | <p id="rfc.section.A.p.5">Despite the name, the "multipart/byteranges" media type is not limited to byte ranges. The following example uses an "exampleunit" |
|---|
| 1212 | range unit: |
|---|
| 1213 | </p> |
|---|
| 1214 | <div id="rfc.figure.u.28"></div><pre class="text">HTTP/1.1 206 Partial Content |
|---|
| 1215 | Date: Tue, 14 Nov 1995 06:25:24 GMT |
|---|
| 1216 | Last-Modified: Tue, 14 July 04:58:08 GMT |
|---|
| 1217 | Content-Length: 2331785 |
|---|
| 1218 | Content-Type: multipart/byteranges; boundary=THIS_STRING_SEPARATES |
|---|
| 1219 | |
|---|
| 1220 | --THIS_STRING_SEPARATES |
|---|
| 1221 | Content-Type: video/example |
|---|
| 1222 | Content-Range: exampleunit 1.2-4.3/25 |
|---|
| 1223 | |
|---|
| 1224 | ...the first range... |
|---|
| 1225 | --THIS_STRING_SEPARATES |
|---|
| 1226 | Content-Type: video/example |
|---|
| 1227 | Content-Range: exampleunit 11.2-14.3/25 |
|---|
| 1228 | |
|---|
| 1229 | ...the second range |
|---|
| 1230 | --THIS_STRING_SEPARATES-- |
|---|
| 1231 | </pre><h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1> |
|---|
| 1232 | <p id="rfc.section.B.p.1">A weak validator cannot be used in a <a href="#status.206" class="smpl">206</a> response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section 4.1</a>) |
|---|
| 1233 | </p> |
|---|
| 1234 | <p id="rfc.section.B.p.2">The Content-Range header field only has meaning when the status code explicitly defines its use. (<a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section 4.2</a>) |
|---|
| 1235 | </p> |
|---|
| 1236 | <p id="rfc.section.B.p.3">Servers are given more leeway in how they respond to a range request, in order to mitigate abuse by malicious (or just greedy) |
|---|
| 1237 | clients. |
|---|
| 1238 | </p> |
|---|
| 1239 | <p id="rfc.section.B.p.4">multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>) |
|---|
| 1240 | </p> |
|---|
| 1241 | <p id="rfc.section.B.p.5">This specification introduces a Range Unit Registry. (<a href="#range.unit.registry" title="Range Unit Registry">Section 5.1</a>) |
|---|
| 1242 | </p> |
|---|
| 1243 | <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1> |
|---|
| 1244 | <p id="rfc.section.C.p.1">The following core rules are included by reference, as defined in <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a> of <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG |
|---|
| 1245 | (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII |
|---|
| 1246 | character). |
|---|
| 1247 | </p> |
|---|
| 1248 | <p id="rfc.section.C.p.2">Note that all rules derived from <a href="#imported.abnf" class="smpl">token</a> are to be compared case-insensitively, like <a href="#range.units" class="smpl">range-unit</a> and <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a>. |
|---|
| 1249 | </p> |
|---|
| 1250 | <p id="rfc.section.C.p.3">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>: |
|---|
| 1251 | </p> |
|---|
| 1252 | <div id="rfc.figure.u.29"></div><pre class="inline"> <a href="#imported.abnf" class="smpl">OWS</a> = <OWS, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>> |
|---|
| 1253 | <a href="#imported.abnf" class="smpl">token</a> = <token, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.6</a>> |
|---|
| 1254 | </pre><p id="rfc.section.C.p.5">The rules below are defined in other parts:</p> |
|---|
| 1255 | <div id="rfc.figure.u.30"></div><pre class="inline"> <a href="#imported.abnf" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>> |
|---|
| 1256 | <a href="#imported.abnf" class="smpl">entity-tag</a> = <entity-tag, defined in <a href="#Part4" id="rfc.xref.Part4.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a>> |
|---|
| 1257 | </pre><h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> |
|---|
| 1258 | <p id="rfc.section.D.p.1">In the collected ABNF below, list rules are expanded as per <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>. |
|---|
| 1259 | </p> |
|---|
| 1260 | <div id="rfc.figure.u.31"></div><pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = acceptable-ranges |
|---|
| 1261 | |
|---|
| 1262 | <a href="#header.content-range" class="smpl">Content-Range</a> = byte-content-range / other-content-range |
|---|
| 1263 | |
|---|
| 1264 | <a href="#imported.abnf" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part2], Section 7.1.1.1> |
|---|
| 1265 | |
|---|
| 1266 | <a href="#header.if-range" class="smpl">If-Range</a> = entity-tag / HTTP-date |
|---|
| 1267 | |
|---|
| 1268 | <a href="#imported.abnf" class="smpl">OWS</a> = <OWS, defined in [Part1], Section 3.2.3> |
|---|
| 1269 | |
|---|
| 1270 | <a href="#header.range" class="smpl">Range</a> = byte-ranges-specifier / other-ranges-specifier |
|---|
| 1271 | |
|---|
| 1272 | <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = ( *( "," OWS ) range-unit *( OWS "," [ OWS |
|---|
| 1273 | range-unit ] ) ) / "none" |
|---|
| 1274 | |
|---|
| 1275 | <a href="#header.content-range" class="smpl">byte-content-range</a> = bytes-unit SP ( byte-range-resp / |
|---|
| 1276 | unsatisfied-range ) |
|---|
| 1277 | <a href="#header.content-range" class="smpl">byte-range</a> = first-byte-pos "-" last-byte-pos |
|---|
| 1278 | <a href="#header.content-range" class="smpl">byte-range-resp</a> = byte-range "/" ( complete-length / "*" ) |
|---|
| 1279 | <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = *( "," OWS ) ( byte-range-spec / |
|---|
| 1280 | suffix-byte-range-spec ) *( OWS "," [ OWS ( byte-range-spec / |
|---|
| 1281 | suffix-byte-range-spec ) ] ) |
|---|
| 1282 | <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = first-byte-pos "-" [ last-byte-pos ] |
|---|
| 1283 | <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = bytes-unit "=" byte-range-set |
|---|
| 1284 | <a href="#byte.ranges" class="smpl">bytes-unit</a> = "bytes" |
|---|
| 1285 | |
|---|
| 1286 | <a href="#header.content-range" class="smpl">complete-length</a> = 1*DIGIT |
|---|
| 1287 | |
|---|
| 1288 | <a href="#imported.abnf" class="smpl">entity-tag</a> = <entity-tag, defined in [Part4], Section 2.3> |
|---|
| 1289 | |
|---|
| 1290 | <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> = 1*DIGIT |
|---|
| 1291 | |
|---|
| 1292 | <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> = 1*DIGIT |
|---|
| 1293 | |
|---|
| 1294 | <a href="#header.content-range" class="smpl">other-content-range</a> = other-range-unit SP other-range-resp |
|---|
| 1295 | <a href="#header.content-range" class="smpl">other-range-resp</a> = *CHAR |
|---|
| 1296 | <a href="#header.range" class="smpl">other-range-set</a> = 1*CHAR |
|---|
| 1297 | <a href="#range.units.other" class="smpl">other-range-unit</a> = token |
|---|
| 1298 | <a href="#header.range" class="smpl">other-ranges-specifier</a> = other-range-unit "=" other-range-set |
|---|
| 1299 | |
|---|
| 1300 | <a href="#range.units" class="smpl">range-unit</a> = bytes-unit / other-range-unit |
|---|
| 1301 | |
|---|
| 1302 | <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" suffix-length |
|---|
| 1303 | <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*DIGIT |
|---|
| 1304 | |
|---|
| 1305 | <a href="#imported.abnf" class="smpl">token</a> = <token, defined in [Part1], Section 3.2.6> |
|---|
| 1306 | |
|---|
| 1307 | <a href="#header.content-range" class="smpl">unsatisfied-range</a> = "*/" complete-length |
|---|
| 1308 | </pre><h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a> <a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> |
|---|
| 1309 | <p id="rfc.section.E.p.1">Changes up to the first Working Group Last Call draft are summarized in <<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-19#appendix-D">http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-19#appendix-D</a>>. |
|---|
| 1310 | </p> |
|---|
| 1311 | <h2 id="rfc.section.E.1"><a href="#rfc.section.E.1">E.1</a> <a id="changes.since.19" href="#changes.since.19">Since draft-ietf-httpbis-p5-range-19</a></h2> |
|---|
| 1312 | <p id="rfc.section.E.1.p.1">Closed issues: </p> |
|---|
| 1313 | <ul> |
|---|
| 1314 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/358">http://tools.ietf.org/wg/httpbis/trac/ticket/358</a>>: "ABNF list expansion code problem" |
|---|
| 1315 | </li> |
|---|
| 1316 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>>: "ABNF requirements for recipients" |
|---|
| 1317 | </li> |
|---|
| 1318 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/367">http://tools.ietf.org/wg/httpbis/trac/ticket/367</a>>: "reserve 'none' as byte range unit" |
|---|
| 1319 | </li> |
|---|
| 1320 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/368">http://tools.ietf.org/wg/httpbis/trac/ticket/368</a>>: "note introduction of new IANA registries as normative changes" |
|---|
| 1321 | </li> |
|---|
| 1322 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/369">http://tools.ietf.org/wg/httpbis/trac/ticket/369</a>>: "range units vs leading zeroes vs size" |
|---|
| 1323 | </li> |
|---|
| 1324 | </ul> |
|---|
| 1325 | <h2 id="rfc.section.E.2"><a href="#rfc.section.E.2">E.2</a> <a id="changes.since.20" href="#changes.since.20">Since draft-ietf-httpbis-p5-range-20</a></h2> |
|---|
| 1326 | <p id="rfc.section.E.2.p.1"> </p> |
|---|
| 1327 | <ul> |
|---|
| 1328 | <li>Conformance criteria and considerations regarding error handling are now defined in Part 1.</li> |
|---|
| 1329 | </ul> |
|---|
| 1330 | <h2 id="rfc.section.E.3"><a href="#rfc.section.E.3">E.3</a> <a id="changes.since.21" href="#changes.since.21">Since draft-ietf-httpbis-p5-range-21</a></h2> |
|---|
| 1331 | <p id="rfc.section.E.3.p.1">Closed issues: </p> |
|---|
| 1332 | <ul> |
|---|
| 1333 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/175">http://tools.ietf.org/wg/httpbis/trac/ticket/175</a>>: "Security consideration: range flooding" |
|---|
| 1334 | </li> |
|---|
| 1335 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/223">http://tools.ietf.org/wg/httpbis/trac/ticket/223</a>>: "Allowing heuristic caching for new status codes" |
|---|
| 1336 | </li> |
|---|
| 1337 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/311">http://tools.ietf.org/wg/httpbis/trac/ticket/311</a>>: "Add limitations to Range to reduce its use as a denial-of-service tool" |
|---|
| 1338 | </li> |
|---|
| 1339 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/407">http://tools.ietf.org/wg/httpbis/trac/ticket/407</a>>: "416 and multipart/byteranges" |
|---|
| 1340 | </li> |
|---|
| 1341 | </ul> |
|---|
| 1342 | <h2 id="rfc.section.E.4"><a href="#rfc.section.E.4">E.4</a> <a id="changes.since.22" href="#changes.since.22">Since draft-ietf-httpbis-p5-range-22</a></h2> |
|---|
| 1343 | <p id="rfc.section.E.4.p.1">Closed issues: </p> |
|---|
| 1344 | <ul> |
|---|
| 1345 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>>: "explain list expansion in ABNF appendices" |
|---|
| 1346 | </li> |
|---|
| 1347 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/437">http://tools.ietf.org/wg/httpbis/trac/ticket/437</a>>: "incorrect example dates" |
|---|
| 1348 | </li> |
|---|
| 1349 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/438">http://tools.ietf.org/wg/httpbis/trac/ticket/438</a>>: "media type registration template issues" |
|---|
| 1350 | </li> |
|---|
| 1351 | <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/485">http://tools.ietf.org/wg/httpbis/trac/ticket/485</a>>: "MUSTs and other feedback" |
|---|
| 1352 | </li> |
|---|
| 1353 | </ul> |
|---|
| 1354 | <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> |
|---|
| 1355 | <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.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.G">G</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> |
|---|
| 1356 | </p> |
|---|
| 1357 | <div class="print2col"> |
|---|
| 1358 | <ul class="ind"> |
|---|
| 1359 | <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul> |
|---|
| 1360 | <li>206 Partial Content (status code) <a href="#rfc.iref.20"><b>4.1</b></a>, <a href="#rfc.xref.status.206.1">5.2</a>, <a href="#rfc.xref.status.206.2">B</a></li> |
|---|
| 1361 | </ul> |
|---|
| 1362 | </li> |
|---|
| 1363 | <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul> |
|---|
| 1364 | <li>416 Range Not Satisfiable (status code) <a href="#rfc.iref.29"><b>4.4</b></a>, <a href="#rfc.xref.status.416.1">5.2</a></li> |
|---|
| 1365 | </ul> |
|---|
| 1366 | </li> |
|---|
| 1367 | <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul> |
|---|
| 1368 | <li>Accept-Ranges header field <a href="#rfc.xref.header.accept-ranges.1">2</a>, <a href="#rfc.iref.a.1"><b>2.3</b></a>, <a href="#rfc.xref.header.accept-ranges.2">5.1.2</a>, <a href="#rfc.xref.header.accept-ranges.3">5.3</a></li> |
|---|
| 1369 | </ul> |
|---|
| 1370 | </li> |
|---|
| 1371 | <li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul> |
|---|
| 1372 | <li><em>BCP13</em> <a href="#BCP13"><b>8.2</b></a>, <a href="#rfc.xref.BCP13.1">A</a></li> |
|---|
| 1373 | <li><em>BCP90</em> <a href="#rfc.xref.BCP90.1">5.3</a>, <a href="#BCP90"><b>8.2</b></a></li> |
|---|
| 1374 | </ul> |
|---|
| 1375 | </li> |
|---|
| 1376 | <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul> |
|---|
| 1377 | <li>Content-Range header field <a href="#rfc.xref.header.content-range.1">2</a>, <a href="#rfc.iref.c.1"><b>4.2</b></a>, <a href="#rfc.xref.header.content-range.2">4.4</a>, <a href="#rfc.xref.header.content-range.3">5.3</a>, <a href="#rfc.xref.header.content-range.4">B</a></li> |
|---|
| 1378 | </ul> |
|---|
| 1379 | </li> |
|---|
| 1380 | <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul> |
|---|
| 1381 | <li><tt>Grammar</tt> |
|---|
| 1382 | <ul> |
|---|
| 1383 | <li><tt>Accept-Ranges</tt> <a href="#rfc.iref.g.14"><b>2.3</b></a></li> |
|---|
| 1384 | <li><tt>acceptable-ranges</tt> <a href="#rfc.iref.g.15"><b>2.3</b></a></li> |
|---|
| 1385 | <li><tt>byte-content-range</tt> <a href="#rfc.iref.g.19"><b>4.2</b></a></li> |
|---|
| 1386 | <li><tt>byte-range</tt> <a href="#rfc.iref.g.21"><b>4.2</b></a></li> |
|---|
| 1387 | <li><tt>byte-range-resp</tt> <a href="#rfc.iref.g.20"><b>4.2</b></a></li> |
|---|
| 1388 | <li><tt>byte-range-set</tt> <a href="#rfc.iref.g.7"><b>2.1</b></a></li> |
|---|
| 1389 | <li><tt>byte-range-spec</tt> <a href="#rfc.iref.g.8"><b>2.1</b></a></li> |
|---|
| 1390 | <li><tt>byte-ranges-specifier</tt> <a href="#rfc.iref.g.6"><b>2.1</b></a></li> |
|---|
| 1391 | <li><tt>bytes-unit</tt> <a href="#rfc.iref.g.2">2</a>, <a href="#rfc.iref.g.4"><b>2.1</b></a></li> |
|---|
| 1392 | <li><tt>complete-length</tt> <a href="#rfc.iref.g.25"><b>4.2</b></a></li> |
|---|
| 1393 | <li><tt>Content-Range</tt> <a href="#rfc.iref.g.18"><b>4.2</b></a></li> |
|---|
| 1394 | <li><tt>first-byte-pos</tt> <a href="#rfc.iref.g.9"><b>2.1</b></a></li> |
|---|
| 1395 | <li><tt>If-Range</tt> <a href="#rfc.iref.g.17"><b>3.2</b></a></li> |
|---|
| 1396 | <li><tt>last-byte-pos</tt> <a href="#rfc.iref.g.10"><b>2.1</b></a></li> |
|---|
| 1397 | <li><tt>other-content-range</tt> <a href="#rfc.iref.g.23"><b>4.2</b></a></li> |
|---|
| 1398 | <li><tt>other-range-resp</tt> <a href="#rfc.iref.g.24"><b>4.2</b></a></li> |
|---|
| 1399 | <li><tt>other-range-unit</tt> <a href="#rfc.iref.g.3">2</a>, <a href="#rfc.iref.g.13"><b>2.2</b></a></li> |
|---|
| 1400 | <li><tt>Range</tt> <a href="#rfc.iref.g.16"><b>3.1</b></a></li> |
|---|
| 1401 | <li><tt>range-unit</tt> <a href="#rfc.iref.g.1"><b>2</b></a></li> |
|---|
| 1402 | <li><tt>ranges-specifier</tt> <a href="#rfc.iref.g.5"><b>2.1</b></a></li> |
|---|
| 1403 | <li><tt>suffix-byte-range-spec</tt> <a href="#rfc.iref.g.11"><b>2.1</b></a></li> |
|---|
| 1404 | <li><tt>suffix-length</tt> <a href="#rfc.iref.g.12"><b>2.1</b></a></li> |
|---|
| 1405 | <li><tt>unsatisfied-range</tt> <a href="#rfc.iref.g.22"><b>4.2</b></a></li> |
|---|
| 1406 | </ul> |
|---|
| 1407 | </li> |
|---|
| 1408 | </ul> |
|---|
| 1409 | </li> |
|---|
| 1410 | <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul> |
|---|
| 1411 | <li>If-Range header field <a href="#rfc.xref.header.if-range.1">3.1</a>, <a href="#rfc.iref.i.1"><b>3.2</b></a>, <a href="#rfc.xref.header.if-range.2">5.3</a></li> |
|---|
| 1412 | </ul> |
|---|
| 1413 | </li> |
|---|
| 1414 | <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul> |
|---|
| 1415 | <li>Media Type |
|---|
| 1416 | <ul> |
|---|
| 1417 | <li>multipart/byteranges <a href="#rfc.iref.m.1"><b>A</b></a></li> |
|---|
| 1418 | <li>multipart/x-byteranges <a href="#rfc.iref.m.4">A</a></li> |
|---|
| 1419 | </ul> |
|---|
| 1420 | </li> |
|---|
| 1421 | <li>multipart/byteranges Media Type <a href="#rfc.iref.m.2"><b>A</b></a></li> |
|---|
| 1422 | <li>multipart/x-byteranges Media Type <a href="#rfc.iref.m.3">A</a></li> |
|---|
| 1423 | </ul> |
|---|
| 1424 | </li> |
|---|
| 1425 | <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> |
|---|
| 1426 | <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1.1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">6</a>, <a href="#rfc.xref.Part1.4">7</a>, <a href="#Part1"><b>8.1</b></a>, <a href="#rfc.xref.Part1.5">C</a>, <a href="#rfc.xref.Part1.6">C</a>, <a href="#rfc.xref.Part1.7">C</a>, <a href="#rfc.xref.Part1.8">D</a><ul> |
|---|
| 1427 | <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.8">D</a></li> |
|---|
| 1428 | <li><em>Section 2.5</em> <a href="#rfc.xref.Part1.1">1.1</a></li> |
|---|
| 1429 | <li><em>Section 3.2.3</em> <a href="#rfc.xref.Part1.6">C</a></li> |
|---|
| 1430 | <li><em>Section 3.2.6</em> <a href="#rfc.xref.Part1.7">C</a></li> |
|---|
| 1431 | <li><em>Section 9</em> <a href="#rfc.xref.Part1.4">7</a></li> |
|---|
| 1432 | </ul> |
|---|
| 1433 | </li> |
|---|
| 1434 | <li><em>Part2</em> <a href="#rfc.xref.Part2.1">2.1</a>, <a href="#rfc.xref.Part2.2">6</a>, <a href="#Part2"><b>8.1</b></a>, <a href="#rfc.xref.Part2.3">C</a><ul> |
|---|
| 1435 | <li><em>Section 3</em> <a href="#rfc.xref.Part2.1">2.1</a></li> |
|---|
| 1436 | <li><em>Section 7.1.1.1</em> <a href="#rfc.xref.Part2.3">C</a></li> |
|---|
| 1437 | </ul> |
|---|
| 1438 | </li> |
|---|
| 1439 | <li><em>Part4</em> <a href="#rfc.xref.Part4.1">3.1</a>, <a href="#rfc.xref.Part4.2">3.2</a>, <a href="#rfc.xref.Part4.3">3.2</a>, <a href="#rfc.xref.Part4.4">4.3</a>, <a href="#rfc.xref.Part4.5">4.3</a>, <a href="#Part4"><b>8.1</b></a>, <a href="#rfc.xref.Part4.6">C</a><ul> |
|---|
| 1440 | <li><em>Section 2.2.2</em> <a href="#rfc.xref.Part4.2">3.2</a>, <a href="#rfc.xref.Part4.3">3.2</a>, <a href="#rfc.xref.Part4.5">4.3</a></li> |
|---|
| 1441 | <li><em>Section 2.3</em> <a href="#rfc.xref.Part4.4">4.3</a>, <a href="#rfc.xref.Part4.6">C</a></li> |
|---|
| 1442 | </ul> |
|---|
| 1443 | </li> |
|---|
| 1444 | <li><em>Part6</em> <a href="#rfc.xref.Part6.1">4.1</a>, <a href="#Part6"><b>8.1</b></a><ul> |
|---|
| 1445 | <li><em>Section 4.1.2</em> <a href="#rfc.xref.Part6.1">4.1</a></li> |
|---|
| 1446 | </ul> |
|---|
| 1447 | </li> |
|---|
| 1448 | </ul> |
|---|
| 1449 | </li> |
|---|
| 1450 | <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul> |
|---|
| 1451 | <li>Range header field <a href="#rfc.xref.header.range.1">2</a>, <a href="#rfc.iref.r.1"><b>3.1</b></a>, <a href="#rfc.xref.header.range.2">4.1</a>, <a href="#rfc.xref.header.range.3">4.4</a>, <a href="#rfc.xref.header.range.4">5.3</a></li> |
|---|
| 1452 | <li><em>RFC2046</em> <a href="#RFC2046"><b>8.1</b></a>, <a href="#rfc.xref.RFC2046.1">A</a>, <a href="#rfc.xref.RFC2046.2">A</a><ul> |
|---|
| 1453 | <li><em>Section 5.1</em> <a href="#rfc.xref.RFC2046.1">A</a></li> |
|---|
| 1454 | </ul> |
|---|
| 1455 | </li> |
|---|
| 1456 | <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>8.1</b></a></li> |
|---|
| 1457 | <li><em>RFC2616</em> <a href="#RFC2616"><b>8.2</b></a></li> |
|---|
| 1458 | <li><em>RFC5226</em> <a href="#rfc.xref.RFC5226.1">5.1.1</a>, <a href="#RFC5226"><b>8.2</b></a><ul> |
|---|
| 1459 | <li><em>Section 4.1</em> <a href="#rfc.xref.RFC5226.1">5.1.1</a></li> |
|---|
| 1460 | </ul> |
|---|
| 1461 | </li> |
|---|
| 1462 | <li><em>RFC5234</em> <a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#RFC5234"><b>8.1</b></a>, <a href="#rfc.xref.RFC5234.2">C</a><ul> |
|---|
| 1463 | <li><em>Appendix B.1</em> <a href="#rfc.xref.RFC5234.2">C</a></li> |
|---|
| 1464 | </ul> |
|---|
| 1465 | </li> |
|---|
| 1466 | </ul> |
|---|
| 1467 | </li> |
|---|
| 1468 | </ul> |
|---|
| 1469 | </div> |
|---|
| 1470 | </body> |
|---|
| 1471 | </html> |
|---|
![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
