| 1 | <!DOCTYPE html |
|---|
| 2 | PUBLIC "-//W3C//DTD HTML 4.01//EN"> |
|---|
| 3 | <html lang="en"> |
|---|
| 4 | <head profile="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 type="application/javascript"> |
|---|
| 7 | var buttonsAdded = false; |
|---|
| 8 | |
|---|
| 9 | function initFeedback() { |
|---|
| 10 | var fb = document.createElement("div"); |
|---|
| 11 | fb.className = "feedback noprint"; |
|---|
| 12 | fb.setAttribute("onclick", "feedback();"); |
|---|
| 13 | fb.appendChild(document.createTextNode("feedback")); |
|---|
| 14 | |
|---|
| 15 | document.body.appendChild(fb); |
|---|
| 16 | } |
|---|
| 17 | |
|---|
| 18 | function feedback() { |
|---|
| 19 | toggleButtonsToElementsByName("h2"); |
|---|
| 20 | toggleButtonsToElementsByName("h3"); |
|---|
| 21 | toggleButtonsToElementsByName("h4"); |
|---|
| 22 | toggleButtonsToElementsByName("h5"); |
|---|
| 23 | |
|---|
| 24 | buttonsAdded = !buttonsAdded; |
|---|
| 25 | } |
|---|
| 26 | |
|---|
| 27 | function toggleButtonsToElementsByName(name) { |
|---|
| 28 | var list = document.getElementsByTagName(name); |
|---|
| 29 | for (var i = 0; i < list.length; i++) { |
|---|
| 30 | toggleButton(list.item(i)); |
|---|
| 31 | } |
|---|
| 32 | } |
|---|
| 33 | |
|---|
| 34 | function toggleButton(node) { |
|---|
| 35 | if (! buttonsAdded) { |
|---|
| 36 | |
|---|
| 37 | // docname |
|---|
| 38 | var template = "mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&body=<{ref}>:"; |
|---|
| 39 | |
|---|
| 40 | var id = node.getAttribute("id"); |
|---|
| 41 | // better id available? |
|---|
| 42 | var titlelinks = node.getElementsByTagName("a"); |
|---|
| 43 | for (var i = 0; i < titlelinks.length; i++) { |
|---|
| 44 | var tl = titlelinks.item(i); |
|---|
| 45 | if (tl.getAttribute("id")) { |
|---|
| 46 | id = tl.getAttribute("id"); |
|---|
| 47 | } |
|---|
| 48 | } |
|---|
| 49 | |
|---|
| 50 | // ref |
|---|
| 51 | var ref = window.location.toString(); |
|---|
| 52 | var hash = ref.indexOf("#"); |
|---|
| 53 | if (hash != -1) { |
|---|
| 54 | ref = ref.substring(0, hash); |
|---|
| 55 | } |
|---|
| 56 | if (id != "") { |
|---|
| 57 | ref += "#" + id; |
|---|
| 58 | } |
|---|
| 59 | |
|---|
| 60 | // docname |
|---|
| 61 | var docname = "draft-ietf-httpbis-p5-range-latest"; |
|---|
| 62 | |
|---|
| 63 | // section |
|---|
| 64 | var section = node.textContent; |
|---|
| 65 | section = section.replace("\u00a0", " "); |
|---|
| 66 | |
|---|
| 67 | // build URI from template |
|---|
| 68 | var uri = template.replace("{docname}", encodeURIComponent(docname)); |
|---|
| 69 | uri = uri.replace("{section}", encodeURIComponent(section)); |
|---|
| 70 | uri = uri.replace("{ref}", encodeURIComponent(ref)); |
|---|
| 71 | |
|---|
| 72 | var button = document.createElement("a"); |
|---|
| 73 | button.className = "fbbutton noprint"; |
|---|
| 74 | button.setAttribute("href", uri); |
|---|
| 75 | button.appendChild(document.createTextNode("send feedback")); |
|---|
| 76 | node.appendChild(button); |
|---|
| 77 | } |
|---|
| 78 | else { |
|---|
| 79 | var buttons = node.getElementsByTagName("a"); |
|---|
| 80 | for (var i = 0; i < buttons.length; i++) { |
|---|
| 81 | var b = buttons.item(i); |
|---|
| 82 | if (b.className == "fbbutton noprint") { |
|---|
| 83 | node.removeChild(b); |
|---|
| 84 | } |
|---|
| 85 | } |
|---|
| 86 | } |
|---|
| 87 | }</script><style type="text/css" title="Xml2Rfc (sans serif)"> |
|---|
| 88 | a { |
|---|
| 89 | text-decoration: none; |
|---|
| 90 | } |
|---|
| 91 | a.smpl { |
|---|
| 92 | color: black; |
|---|
| 93 | } |
|---|
| 94 | a:hover { |
|---|
| 95 | text-decoration: underline; |
|---|
| 96 | } |
|---|
| 97 | a:active { |
|---|
| 98 | text-decoration: underline; |
|---|
| 99 | } |
|---|
| 100 | address { |
|---|
| 101 | margin-top: 1em; |
|---|
| 102 | margin-left: 2em; |
|---|
| 103 | font-style: normal; |
|---|
| 104 | } |
|---|
| 105 | body { |
|---|
| 106 | color: black; |
|---|
| 107 | font-family: cambria, georgia, serif; |
|---|
| 108 | font-size: 12pt; |
|---|
| 109 | margin: 2em auto; |
|---|
| 110 | max-width: 1000px; |
|---|
| 111 | } |
|---|
| 112 | samp, tt, code, pre { |
|---|
| 113 | font-family: consolas, monaco, monospace; |
|---|
| 114 | } |
|---|
| 115 | cite { |
|---|
| 116 | font-style: normal; |
|---|
| 117 | } |
|---|
| 118 | div.note { |
|---|
| 119 | margin-left: 2em; |
|---|
| 120 | } |
|---|
| 121 | dl { |
|---|
| 122 | margin-left: 2em; |
|---|
| 123 | } |
|---|
| 124 | dl > dt { |
|---|
| 125 | float: left; |
|---|
| 126 | margin-right: 1em; |
|---|
| 127 | } |
|---|
| 128 | dl.nohang > dt { |
|---|
| 129 | float: none; |
|---|
| 130 | } |
|---|
| 131 | dl > dd { |
|---|
| 132 | margin-bottom: .5em; |
|---|
| 133 | } |
|---|
| 134 | dl.compact > dd { |
|---|
| 135 | margin-bottom: .0em; |
|---|
| 136 | } |
|---|
| 137 | dl > dd > dl { |
|---|
| 138 | margin-top: 0.5em; |
|---|
| 139 | } |
|---|
| 140 | ul.empty { |
|---|
| 141 | list-style-type: none; |
|---|
| 142 | } |
|---|
| 143 | ul.empty li { |
|---|
| 144 | margin-top: .5em; |
|---|
| 145 | } |
|---|
| 146 | dl p { |
|---|
| 147 | margin-left: 0em; |
|---|
| 148 | } |
|---|
| 149 | dl.reference > dt { |
|---|
| 150 | font-weight: bold; |
|---|
| 151 | } |
|---|
| 152 | dl.reference > dd { |
|---|
| 153 | margin-left: 6em; |
|---|
| 154 | } |
|---|
| 155 | h1 { |
|---|
| 156 | color: green; |
|---|
| 157 | font-size: 150%; |
|---|
| 158 | line-height: 18pt; |
|---|
| 159 | font-weight: bold; |
|---|
| 160 | text-align: center; |
|---|
| 161 | margin-top: 36pt; |
|---|
| 162 | margin-bottom: 0pt; |
|---|
| 163 | } |
|---|
| 164 | h2 { |
|---|
| 165 | font-size: 130%; |
|---|
| 166 | line-height: 21pt; |
|---|
| 167 | page-break-after: avoid; |
|---|
| 168 | } |
|---|
| 169 | h2.np { |
|---|
| 170 | page-break-before: always; |
|---|
| 171 | } |
|---|
| 172 | h3 { |
|---|
| 173 | font-size: 120%; |
|---|
| 174 | line-height: 15pt; |
|---|
| 175 | page-break-after: avoid; |
|---|
| 176 | } |
|---|
| 177 | h4 { |
|---|
| 178 | font-size: 110%; |
|---|
| 179 | page-break-after: avoid; |
|---|
| 180 | } |
|---|
| 181 | h5, h6 { |
|---|
| 182 | page-break-after: avoid; |
|---|
| 183 | } |
|---|
| 184 | h1 a, h2 a, h3 a, h4 a, h5 a, h6 a { |
|---|
| 185 | color: black; |
|---|
| 186 | } |
|---|
| 187 | img { |
|---|
| 188 | margin-left: 3em; |
|---|
| 189 | } |
|---|
| 190 | li { |
|---|
| 191 | margin-left: 2em; |
|---|
| 192 | } |
|---|
| 193 | ol { |
|---|
| 194 | margin-left: 2em; |
|---|
| 195 | } |
|---|
| 196 | ol.la { |
|---|
| 197 | list-style-type: lower-alpha; |
|---|
| 198 | } |
|---|
| 199 | ol.ua { |
|---|
| 200 | list-style-type: upper-alpha; |
|---|
| 201 | } |
|---|
| 202 | ol p { |
|---|
| 203 | margin-left: 0em; |
|---|
| 204 | } |
|---|
| 205 | p { |
|---|
| 206 | margin-left: 2em; |
|---|
| 207 | } |
|---|
| 208 | pre { |
|---|
| 209 | font-size: 11pt; |
|---|
| 210 | margin-left: 3em; |
|---|
| 211 | background-color: lightyellow; |
|---|
| 212 | padding: .25em; |
|---|
| 213 | page-break-inside: avoid; |
|---|
| 214 | } |
|---|
| 215 | pre.text2 { |
|---|
| 216 | border-style: dotted; |
|---|
| 217 | border-width: 1px; |
|---|
| 218 | background-color: #f0f0f0; |
|---|
| 219 | } |
|---|
| 220 | pre.inline { |
|---|
| 221 | background-color: white; |
|---|
| 222 | padding: 0em; |
|---|
| 223 | page-break-inside: auto; |
|---|
| 224 | } |
|---|
| 225 | pre.text { |
|---|
| 226 | border-style: dotted; |
|---|
| 227 | border-width: 1px; |
|---|
| 228 | background-color: #f8f8f8; |
|---|
| 229 | } |
|---|
| 230 | pre.drawing { |
|---|
| 231 | border-style: solid; |
|---|
| 232 | border-width: 1px; |
|---|
| 233 | background-color: #f8f8f8; |
|---|
| 234 | padding: 2em; |
|---|
| 235 | } |
|---|
| 236 | table { |
|---|
| 237 | margin-left: 2em; |
|---|
| 238 | } |
|---|
| 239 | table.tt { |
|---|
| 240 | vertical-align: top; |
|---|
| 241 | border-color: gray; |
|---|
| 242 | } |
|---|
| 243 | table.tt th { |
|---|
| 244 | border-color: gray; |
|---|
| 245 | } |
|---|
| 246 | table.tt td { |
|---|
| 247 | border-color: gray; |
|---|
| 248 | } |
|---|
| 249 | table.all { |
|---|
| 250 | border-style: solid; |
|---|
| 251 | border-width: 2px; |
|---|
| 252 | } |
|---|
| 253 | table.full { |
|---|
| 254 | border-style: solid; |
|---|
| 255 | border-width: 2px; |
|---|
| 256 | } |
|---|
| 257 | table.tt td { |
|---|
| 258 | vertical-align: top; |
|---|
| 259 | } |
|---|
| 260 | table.all td { |
|---|
| 261 | border-style: solid; |
|---|
| 262 | border-width: 1px; |
|---|
| 263 | } |
|---|
| 264 | table.full td { |
|---|
| 265 | border-style: none solid; |
|---|
| 266 | border-width: 1px; |
|---|
| 267 | } |
|---|
| 268 | table.tt th { |
|---|
| 269 | vertical-align: top; |
|---|
| 270 | } |
|---|
| 271 | table.all th { |
|---|
| 272 | border-style: solid; |
|---|
| 273 | border-width: 1px; |
|---|
| 274 | } |
|---|
| 275 | table.full th { |
|---|
| 276 | border-style: solid; |
|---|
| 277 | border-width: 1px 1px 2px 1px; |
|---|
| 278 | } |
|---|
| 279 | table.headers th { |
|---|
| 280 | border-style: none none solid none; |
|---|
| 281 | border-width: 2px; |
|---|
| 282 | } |
|---|
| 283 | table.tleft { |
|---|
| 284 | margin-right: auto; |
|---|
| 285 | } |
|---|
| 286 | table.tright { |
|---|
| 287 | margin-left: auto; |
|---|
| 288 | } |
|---|
| 289 | table.tcenter { |
|---|
| 290 | margin-left: auto; |
|---|
| 291 | margin-right: auto; |
|---|
| 292 | } |
|---|
| 293 | caption { |
|---|
| 294 | caption-side: bottom; |
|---|
| 295 | font-weight: bold; |
|---|
| 296 | font-size: 10pt; |
|---|
| 297 | margin-top: .5em; |
|---|
| 298 | } |
|---|
| 299 | |
|---|
| 300 | table.header { |
|---|
| 301 | border-spacing: 1px; |
|---|
| 302 | width: 95%; |
|---|
| 303 | font-size: 11pt; |
|---|
| 304 | color: white; |
|---|
| 305 | } |
|---|
| 306 | td.top { |
|---|
| 307 | vertical-align: top; |
|---|
| 308 | } |
|---|
| 309 | td.topnowrap { |
|---|
| 310 | vertical-align: top; |
|---|
| 311 | white-space: nowrap; |
|---|
| 312 | } |
|---|
| 313 | table.header td { |
|---|
| 314 | background-color: gray; |
|---|
| 315 | width: 50%; |
|---|
| 316 | } |
|---|
| 317 | table.header a { |
|---|
| 318 | color: white; |
|---|
| 319 | } |
|---|
| 320 | thead { |
|---|
| 321 | display:table-header-group; |
|---|
| 322 | } |
|---|
| 323 | ul.toc, ul.toc ul { |
|---|
| 324 | list-style: none; |
|---|
| 325 | margin-left: 1.5em; |
|---|
| 326 | padding-left: 0em; |
|---|
| 327 | } |
|---|
| 328 | ul.toc li { |
|---|
| 329 | line-height: 150%; |
|---|
| 330 | font-weight: bold; |
|---|
| 331 | margin-left: 0em; |
|---|
| 332 | } |
|---|
| 333 | ul.toc li li { |
|---|
| 334 | line-height: normal; |
|---|
| 335 | font-weight: normal; |
|---|
| 336 | font-size: 11pt; |
|---|
| 337 | margin-left: 0em; |
|---|
| 338 | } |
|---|
| 339 | li.excluded { |
|---|
| 340 | font-size: 0pt; |
|---|
| 341 | } |
|---|
| 342 | ul p { |
|---|
| 343 | margin-left: 0em; |
|---|
| 344 | } |
|---|
| 345 | .filename, h1, h2, h3, h4 { |
|---|
| 346 | font-family: candara, calibri, segoe, optima, arial, sans-serif; |
|---|
| 347 | } |
|---|
| 348 | ul.ind, ul.ind ul { |
|---|
| 349 | list-style: none; |
|---|
| 350 | margin-left: 1.5em; |
|---|
| 351 | padding-left: 0em; |
|---|
| 352 | page-break-before: avoid; |
|---|
| 353 | } |
|---|
| 354 | ul.ind li { |
|---|
| 355 | font-weight: bold; |
|---|
| 356 | line-height: 200%; |
|---|
| 357 | margin-left: 0em; |
|---|
| 358 | } |
|---|
| 359 | ul.ind li li { |
|---|
| 360 | font-weight: normal; |
|---|
| 361 | line-height: 150%; |
|---|
| 362 | margin-left: 0em; |
|---|
| 363 | } |
|---|
| 364 | .avoidbreakinside { |
|---|
| 365 | page-break-inside: avoid; |
|---|
| 366 | } |
|---|
| 367 | .avoidbreakafter { |
|---|
| 368 | page-break-after: avoid; |
|---|
| 369 | } |
|---|
| 370 | .bcp14 { |
|---|
| 371 | font-style: normal; |
|---|
| 372 | text-transform: lowercase; |
|---|
| 373 | font-variant: small-caps; |
|---|
| 374 | } |
|---|
| 375 | .comment { |
|---|
| 376 | background-color: yellow; |
|---|
| 377 | } |
|---|
| 378 | .center { |
|---|
| 379 | text-align: center; |
|---|
| 380 | } |
|---|
| 381 | .error { |
|---|
| 382 | color: red; |
|---|
| 383 | font-style: italic; |
|---|
| 384 | font-weight: bold; |
|---|
| 385 | } |
|---|
| 386 | .figure { |
|---|
| 387 | font-weight: bold; |
|---|
| 388 | text-align: center; |
|---|
| 389 | font-size: 10pt; |
|---|
| 390 | } |
|---|
| 391 | .filename { |
|---|
| 392 | color: #333333; |
|---|
| 393 | font-size: 112%; |
|---|
| 394 | font-weight: bold; |
|---|
| 395 | line-height: 21pt; |
|---|
| 396 | text-align: center; |
|---|
| 397 | margin-top: 0pt; |
|---|
| 398 | } |
|---|
| 399 | .fn { |
|---|
| 400 | font-weight: bold; |
|---|
| 401 | } |
|---|
| 402 | .left { |
|---|
| 403 | text-align: left; |
|---|
| 404 | } |
|---|
| 405 | .right { |
|---|
| 406 | text-align: right; |
|---|
| 407 | } |
|---|
| 408 | .warning { |
|---|
| 409 | font-size: 130%; |
|---|
| 410 | background-color: yellow; |
|---|
| 411 | }.feedback { |
|---|
| 412 | position: fixed; |
|---|
| 413 | bottom: 1%; |
|---|
| 414 | right: 1%; |
|---|
| 415 | padding: 3px 5px; |
|---|
| 416 | color: white; |
|---|
| 417 | border-radius: 5px; |
|---|
| 418 | background: #006400; |
|---|
| 419 | border: 1px solid silver; |
|---|
| 420 | -webkit-user-select: none; |
|---|
| 421 | -moz-user-select: none; |
|---|
| 422 | -ms-user-select: none; |
|---|
| 423 | } |
|---|
| 424 | .fbbutton { |
|---|
| 425 | margin-left: 1em; |
|---|
| 426 | color: #303030; |
|---|
| 427 | font-size: small; |
|---|
| 428 | font-weight: normal; |
|---|
| 429 | background: #d0d000; |
|---|
| 430 | padding: 1px 4px; |
|---|
| 431 | border: 1px solid silver; |
|---|
| 432 | border-radius: 5px; |
|---|
| 433 | } |
|---|
| 434 | .publishedasrfc { |
|---|
| 435 | background-color: yellow; |
|---|
| 436 | color: green; |
|---|
| 437 | font-size: 14pt; |
|---|
| 438 | text-align: center; |
|---|
| 439 | } |
|---|
| 440 | |
|---|
| 441 | @media screen { |
|---|
| 442 | pre.text, pre.text2 { |
|---|
| 443 | width: 69em; |
|---|
| 444 | } |
|---|
| 445 | } |
|---|
| 446 | |
|---|
| 447 | @media print { |
|---|
| 448 | .noprint { |
|---|
| 449 | display: none; |
|---|
| 450 | } |
|---|
| 451 | |
|---|
| 452 | a { |
|---|
| 453 | color: black; |
|---|
| 454 | text-decoration: none; |
|---|
| 455 | } |
|---|
| 456 | |
|---|
| 457 | table.header { |
|---|
| 458 | width: 90%; |
|---|
| 459 | } |
|---|
| 460 | |
|---|
| 461 | td.header { |
|---|
| 462 | width: 50%; |
|---|
| 463 | color: black; |
|---|
| 464 | background-color: white; |
|---|
| 465 | vertical-align: top; |
|---|
| 466 | font-size: 110%; |
|---|
| 467 | } |
|---|
| 468 | |
|---|
| 469 | ul.toc a:last-child::after { |
|---|
| 470 | content: leader('.') target-counter(attr(href), page); |
|---|
| 471 | } |
|---|
| 472 | |
|---|
| 473 | ul.ind li li a { |
|---|
| 474 | content: target-counter(attr(href), page); |
|---|
| 475 | } |
|---|
| 476 | |
|---|
| 477 | pre { |
|---|
| 478 | font-size: 10pt; |
|---|
| 479 | } |
|---|
| 480 | |
|---|
| 481 | .print2col { |
|---|
| 482 | column-count: 2; |
|---|
| 483 | -moz-column-count: 2; |
|---|
| 484 | column-fill: auto; |
|---|
| 485 | } |
|---|
| 486 | } |
|---|
| 487 | |
|---|
| 488 | @page { |
|---|
| 489 | @top-left { |
|---|
| 490 | content: "Internet-Draft"; |
|---|
| 491 | } |
|---|
| 492 | @top-right { |
|---|
| 493 | content: "June 2014"; |
|---|
| 494 | } |
|---|
| 495 | @top-center { |
|---|
| 496 | content: "HTTP/1.1 Range Requests"; |
|---|
| 497 | } |
|---|
| 498 | @bottom-left { |
|---|
| 499 | content: "Fielding, et al."; |
|---|
| 500 | } |
|---|
| 501 | @bottom-center { |
|---|
| 502 | content: "Expires December 2014"; |
|---|
| 503 | } |
|---|
| 504 | @bottom-right { |
|---|
| 505 | content: "[Page " counter(page) "]"; |
|---|
| 506 | } |
|---|
| 507 | } |
|---|
| 508 | |
|---|
| 509 | @page:first { |
|---|
| 510 | @top-left { |
|---|
| 511 | content: normal; |
|---|
| 512 | } |
|---|
| 513 | @top-right { |
|---|
| 514 | content: normal; |
|---|
| 515 | } |
|---|
| 516 | @top-center { |
|---|
| 517 | content: normal; |
|---|
| 518 | } |
|---|
| 519 | } |
|---|
| 520 | </style><link rel="Contents" href="#rfc.toc"> |
|---|
| 521 | <link rel="Author" href="#rfc.authors"> |
|---|
| 522 | <link rel="Copyright" href="#rfc.copyrightnotice"> |
|---|
| 523 | <link rel="Index" href="#rfc.index"> |
|---|
| 524 | <link rel="Chapter" title="1 Introduction" href="#rfc.section.1"> |
|---|
| 525 | <link rel="Chapter" title="2 Range Units" href="#rfc.section.2"> |
|---|
| 526 | <link rel="Chapter" title="3 Range Requests" href="#rfc.section.3"> |
|---|
| 527 | <link rel="Chapter" title="4 Responses to a Range Request" href="#rfc.section.4"> |
|---|
| 528 | <link rel="Chapter" title="5 IANA Considerations" href="#rfc.section.5"> |
|---|
| 529 | <link rel="Chapter" title="6 Security Considerations" href="#rfc.section.6"> |
|---|
| 530 | <link rel="Chapter" title="7 Acknowledgments" href="#rfc.section.7"> |
|---|
| 531 | <link rel="Chapter" href="#rfc.section.8" title="8 References"> |
|---|
| 532 | <link rel="Appendix" title="A Internet Media Type multipart/byteranges" href="#rfc.section.A"> |
|---|
| 533 | <link rel="Appendix" title="B Changes from RFC 2616" href="#rfc.section.B"> |
|---|
| 534 | <link rel="Appendix" title="C Imported ABNF" href="#rfc.section.C"> |
|---|
| 535 | <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D"> |
|---|
| 536 | <link rel="Alternate" title="RFC7233" href="http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7233.html"> |
|---|
| 537 | <link href="p4-conditional.html" rel="prev"> |
|---|
| 538 | <link href="p6-cache.html" rel="next"> |
|---|
| 539 | <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.756, 2015/12/31 17:59:21, XSLT vendor: Saxonica http://www.saxonica.com/"> |
|---|
| 540 | <meta name="keywords" content="Hypertext Transfer Protocol, HTTP, HTTP Range Requests"> |
|---|
| 541 | <link rel="schema.dct" href="http://purl.org/dc/terms/"> |
|---|
| 542 | <meta name="dct.creator" content="Fielding, R."> |
|---|
| 543 | <meta name="dct.creator" content="Lafon, Y."> |
|---|
| 544 | <meta name="dct.creator" content="Reschke, J. F."> |
|---|
| 545 | <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> |
|---|
| 546 | <meta name="dct.issued" scheme="ISO8601" content="2014-06"> |
|---|
| 547 | <meta name="dct.replaces" content="urn:ietf:rfc:2616"> |
|---|
| 548 | <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests."> |
|---|
| 549 | <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests."> |
|---|
| 550 | </head> |
|---|
| 551 | <body onload="initFeedback();"> |
|---|
| 552 | <table class="header" id="rfc.headerblock"> |
|---|
| 553 | <tbody> |
|---|
| 554 | <tr> |
|---|
| 555 | <td class="left">HTTPbis Working Group</td> |
|---|
| 556 | <td class="right">R. Fielding, Editor</td> |
|---|
| 557 | </tr> |
|---|
| 558 | <tr> |
|---|
| 559 | <td class="left">Internet-Draft</td> |
|---|
| 560 | <td class="right">Adobe</td> |
|---|
| 561 | </tr> |
|---|
| 562 | <tr> |
|---|
| 563 | <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved) |
|---|
| 564 | </td> |
|---|
| 565 | <td class="right">Y. Lafon, Editor</td> |
|---|
| 566 | </tr> |
|---|
| 567 | <tr> |
|---|
| 568 | <td class="left">Intended status: Standards Track</td> |
|---|
| 569 | <td class="right">W3C</td> |
|---|
| 570 | </tr> |
|---|
| 571 | <tr> |
|---|
| 572 | <td class="left">Expires: December 2014</td> |
|---|
| 573 | <td class="right">J. Reschke, Editor</td> |
|---|
| 574 | </tr> |
|---|
| 575 | <tr> |
|---|
| 576 | <td class="left"></td> |
|---|
| 577 | <td class="right">greenbytes</td> |
|---|
| 578 | </tr> |
|---|
| 579 | <tr> |
|---|
| 580 | <td class="left"></td> |
|---|
| 581 | <td class="right">June 2014</td> |
|---|
| 582 | </tr> |
|---|
| 583 | </tbody> |
|---|
| 584 | </table> |
|---|
| 585 | <div id="rfc.title"> |
|---|
| 586 | <h1>Hypertext Transfer Protocol (HTTP/1.1): Range Requests</h1> |
|---|
| 587 | <div class="filename">draft-ietf-httpbis-p5-range-latest</div> |
|---|
| 588 | </div> |
|---|
| 589 | <p class="publishedasrfc"><b>Note:</b> a later version of this document has been published as <a href="http://svn.tools.ietf.org/svn/wg/httpbis/specs/rfc7233.html">RFC7233</a>. |
|---|
| 590 | |
|---|
| 591 | </p> |
|---|
| 592 | <h2 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h2> |
|---|
| 593 | <p>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for |
|---|
| 594 | distributed, collaborative, hypertext information systems. This document defines range |
|---|
| 595 | requests and the rules for constructing and combining responses to those requests. |
|---|
| 596 | </p> |
|---|
| 597 | <h2 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h2> |
|---|
| 598 | <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), |
|---|
| 599 | 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>>. |
|---|
| 600 | </p> |
|---|
| 601 | <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>>. |
|---|
| 602 | </p> |
|---|
| 603 | <p><em>This is a temporary document for the purpose of tracking the editorial changes made |
|---|
| 604 | during the AUTH48 (RFC publication) phase.</em> |
|---|
| 605 | </p> |
|---|
| 606 | <div id="rfc.status"> |
|---|
| 607 | <h2><a href="#rfc.status">Status of This Memo</a></h2> |
|---|
| 608 | <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 |
|---|
| 609 | and BCP 79. |
|---|
| 610 | </p> |
|---|
| 611 | <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). |
|---|
| 612 | Note that other groups may also distribute working documents as Internet-Drafts. The |
|---|
| 613 | list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>. |
|---|
| 614 | </p> |
|---|
| 615 | <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, |
|---|
| 616 | replaced, or obsoleted by other documents at any time. It is inappropriate to use |
|---|
| 617 | Internet-Drafts as reference material or to cite them other than as “work in progress”. |
|---|
| 618 | </p> |
|---|
| 619 | <p>This Internet-Draft will expire in December 2014.</p> |
|---|
| 620 | </div> |
|---|
| 621 | <div id="rfc.copyrightnotice"> |
|---|
| 622 | <h2><a href="#rfc.copyrightnotice">Copyright Notice</a></h2> |
|---|
| 623 | <p>Copyright © 2014 IETF Trust and the persons identified as the document authors. All |
|---|
| 624 | rights reserved. |
|---|
| 625 | </p> |
|---|
| 626 | <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating |
|---|
| 627 | 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 |
|---|
| 628 | carefully, as they describe your rights and restrictions with respect to this document. |
|---|
| 629 | Code Components extracted from this document must include Simplified BSD License text |
|---|
| 630 | as described in Section 4.e of the Trust Legal Provisions and are provided without |
|---|
| 631 | warranty as described in the Simplified BSD License. |
|---|
| 632 | </p> |
|---|
| 633 | <p>This document may contain material from IETF Documents or IETF Contributions published |
|---|
| 634 | or made publicly available before November 10, 2008. The person(s) controlling the |
|---|
| 635 | copyright in some of this material may not have granted the IETF Trust the right to |
|---|
| 636 | allow modifications of such material outside the IETF Standards Process. Without obtaining |
|---|
| 637 | an adequate license from the person(s) controlling the copyright in such materials, |
|---|
| 638 | this document may not be modified outside the IETF Standards Process, and derivative |
|---|
| 639 | works of it may not be created outside the IETF Standards Process, except to format |
|---|
| 640 | it for publication as an RFC or to translate it into languages other than English. |
|---|
| 641 | </p> |
|---|
| 642 | </div> |
|---|
| 643 | <hr class="noprint"> |
|---|
| 644 | <div id="rfc.toc"> |
|---|
| 645 | <h2 class="np"><a href="#rfc.toc">Table of Contents</a></h2> |
|---|
| 646 | <ul class="toc"> |
|---|
| 647 | <li><a href="#rfc.section.1">1.</a> <a href="#introduction">Introduction</a><ul> |
|---|
| 648 | <li><a href="#rfc.section.1.1">1.1</a> <a href="#conformance">Conformance and Error Handling</a></li> |
|---|
| 649 | <li><a href="#rfc.section.1.2">1.2</a> <a href="#notation">Syntax Notation</a></li> |
|---|
| 650 | </ul> |
|---|
| 651 | </li> |
|---|
| 652 | <li><a href="#rfc.section.2">2.</a> <a href="#range.units">Range Units</a><ul> |
|---|
| 653 | <li><a href="#rfc.section.2.1">2.1</a> <a href="#byte.ranges">Byte Ranges</a></li> |
|---|
| 654 | <li><a href="#rfc.section.2.2">2.2</a> <a href="#range.units.other">Other Range Units</a></li> |
|---|
| 655 | <li><a href="#rfc.section.2.3">2.3</a> <a href="#header.accept-ranges">Accept-Ranges</a></li> |
|---|
| 656 | </ul> |
|---|
| 657 | </li> |
|---|
| 658 | <li><a href="#rfc.section.3">3.</a> <a href="#range.requests">Range Requests</a><ul> |
|---|
| 659 | <li><a href="#rfc.section.3.1">3.1</a> <a href="#header.range">Range</a></li> |
|---|
| 660 | <li><a href="#rfc.section.3.2">3.2</a> <a href="#header.if-range">If-Range</a></li> |
|---|
| 661 | </ul> |
|---|
| 662 | </li> |
|---|
| 663 | <li><a href="#rfc.section.4">4.</a> <a href="#range.response">Responses to a Range Request</a><ul> |
|---|
| 664 | <li><a href="#rfc.section.4.1">4.1</a> <a href="#status.206">206 Partial Content</a></li> |
|---|
| 665 | <li><a href="#rfc.section.4.2">4.2</a> <a href="#header.content-range">Content-Range</a></li> |
|---|
| 666 | <li><a href="#rfc.section.4.3">4.3</a> <a href="#combining.byte.ranges">Combining Ranges</a></li> |
|---|
| 667 | <li><a href="#rfc.section.4.4">4.4</a> <a href="#status.416">416 Range Not Satisfiable</a></li> |
|---|
| 668 | </ul> |
|---|
| 669 | </li> |
|---|
| 670 | <li><a href="#rfc.section.5">5.</a> <a href="#IANA.considerations">IANA Considerations</a><ul> |
|---|
| 671 | <li><a href="#rfc.section.5.1">5.1</a> <a href="#range.unit.registry">Range Unit Registry</a><ul> |
|---|
| 672 | <li><a href="#rfc.section.5.1.1">5.1.1</a> <a href="#range.unit.registry.procedure">Procedure</a></li> |
|---|
| 673 | <li><a href="#rfc.section.5.1.2">5.1.2</a> <a href="#range.unit.registration">Registrations</a></li> |
|---|
| 674 | </ul> |
|---|
| 675 | </li> |
|---|
| 676 | <li><a href="#rfc.section.5.2">5.2</a> <a href="#status.code.registration">Status Code Registration</a></li> |
|---|
| 677 | <li><a href="#rfc.section.5.3">5.3</a> <a href="#header.field.registration">Header Field Registration</a></li> |
|---|
| 678 | <li><a href="#rfc.section.5.4">5.4</a> <a href="#internet.media.type.http">Internet Media Type Registration</a><ul> |
|---|
| 679 | <li><a href="#rfc.section.5.4.1">5.4.1</a> <a href="#internet.media.type.multipart.byteranges.reg">Internet Media Type multipart/byteranges</a></li> |
|---|
| 680 | </ul> |
|---|
| 681 | </li> |
|---|
| 682 | </ul> |
|---|
| 683 | </li> |
|---|
| 684 | <li><a href="#rfc.section.6">6.</a> <a href="#security.considerations">Security Considerations</a><ul> |
|---|
| 685 | <li><a href="#rfc.section.6.1">6.1</a> <a href="#overlapping.ranges">Denial-of-Service Attacks Using Range</a></li> |
|---|
| 686 | </ul> |
|---|
| 687 | </li> |
|---|
| 688 | <li><a href="#rfc.section.7">7.</a> <a href="#acks">Acknowledgments</a></li> |
|---|
| 689 | <li><a href="#rfc.section.8">8.</a> <a href="#rfc.references">References</a><ul> |
|---|
| 690 | <li><a href="#rfc.section.8.1">8.1</a> <a href="#rfc.references.1">Normative References</a></li> |
|---|
| 691 | <li><a href="#rfc.section.8.2">8.2</a> <a href="#rfc.references.2">Informative References</a></li> |
|---|
| 692 | </ul> |
|---|
| 693 | </li> |
|---|
| 694 | <li><a href="#rfc.section.A">A.</a> <a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></li> |
|---|
| 695 | <li><a href="#rfc.section.B">B.</a> <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> |
|---|
| 696 | <li><a href="#rfc.section.C">C.</a> <a href="#imported.abnf">Imported ABNF</a></li> |
|---|
| 697 | <li><a href="#rfc.section.D">D.</a> <a href="#collected.abnf">Collected ABNF</a></li> |
|---|
| 698 | <li><a href="#rfc.index">Index</a></li> |
|---|
| 699 | <li><a href="#rfc.authors">Authors' Addresses</a></li> |
|---|
| 700 | </ul> |
|---|
| 701 | </div> |
|---|
| 702 | <div id="introduction"> |
|---|
| 703 | <h2 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> <a href="#introduction">Introduction</a></h2> |
|---|
| 704 | <div id="rfc.section.1.p.1"> |
|---|
| 705 | <p>Hypertext Transfer Protocol (HTTP) clients often encounter interrupted data transfers |
|---|
| 706 | as a result of canceled requests or dropped connections. When a client has stored |
|---|
| 707 | a partial representation, it is desirable to request the remainder of that representation |
|---|
| 708 | in a subsequent request rather than transfer the entire representation. Likewise, |
|---|
| 709 | devices with limited local storage might benefit from being able to request only a |
|---|
| 710 | subset of a larger representation, such as a single page of a very large document, |
|---|
| 711 | or the dimensions of an embedded image. |
|---|
| 712 | </p> |
|---|
| 713 | </div> |
|---|
| 714 | <div id="rfc.section.1.p.2"> |
|---|
| 715 | <p>This document defines HTTP/1.1 range requests, partial responses, and the multipart/byteranges |
|---|
| 716 | media type. Range requests are an <em class="bcp14">OPTIONAL</em> feature of HTTP, designed so that recipients not implementing this feature (or not |
|---|
| 717 | supporting it for the target resource) can respond as if it is a normal GET request |
|---|
| 718 | without impacting interoperability. Partial responses are indicated by a distinct |
|---|
| 719 | status code to not be mistaken for full responses by caches that might not implement |
|---|
| 720 | the feature. |
|---|
| 721 | </p> |
|---|
| 722 | </div> |
|---|
| 723 | <div id="rfc.section.1.p.3"> |
|---|
| 724 | <p>Although the range request mechanism is designed to allow for extensible range types, |
|---|
| 725 | this specification only defines requests for byte ranges. |
|---|
| 726 | </p> |
|---|
| 727 | </div> |
|---|
| 728 | <div id="conformance"> |
|---|
| 729 | <h3 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a> <a href="#conformance">Conformance and Error Handling</a></h3> |
|---|
| 730 | <div id="rfc.section.1.1.p.1"> |
|---|
| 731 | <p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD |
|---|
| 732 | NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted |
|---|
| 733 | 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>. |
|---|
| 734 | </p> |
|---|
| 735 | </div> |
|---|
| 736 | <div id="rfc.section.1.1.p.2"> |
|---|
| 737 | <p>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="#RFC7230" id="rfc.xref.RFC7230.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>. |
|---|
| 738 | </p> |
|---|
| 739 | </div> |
|---|
| 740 | </div> |
|---|
| 741 | <div id="notation"> |
|---|
| 742 | <h3 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a> <a href="#notation">Syntax Notation</a></h3> |
|---|
| 743 | <div id="rfc.section.1.2.p.1"> |
|---|
| 744 | <p>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 a list extension, defined in <a href="p1-messaging.html#abnf.extension" title="ABNF List Extension: #rule">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, that allows for compact definition of comma-separated lists using a '#' operator |
|---|
| 745 | (similar to how the '*' operator indicates repetition). <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 grammar with all list operators expanded to standard ABNF notation. |
|---|
| 746 | </p> |
|---|
| 747 | </div> |
|---|
| 748 | </div> |
|---|
| 749 | </div> |
|---|
| 750 | <div id="range.units"> |
|---|
| 751 | <h2 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a href="#range.units">Range Units</a></h2> |
|---|
| 752 | <div id="rfc.section.2.p.1"> |
|---|
| 753 | <p>A representation can be partitioned into subranges according to various structural |
|---|
| 754 | units, depending on the structure inherent in the representation's media type. This |
|---|
| 755 | "<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, |
|---|
| 756 | 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. |
|---|
| 757 | </p> |
|---|
| 758 | </div> |
|---|
| 759 | <div id="rfc.figure.u.1"><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> |
|---|
| 760 | </pre></div> |
|---|
| 761 | <div id="byte.ranges"> |
|---|
| 762 | <h3 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> <a href="#byte.ranges">Byte Ranges</a></h3> |
|---|
| 763 | <div id="rfc.section.2.1.p.1"> |
|---|
| 764 | <p>Since representation data is transferred in payloads as a sequence of octets, a byte |
|---|
| 765 | range is a meaningful substructure for any representation transferable over HTTP (<a href="p2-semantics.html#representations" title="Representations">Section 3</a> of <a href="#RFC7231" id="rfc.xref.RFC7231.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>). The "bytes" range unit is defined for expressing subranges of the data's octet |
|---|
| 766 | sequence. |
|---|
| 767 | </p> |
|---|
| 768 | </div> |
|---|
| 769 | <div id="rfc.figure.u.2"><pre class="inline"><span id="rfc.iref.g.4"></span> <a href="#byte.ranges" class="smpl">bytes-unit</a> = "bytes" |
|---|
| 770 | </pre></div> |
|---|
| 771 | <div id="rule.ranges-specifier"> |
|---|
| 772 | <div id="rfc.section.2.1.p.2"> |
|---|
| 773 | <p> A byte-range request can specify a single range of bytes or a set of ranges within |
|---|
| 774 | a single representation. |
|---|
| 775 | </p> |
|---|
| 776 | </div> |
|---|
| 777 | </div> |
|---|
| 778 | <div id="rfc.figure.u.3"><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> |
|---|
| 779 | <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> ) |
|---|
| 780 | <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> ] |
|---|
| 781 | <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a> |
|---|
| 782 | <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a> |
|---|
| 783 | </pre></div> |
|---|
| 784 | <div id="rfc.section.2.1.p.3"> |
|---|
| 785 | <p>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 |
|---|
| 786 | specified are inclusive. Byte offsets start at zero. |
|---|
| 787 | </p> |
|---|
| 788 | </div> |
|---|
| 789 | <div id="rfc.section.2.1.p.4"> |
|---|
| 790 | <p>Examples of <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> values: |
|---|
| 791 | </p> |
|---|
| 792 | <ul> |
|---|
| 793 | <li>The first 500 bytes (byte offsets 0-499, inclusive): <span id="rfc.figure.u.4"><pre class="text"> bytes=0-499 |
|---|
| 794 | </pre></span> |
|---|
| 795 | </li> |
|---|
| 796 | <li>The second 500 bytes (byte offsets 500-999, inclusive): <span id="rfc.figure.u.5"><pre class="text"> bytes=500-999 |
|---|
| 797 | </pre></span> |
|---|
| 798 | </li> |
|---|
| 799 | </ul> |
|---|
| 800 | </div> |
|---|
| 801 | <div id="rfc.section.2.1.p.5"> |
|---|
| 802 | <p>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>. |
|---|
| 803 | </p> |
|---|
| 804 | </div> |
|---|
| 805 | <div id="rfc.section.2.1.p.6"> |
|---|
| 806 | <p>A client can limit the number of bytes requested without knowing the size of the selected |
|---|
| 807 | 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 |
|---|
| 808 | the representation data, the byte range is interpreted as the remainder of the representation |
|---|
| 809 | (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). |
|---|
| 810 | </p> |
|---|
| 811 | </div> |
|---|
| 812 | <div id="rfc.section.2.1.p.7"> |
|---|
| 813 | <p>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>. |
|---|
| 814 | </p> |
|---|
| 815 | </div> |
|---|
| 816 | <div id="rfc.figure.u.6"><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> |
|---|
| 817 | <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a> |
|---|
| 818 | </pre></div> |
|---|
| 819 | <div id="rfc.section.2.1.p.8"> |
|---|
| 820 | <p>If the selected representation is shorter than the specified <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>, the entire representation is used. |
|---|
| 821 | </p> |
|---|
| 822 | </div> |
|---|
| 823 | <div id="rfc.section.2.1.p.9"> |
|---|
| 824 | <p>Additional examples, assuming a representation of length 10000: </p> |
|---|
| 825 | <ul> |
|---|
| 826 | <li>The final 500 bytes (byte offsets 9500-9999, inclusive): <span id="rfc.figure.u.7"><pre class="text"> bytes=-500 |
|---|
| 827 | </pre></span> Or: <span id="rfc.figure.u.8"><pre class="text"> bytes=9500- |
|---|
| 828 | </pre></span> |
|---|
| 829 | </li> |
|---|
| 830 | <li>The first and last bytes only (bytes 0 and 9999): <span id="rfc.figure.u.9"><pre class="text"> bytes=0-0,-1 |
|---|
| 831 | </pre></span> |
|---|
| 832 | </li> |
|---|
| 833 | <li>Other valid (but not canonical) specifications of the second 500 bytes (byte offsets |
|---|
| 834 | 500-999, inclusive): <span id="rfc.figure.u.10"><pre class="text"> bytes=500-600,601-999 |
|---|
| 835 | bytes=500-700,601-999 |
|---|
| 836 | </pre></span> |
|---|
| 837 | </li> |
|---|
| 838 | </ul> |
|---|
| 839 | </div> |
|---|
| 840 | <div id="rfc.section.2.1.p.10"> |
|---|
| 841 | <p>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. |
|---|
| 842 | </p> |
|---|
| 843 | </div> |
|---|
| 844 | <div id="rfc.section.2.1.p.11"> |
|---|
| 845 | <p>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 |
|---|
| 846 | length of a payload, recipients <em class="bcp14">MUST</em> anticipate potentially large decimal numerals and prevent parsing errors due to integer |
|---|
| 847 | conversion overflows. |
|---|
| 848 | </p> |
|---|
| 849 | </div> |
|---|
| 850 | </div> |
|---|
| 851 | <div id="range.units.other"> |
|---|
| 852 | <h3 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a> <a href="#range.units.other">Other Range Units</a></h3> |
|---|
| 853 | <div id="rfc.section.2.2.p.1"> |
|---|
| 854 | <p>Range units are intended to be extensible. New range units ought to be registered |
|---|
| 855 | with IANA, as defined in <a href="#range.unit.registry" title="Range Unit Registry">Section 5.1</a>. |
|---|
| 856 | </p> |
|---|
| 857 | </div> |
|---|
| 858 | <div id="rfc.figure.u.11"><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> |
|---|
| 859 | </pre></div> |
|---|
| 860 | </div> |
|---|
| 861 | <div id="header.accept-ranges"> |
|---|
| 862 | <h3 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a> <a href="#header.accept-ranges">Accept-Ranges</a></h3> |
|---|
| 863 | <div id="rfc.section.2.3.p.1"> |
|---|
| 864 | <p>The "Accept-Ranges" header field allows a server to indicate that it supports range |
|---|
| 865 | requests for the target resource. |
|---|
| 866 | </p> |
|---|
| 867 | </div> |
|---|
| 868 | <div id="rfc.figure.u.12"><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> |
|---|
| 869 | <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = 1#<a href="#range.units" class="smpl">range-unit</a> / "none" |
|---|
| 870 | </pre></div> |
|---|
| 871 | <div id="rfc.section.2.3.p.2"> |
|---|
| 872 | <p>An origin server that supports byte-range requests for a given target resource <em class="bcp14">MAY</em> send |
|---|
| 873 | </p> |
|---|
| 874 | </div> |
|---|
| 875 | <div id="rfc.figure.u.13"><pre class="text"> Accept-Ranges: bytes |
|---|
| 876 | </pre></div> |
|---|
| 877 | <div id="rfc.section.2.3.p.3"> |
|---|
| 878 | <p>to indicate what range units are supported. A client <em class="bcp14">MAY</em> generate range requests without having received this header field for the resource |
|---|
| 879 | involved. Range units are defined in <a href="#range.units" title="Range Units">Section 2</a>. |
|---|
| 880 | </p> |
|---|
| 881 | </div> |
|---|
| 882 | <div id="rfc.section.2.3.p.4"> |
|---|
| 883 | <p>A server that does not support any kind of range request for the target resource <em class="bcp14">MAY</em> send |
|---|
| 884 | </p> |
|---|
| 885 | </div> |
|---|
| 886 | <div id="rfc.figure.u.14"><pre class="text"> Accept-Ranges: none |
|---|
| 887 | </pre></div> |
|---|
| 888 | <div id="rfc.section.2.3.p.5"> |
|---|
| 889 | <p>to advise the client not to attempt a range request.</p> |
|---|
| 890 | </div> |
|---|
| 891 | </div> |
|---|
| 892 | </div> |
|---|
| 893 | <div id="range.requests"> |
|---|
| 894 | <h2 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a href="#range.requests">Range Requests</a></h2> |
|---|
| 895 | <div id="header.range"> |
|---|
| 896 | <h3 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a> <a href="#header.range">Range</a></h3> |
|---|
| 897 | <div id="rfc.section.3.1.p.1"> |
|---|
| 898 | <p>The "Range" header field on a GET request modifies the method semantics to request |
|---|
| 899 | transfer of only one or more subranges of the selected representation data, rather |
|---|
| 900 | than the entire selected representation data. |
|---|
| 901 | </p> |
|---|
| 902 | </div> |
|---|
| 903 | <div id="rfc.figure.u.15"><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> |
|---|
| 904 | <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> |
|---|
| 905 | <a href="#header.range" class="smpl">other-range-set</a> = 1*<a href="#imported.abnf" class="smpl">VCHAR</a> |
|---|
| 906 | </pre></div> |
|---|
| 907 | <div id="rfc.section.3.1.p.2"> |
|---|
| 908 | <p>A server <em class="bcp14">MAY</em> ignore the Range header field. However, origin servers and intermediate caches ought |
|---|
| 909 | to support byte ranges when possible, since Range supports efficient recovery from |
|---|
| 910 | partially failed transfers and partial retrieval of large representations. A server <em class="bcp14">MUST</em> ignore a Range header field received with a request method other than GET. |
|---|
| 911 | </p> |
|---|
| 912 | </div> |
|---|
| 913 | <div id="rfc.section.3.1.p.3"> |
|---|
| 914 | <p>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> discard a Range header field that contains a range unit it does not understand. |
|---|
| 915 | </p> |
|---|
| 916 | </div> |
|---|
| 917 | <div id="rfc.section.3.1.p.4"> |
|---|
| 918 | <p>A server that supports range requests <em class="bcp14">MAY</em> 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 |
|---|
| 919 | ranges that are not listed in ascending order, since both are indications of either |
|---|
| 920 | 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 |
|---|
| 921 | than a single range that encompasses the same data. |
|---|
| 922 | </p> |
|---|
| 923 | </div> |
|---|
| 924 | <div id="rfc.section.3.1.p.5"> |
|---|
| 925 | <p>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 |
|---|
| 926 | in a complete representation) unless there is a specific need to request a later part |
|---|
| 927 | earlier. For example, a user agent processing a large representation with an internal |
|---|
| 928 | catalog of parts might need to request later parts first, particularly if the representation |
|---|
| 929 | consists of pages stored in reverse order and the user agent wishes to transfer one |
|---|
| 930 | page at a time. |
|---|
| 931 | </p> |
|---|
| 932 | </div> |
|---|
| 933 | <div id="rfc.section.3.1.p.6"> |
|---|
| 934 | <p>The Range header field is evaluated after evaluating the precondition header fields |
|---|
| 935 | defined in <a href="#RFC7232" id="rfc.xref.RFC7232.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>, and only if the result in absence of the Range header field would be 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 |
|---|
| 936 | a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response. |
|---|
| 937 | </p> |
|---|
| 938 | </div> |
|---|
| 939 | <div id="rfc.section.3.1.p.7"> |
|---|
| 940 | <p>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. |
|---|
| 941 | </p> |
|---|
| 942 | </div> |
|---|
| 943 | <div id="rfc.section.3.1.p.8"> |
|---|
| 944 | <p>If all of the preconditions are true, the server supports the Range header field for |
|---|
| 945 | the target resource, and the specified range(s) are valid and satisfiable (as defined |
|---|
| 946 | 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 |
|---|
| 947 | to the satisfiable ranges requested, as defined in <a href="#range.response" title="Responses to a Range Request">Section 4</a>. |
|---|
| 948 | </p> |
|---|
| 949 | </div> |
|---|
| 950 | <div id="rfc.section.3.1.p.9"> |
|---|
| 951 | <p>If all of the preconditions are true, the server supports the Range header field for |
|---|
| 952 | the target resource, and the specified range(s) are invalid or unsatisfiable, the |
|---|
| 953 | server <em class="bcp14">SHOULD</em> send a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response. |
|---|
| 954 | </p> |
|---|
| 955 | </div> |
|---|
| 956 | </div> |
|---|
| 957 | <div id="header.if-range"> |
|---|
| 958 | <h3 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a href="#header.if-range">If-Range</a></h3> |
|---|
| 959 | <div id="rfc.section.3.2.p.1"> |
|---|
| 960 | <p>If a client has a partial copy of a representation and wishes to have an up-to-date |
|---|
| 961 | copy of the entire representation, it 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 precondition fails because the representation has been modified, |
|---|
| 962 | the client would then have to make a second request to obtain the entire current representation. |
|---|
| 963 | </p> |
|---|
| 964 | </div> |
|---|
| 965 | <div id="rfc.section.3.2.p.2"> |
|---|
| 966 | <p>The "If-Range" header field allows a client to "short-circuit" the second request. |
|---|
| 967 | Informally, its meaning is as follows: if the representation is unchanged, send me |
|---|
| 968 | the part(s) that I am requesting in Range; otherwise, send me the entire representation. |
|---|
| 969 | </p> |
|---|
| 970 | </div> |
|---|
| 971 | <div id="rfc.figure.u.16"><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> |
|---|
| 972 | </pre></div> |
|---|
| 973 | <div id="rfc.section.3.2.p.3"> |
|---|
| 974 | <p>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 |
|---|
| 975 | not support Range requests. |
|---|
| 976 | </p> |
|---|
| 977 | </div> |
|---|
| 978 | <div id="rfc.section.3.2.p.4"> |
|---|
| 979 | <p>A client <em class="bcp14">MUST NOT</em> generate an If-Range header field containing an entity-tag that is marked as weak. |
|---|
| 980 | A client <em class="bcp14">MUST NOT</em> generate an If-Range header field containing an <a href="#imported.abnf" class="smpl">HTTP-date</a> unless the client has no entity-tag for the corresponding representation and the date |
|---|
| 981 | is a strong validator in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>. |
|---|
| 982 | </p> |
|---|
| 983 | </div> |
|---|
| 984 | <div id="rfc.section.3.2.p.5"> |
|---|
| 985 | <p>A server that evaluates an If-Range precondition <em class="bcp14">MUST</em> use the strong comparison function when comparing entity-tags (<a href="p4-conditional.html#entity.tag.comparison" title="Comparison">Section 2.3.2</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>) and <em class="bcp14">MUST</em> evaluate the condition as false if an <a href="#imported.abnf" class="smpl">HTTP-date</a> validator is provided that is not a strong validator in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>. A valid <a href="#imported.abnf" class="smpl">entity-tag</a> can be distinguished from a valid <a href="#imported.abnf" class="smpl">HTTP-date</a> by examining the first two characters for a DQUOTE. |
|---|
| 986 | </p> |
|---|
| 987 | </div> |
|---|
| 988 | <div id="rfc.section.3.2.p.6"> |
|---|
| 989 | <p>If the validator given in the If-Range header field matches the current validator |
|---|
| 990 | for the selected representation of the target resource, then the server <em class="bcp14">SHOULD</em> process the <a href="#header.range" class="smpl">Range</a> header field as requested. If the validator does not match, the server <em class="bcp14">MUST</em> ignore the <a href="#header.range" class="smpl">Range</a> header field. Note that this comparison by exact match, including when the validator |
|---|
| 991 | is an <a href="#imported.abnf" class="smpl">HTTP-date</a>, differs from the "earlier than or equal to" comparison used when evaluating an <a href="p4-conditional.html#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> conditional. |
|---|
| 992 | </p> |
|---|
| 993 | </div> |
|---|
| 994 | </div> |
|---|
| 995 | </div> |
|---|
| 996 | <div id="range.response"> |
|---|
| 997 | <h2 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a href="#range.response">Responses to a Range Request</a></h2> |
|---|
| 998 | <div id="status.206"> |
|---|
| 999 | <h3 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a> <a href="#status.206">206 Partial Content</a></h3> |
|---|
| 1000 | <div id="rfc.section.4.1.p.1"> |
|---|
| 1001 | <p>The <dfn>206 (Partial Content)</dfn> status code indicates that the server is successfully fulfilling a range request for |
|---|
| 1002 | the target resource by transferring one or more parts of the selected representation |
|---|
| 1003 | 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>). |
|---|
| 1004 | </p> |
|---|
| 1005 | </div> |
|---|
| 1006 | <div id="rfc.section.4.1.p.2" class="avoidbreakafter"> |
|---|
| 1007 | <p>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 |
|---|
| 1008 | a payload consisting of the range. For example: |
|---|
| 1009 | </p> |
|---|
| 1010 | </div> |
|---|
| 1011 | <div id="rfc.figure.u.17"><pre class="text">HTTP/1.1 206 Partial Content |
|---|
| 1012 | Date: Wed, 15 Nov 1995 06:25:24 GMT |
|---|
| 1013 | Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT |
|---|
| 1014 | Content-Range: bytes 21010-47021/47022 |
|---|
| 1015 | Content-Length: 26012 |
|---|
| 1016 | Content-Type: image/gif |
|---|
| 1017 | |
|---|
| 1018 | ... 26012 bytes of partial image data ... |
|---|
| 1019 | </pre></div> |
|---|
| 1020 | <div id="rfc.section.4.1.p.3"> |
|---|
| 1021 | <p>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 |
|---|
| 1022 | parameter. To avoid confusion with single-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 section of a multiple part response (this field will |
|---|
| 1023 | be sent in each part instead). |
|---|
| 1024 | </p> |
|---|
| 1025 | </div> |
|---|
| 1026 | <div id="rfc.section.4.1.p.4" class="avoidbreakafter"> |
|---|
| 1027 | <p>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 |
|---|
| 1028 | 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: |
|---|
| 1029 | </p> |
|---|
| 1030 | </div> |
|---|
| 1031 | <div id="rfc.figure.u.18"><pre class="text">HTTP/1.1 206 Partial Content |
|---|
| 1032 | Date: Wed, 15 Nov 1995 06:25:24 GMT |
|---|
| 1033 | Last-Modified: Wed, 15 Nov 1995 04:58:08 GMT |
|---|
| 1034 | Content-Length: 1741 |
|---|
| 1035 | Content-Type: multipart/byteranges; boundary=THIS_STRING_SEPARATES |
|---|
| 1036 | |
|---|
| 1037 | --THIS_STRING_SEPARATES |
|---|
| 1038 | Content-Type: application/pdf |
|---|
| 1039 | Content-Range: bytes 500-999/8000 |
|---|
| 1040 | |
|---|
| 1041 | ...the first range... |
|---|
| 1042 | --THIS_STRING_SEPARATES |
|---|
| 1043 | Content-Type: application/pdf |
|---|
| 1044 | Content-Range: bytes 7000-7999/8000 |
|---|
| 1045 | |
|---|
| 1046 | ...the second range |
|---|
| 1047 | --THIS_STRING_SEPARATES-- |
|---|
| 1048 | </pre></div> |
|---|
| 1049 | <div id="rfc.section.4.1.p.5"> |
|---|
| 1050 | <p>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 |
|---|
| 1051 | than the overhead of sending multiple parts, regardless of the order in which the |
|---|
| 1052 | 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 |
|---|
| 1053 | is around 80 bytes, depending on the selected representation's media type and the |
|---|
| 1054 | chosen boundary parameter length, it can be less efficient to transfer many small |
|---|
| 1055 | disjoint parts than it is to transfer the entire selected representation. |
|---|
| 1056 | </p> |
|---|
| 1057 | </div> |
|---|
| 1058 | <div id="rfc.section.4.1.p.6"> |
|---|
| 1059 | <p>A server <em class="bcp14">MUST NOT</em> generate a multipart response to a request for a single range, since a client that |
|---|
| 1060 | does not request multiple parts might not support multipart responses. However, a |
|---|
| 1061 | server <em class="bcp14">MAY</em> generate a multipart/byteranges payload with only a single body part if multiple ranges |
|---|
| 1062 | were requested and only one range was found to be satisfiable or only one range remained |
|---|
| 1063 | after coalescing. A client that cannot process a multipart/byteranges response <em class="bcp14">MUST NOT</em> generate a request that asks for multiple ranges. |
|---|
| 1064 | </p> |
|---|
| 1065 | </div> |
|---|
| 1066 | <div id="rfc.section.4.1.p.7"> |
|---|
| 1067 | <p>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 |
|---|
| 1068 | the received <a href="#header.range" class="smpl">Range</a> header field, excluding those ranges that were deemed unsatisfiable or that were coalesced |
|---|
| 1069 | into other ranges. A client that 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 |
|---|
| 1070 | in that body part; a client cannot rely on receiving the same ranges that it requested, |
|---|
| 1071 | nor the same order that it requested. |
|---|
| 1072 | </p> |
|---|
| 1073 | </div> |
|---|
| 1074 | <div id="rfc.section.4.1.p.8"> |
|---|
| 1075 | <p>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 |
|---|
| 1076 | 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>. |
|---|
| 1077 | </p> |
|---|
| 1078 | </div> |
|---|
| 1079 | <div id="rfc.section.4.1.p.9"> |
|---|
| 1080 | <p>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 |
|---|
| 1081 | client is understood to already have a prior response containing those header fields. |
|---|
| 1082 | 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. |
|---|
| 1083 | </p> |
|---|
| 1084 | </div> |
|---|
| 1085 | <div id="rfc.section.4.1.p.10"> |
|---|
| 1086 | <p>A 206 response is cacheable by default; i.e., unless otherwise indicated by explicit |
|---|
| 1087 | cache controls (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.2.2</a> of <a href="#RFC7234" id="rfc.xref.RFC7234.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[RFC7234]</cite></a>). |
|---|
| 1088 | </p> |
|---|
| 1089 | </div> |
|---|
| 1090 | </div> |
|---|
| 1091 | <div id="header.content-range"> |
|---|
| 1092 | <h3 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a> <a href="#header.content-range">Content-Range</a></h3> |
|---|
| 1093 | <div id="rfc.section.4.2.p.1"> |
|---|
| 1094 | <p>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 |
|---|
| 1095 | the message payload, sent in each part of a multipart 206 response to indicate the |
|---|
| 1096 | 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. |
|---|
| 1097 | </p> |
|---|
| 1098 | </div> |
|---|
| 1099 | <div id="rfc.figure.u.19"><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> |
|---|
| 1100 | / <a href="#header.content-range" class="smpl">other-content-range</a> |
|---|
| 1101 | |
|---|
| 1102 | <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> |
|---|
| 1103 | ( <a href="#header.content-range" class="smpl">byte-range-resp</a> / <a href="#header.content-range" class="smpl">unsatisfied-range</a> ) |
|---|
| 1104 | |
|---|
| 1105 | <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> / "*" ) |
|---|
| 1106 | <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> |
|---|
| 1107 | <a href="#header.content-range" class="smpl">unsatisfied-range</a> = "*/" <a href="#header.content-range" class="smpl">complete-length</a> |
|---|
| 1108 | |
|---|
| 1109 | <a href="#header.content-range" class="smpl">complete-length</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a> |
|---|
| 1110 | |
|---|
| 1111 | <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> |
|---|
| 1112 | <a href="#header.content-range" class="smpl">other-range-resp</a> = *<a href="#imported.abnf" class="smpl">CHAR</a> |
|---|
| 1113 | </pre></div> |
|---|
| 1114 | <div id="rfc.section.4.2.p.2"> |
|---|
| 1115 | <p>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 |
|---|
| 1116 | message <em class="bcp14">SHOULD</em> forward it downstream. |
|---|
| 1117 | </p> |
|---|
| 1118 | </div> |
|---|
| 1119 | <div id="rfc.section.4.2.p.3"> |
|---|
| 1120 | <p>For byte ranges, a sender <em class="bcp14">SHOULD</em> indicate the complete length of the representation from which the range has been extracted, |
|---|
| 1121 | unless the complete length is unknown or difficult to determine. An asterisk character |
|---|
| 1122 | ("*") in place of the complete-length indicates that the representation length was |
|---|
| 1123 | unknown when the header field was generated. |
|---|
| 1124 | </p> |
|---|
| 1125 | </div> |
|---|
| 1126 | <div id="rfc.section.4.2.p.4" class="avoidbreakafter"> |
|---|
| 1127 | <p>The following example illustrates when the complete length of the selected representation |
|---|
| 1128 | is known by the sender to be 1234 bytes: |
|---|
| 1129 | </p> |
|---|
| 1130 | </div> |
|---|
| 1131 | <div id="rfc.figure.u.20"><pre class="text"> Content-Range: bytes 42-1233/1234 |
|---|
| 1132 | </pre></div> |
|---|
| 1133 | <div id="rfc.section.4.2.p.5" class="avoidbreakafter"> |
|---|
| 1134 | <p>and this second example illustrates when the complete length is unknown:</p> |
|---|
| 1135 | </div> |
|---|
| 1136 | <div id="rfc.figure.u.21"><pre class="text"> Content-Range: bytes 42-1233/* |
|---|
| 1137 | </pre></div> |
|---|
| 1138 | <div id="rfc.section.4.2.p.6"> |
|---|
| 1139 | <p>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. |
|---|
| 1140 | </p> |
|---|
| 1141 | </div> |
|---|
| 1142 | <div id="rfc.section.4.2.p.7" class="avoidbreakafter"> |
|---|
| 1143 | <p>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: |
|---|
| 1144 | </p> |
|---|
| 1145 | </div> |
|---|
| 1146 | <div id="rfc.figure.u.22"><pre class="text"> Content-Range: bytes */1234 |
|---|
| 1147 | </pre></div> |
|---|
| 1148 | <div id="rfc.section.4.2.p.8"> |
|---|
| 1149 | <p>The complete-length in a 416 response indicates the current length of the selected |
|---|
| 1150 | representation. |
|---|
| 1151 | </p> |
|---|
| 1152 | </div> |
|---|
| 1153 | <div id="rfc.section.4.2.p.9"> |
|---|
| 1154 | <p>The Content-Range header field has no meaning for status codes that do not explicitly |
|---|
| 1155 | describe its semantic. For this specification, 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. |
|---|
| 1156 | </p> |
|---|
| 1157 | </div> |
|---|
| 1158 | <div id="rfc.section.4.2.p.10"> |
|---|
| 1159 | <p>The following are examples of Content-Range values in which the selected representation |
|---|
| 1160 | contains a total of 1234 bytes: |
|---|
| 1161 | </p> |
|---|
| 1162 | <ul> |
|---|
| 1163 | <li>The first 500 bytes: <span id="rfc.figure.u.23"><pre class="text"> Content-Range: bytes 0-499/1234 |
|---|
| 1164 | </pre></span> |
|---|
| 1165 | </li> |
|---|
| 1166 | <li>The second 500 bytes: <span id="rfc.figure.u.24"><pre class="text"> Content-Range: bytes 500-999/1234 |
|---|
| 1167 | </pre></span> |
|---|
| 1168 | </li> |
|---|
| 1169 | <li>All except for the first 500 bytes: <span id="rfc.figure.u.25"><pre class="text"> Content-Range: bytes 500-1233/1234 |
|---|
| 1170 | </pre></span> |
|---|
| 1171 | </li> |
|---|
| 1172 | <li>The last 500 bytes: <span id="rfc.figure.u.26"><pre class="text"> Content-Range: bytes 734-1233/1234 |
|---|
| 1173 | </pre></span> |
|---|
| 1174 | </li> |
|---|
| 1175 | </ul> |
|---|
| 1176 | </div> |
|---|
| 1177 | </div> |
|---|
| 1178 | <div id="combining.byte.ranges"> |
|---|
| 1179 | <h3 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a> <a href="#combining.byte.ranges">Combining Ranges</a></h3> |
|---|
| 1180 | <div id="rfc.section.4.3.p.1"> |
|---|
| 1181 | <p>A response might transfer only a subrange of a representation if the connection closed |
|---|
| 1182 | prematurely or if the request used one or more Range specifications. After several |
|---|
| 1183 | such transfers, a client might have received several ranges of the same representation. |
|---|
| 1184 | These ranges can only be safely combined if they all have in common the same strong |
|---|
| 1185 | validator (<a href="p4-conditional.html#weak.and.strong.validators" title="Weak versus Strong">Section 2.1</a> of <a href="#RFC7232" id="rfc.xref.RFC7232.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>). |
|---|
| 1186 | </p> |
|---|
| 1187 | </div> |
|---|
| 1188 | <div id="rfc.section.4.3.p.2"> |
|---|
| 1189 | <p>A client that has received multiple partial responses to GET requests on a target |
|---|
| 1190 | resource <em class="bcp14">MAY</em> combine those responses into a larger continuous range if they share the same strong |
|---|
| 1191 | validator. |
|---|
| 1192 | </p> |
|---|
| 1193 | </div> |
|---|
| 1194 | <div id="rfc.section.4.3.p.3"> |
|---|
| 1195 | <p>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 |
|---|
| 1196 | and replace those of the matching stored responses. |
|---|
| 1197 | </p> |
|---|
| 1198 | </div> |
|---|
| 1199 | <div id="rfc.section.4.3.p.4"> |
|---|
| 1200 | <p>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 |
|---|
| 1201 | header fields. If all of the matching stored responses are 206 responses, then the |
|---|
| 1202 | stored response with the most recent header fields is used as the source of header |
|---|
| 1203 | 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. |
|---|
| 1204 | </p> |
|---|
| 1205 | </div> |
|---|
| 1206 | <div id="rfc.section.4.3.p.5"> |
|---|
| 1207 | <p>The combined response message body consists of the union of partial content ranges |
|---|
| 1208 | in the new response and each of the selected responses. If the union consists of the |
|---|
| 1209 | entire range of the representation, then the client <em class="bcp14">MUST</em> process 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> process 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. |
|---|
| 1210 | </p> |
|---|
| 1211 | </div> |
|---|
| 1212 | </div> |
|---|
| 1213 | <div id="status.416"> |
|---|
| 1214 | <h3 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a> <a href="#status.416">416 Range Not Satisfiable</a></h3> |
|---|
| 1215 | <div id="rfc.section.4.4.p.1"> |
|---|
| 1216 | <p>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 |
|---|
| 1217 | has been rejected due to invalid ranges or an excessive request of small or overlapping |
|---|
| 1218 | ranges. |
|---|
| 1219 | </p> |
|---|
| 1220 | </div> |
|---|
| 1221 | <div id="rfc.section.4.4.p.2"> |
|---|
| 1222 | <p>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 |
|---|
| 1223 | status code is generated in response 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>). |
|---|
| 1224 | </p> |
|---|
| 1225 | </div> |
|---|
| 1226 | <div id="rfc.figure.u.27"> |
|---|
| 1227 | <p>For example:</p><pre class="text">HTTP/1.1 416 Range Not Satisfiable |
|---|
| 1228 | Date: Fri, 20 Jan 2012 15:41:54 GMT |
|---|
| 1229 | Content-Range: bytes */47022 |
|---|
| 1230 | </pre></div> |
|---|
| 1231 | <div class="note"> |
|---|
| 1232 | <div id="rfc.section.4.4.p.3"> |
|---|
| 1233 | <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 |
|---|
| 1234 | in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response. That is partly because most clients are prepared to receive 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 |
|---|
| 1235 | stop making an invalid partial request until they have received a complete representation. |
|---|
| 1236 | 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. |
|---|
| 1237 | </p> |
|---|
| 1238 | </div> |
|---|
| 1239 | </div> |
|---|
| 1240 | </div> |
|---|
| 1241 | </div> |
|---|
| 1242 | <div id="IANA.considerations"> |
|---|
| 1243 | <h2 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a href="#IANA.considerations">IANA Considerations</a></h2> |
|---|
| 1244 | <div id="range.unit.registry"> |
|---|
| 1245 | <h3 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a> <a href="#range.unit.registry">Range Unit Registry</a></h3> |
|---|
| 1246 | <div id="rfc.section.5.1.p.1"> |
|---|
| 1247 | <p>The "HTTP Range Unit Registry" defines the namespace for the range unit names and |
|---|
| 1248 | refers to their corresponding specifications. The registry has been created and is |
|---|
| 1249 | now maintained at <<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>>. |
|---|
| 1250 | </p> |
|---|
| 1251 | </div> |
|---|
| 1252 | <div id="range.unit.registry.procedure"> |
|---|
| 1253 | <h4 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a> <a href="#range.unit.registry.procedure">Procedure</a></h4> |
|---|
| 1254 | <div id="rfc.section.5.1.1.p.1"> |
|---|
| 1255 | <p>Registration of an HTTP Range Unit <em class="bcp14">MUST</em> include the following fields: |
|---|
| 1256 | </p> |
|---|
| 1257 | <ul> |
|---|
| 1258 | <li>Name</li> |
|---|
| 1259 | <li>Description</li> |
|---|
| 1260 | <li>Pointer to specification text</li> |
|---|
| 1261 | </ul> |
|---|
| 1262 | </div> |
|---|
| 1263 | <div id="rfc.section.5.1.1.p.2"> |
|---|
| 1264 | <p>Values to be added to this namespace 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="https://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). |
|---|
| 1265 | </p> |
|---|
| 1266 | </div> |
|---|
| 1267 | </div> |
|---|
| 1268 | <div id="range.unit.registration"> |
|---|
| 1269 | <h4 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a> <a href="#range.unit.registration">Registrations</a></h4> |
|---|
| 1270 | <div id="rfc.section.5.1.2.p.1" class="avoidbreakafter"> |
|---|
| 1271 | <p>The initial range unit registry contains the registrations below:</p> |
|---|
| 1272 | </div> |
|---|
| 1273 | <div id="rfc.table.1"> |
|---|
| 1274 | <div id="iana.range.units.table"></div> |
|---|
| 1275 | <table class="tt full tleft" cellpadding="3" cellspacing="0"> |
|---|
| 1276 | <thead> |
|---|
| 1277 | <tr> |
|---|
| 1278 | <th>Range Unit Name</th> |
|---|
| 1279 | <th>Description</th> |
|---|
| 1280 | <th>Reference</th> |
|---|
| 1281 | </tr> |
|---|
| 1282 | </thead> |
|---|
| 1283 | <tbody> |
|---|
| 1284 | <tr> |
|---|
| 1285 | <td class="left">bytes</td> |
|---|
| 1286 | <td class="left">a range of octets</td> |
|---|
| 1287 | <td class="left"><a href="#byte.ranges" title="Byte Ranges">Section 2.1</a></td> |
|---|
| 1288 | </tr> |
|---|
| 1289 | <tr> |
|---|
| 1290 | <td class="left">none</td> |
|---|
| 1291 | <td class="left">reserved as keyword, indicating no ranges are supported</td> |
|---|
| 1292 | <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.2" title="Accept-Ranges">Section 2.3</a></td> |
|---|
| 1293 | </tr> |
|---|
| 1294 | </tbody> |
|---|
| 1295 | </table> |
|---|
| 1296 | </div> |
|---|
| 1297 | <div id="rfc.section.5.1.2.p.2"> |
|---|
| 1298 | <p>The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> |
|---|
| 1299 | </div> |
|---|
| 1300 | </div> |
|---|
| 1301 | </div> |
|---|
| 1302 | <div id="status.code.registration"> |
|---|
| 1303 | <h3 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a> <a href="#status.code.registration">Status Code Registration</a></h3> |
|---|
| 1304 | <div id="rfc.section.5.2.p.1" class="avoidbreakafter"> |
|---|
| 1305 | <p>The "Hypertext Transfer Protocol (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>> has been updated to include the registrations below: |
|---|
| 1306 | </p> |
|---|
| 1307 | </div> |
|---|
| 1308 | <div id="rfc.table.2"> |
|---|
| 1309 | <div id="iana.status.code.registration.table"></div> |
|---|
| 1310 | <table class="tt full tleft" cellpadding="3" cellspacing="0"> |
|---|
| 1311 | <thead> |
|---|
| 1312 | <tr> |
|---|
| 1313 | <th>Value</th> |
|---|
| 1314 | <th>Description</th> |
|---|
| 1315 | <th>Reference</th> |
|---|
| 1316 | </tr> |
|---|
| 1317 | </thead> |
|---|
| 1318 | <tbody> |
|---|
| 1319 | <tr> |
|---|
| 1320 | <td class="left">206</td> |
|---|
| 1321 | <td class="left">Partial Content</td> |
|---|
| 1322 | <td class="left"><a href="#status.206" id="rfc.xref.status.206.1" title="206 Partial Content">Section 4.1</a> |
|---|
| 1323 | </td> |
|---|
| 1324 | </tr> |
|---|
| 1325 | <tr> |
|---|
| 1326 | <td class="left">416</td> |
|---|
| 1327 | <td class="left">Range Not Satisfiable</td> |
|---|
| 1328 | <td class="left"><a href="#status.416" id="rfc.xref.status.416.1" title="416 Range Not Satisfiable">Section 4.4</a> |
|---|
| 1329 | </td> |
|---|
| 1330 | </tr> |
|---|
| 1331 | </tbody> |
|---|
| 1332 | </table> |
|---|
| 1333 | </div> |
|---|
| 1334 | </div> |
|---|
| 1335 | <div id="header.field.registration"> |
|---|
| 1336 | <h3 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a> <a href="#header.field.registration">Header Field Registration</a></h3> |
|---|
| 1337 | <div id="rfc.section.5.3.p.1"> |
|---|
| 1338 | <p>HTTP header fields are registered within the "Message Headers" registry maintained |
|---|
| 1339 | at <<a href="http://www.iana.org/assignments/message-headers/">http://www.iana.org/assignments/message-headers/</a>>. |
|---|
| 1340 | </p> |
|---|
| 1341 | </div> |
|---|
| 1342 | <div id="rfc.section.5.3.p.2" class="avoidbreakafter"> |
|---|
| 1343 | <p>This document defines the following HTTP header fields, so their associated registry |
|---|
| 1344 | entries have been updated according to the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>): |
|---|
| 1345 | </p> |
|---|
| 1346 | </div> |
|---|
| 1347 | <div id="rfc.table.3"> |
|---|
| 1348 | <div id="iana.header.registration.table"></div> |
|---|
| 1349 | <table class="tt full tleft" cellpadding="3" cellspacing="0"> |
|---|
| 1350 | <thead> |
|---|
| 1351 | <tr> |
|---|
| 1352 | <th>Header Field Name</th> |
|---|
| 1353 | <th>Protocol</th> |
|---|
| 1354 | <th>Status</th> |
|---|
| 1355 | <th>Reference</th> |
|---|
| 1356 | </tr> |
|---|
| 1357 | </thead> |
|---|
| 1358 | <tbody> |
|---|
| 1359 | <tr> |
|---|
| 1360 | <td class="left">Accept-Ranges</td> |
|---|
| 1361 | <td class="left">http</td> |
|---|
| 1362 | <td class="left">standard</td> |
|---|
| 1363 | <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.3" title="Accept-Ranges">Section 2.3</a> |
|---|
| 1364 | </td> |
|---|
| 1365 | </tr> |
|---|
| 1366 | <tr> |
|---|
| 1367 | <td class="left">Content-Range</td> |
|---|
| 1368 | <td class="left">http</td> |
|---|
| 1369 | <td class="left">standard</td> |
|---|
| 1370 | <td class="left"><a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section 4.2</a> |
|---|
| 1371 | </td> |
|---|
| 1372 | </tr> |
|---|
| 1373 | <tr> |
|---|
| 1374 | <td class="left">If-Range</td> |
|---|
| 1375 | <td class="left">http</td> |
|---|
| 1376 | <td class="left">standard</td> |
|---|
| 1377 | <td class="left"><a href="#header.if-range" id="rfc.xref.header.if-range.2" title="If-Range">Section 3.2</a> |
|---|
| 1378 | </td> |
|---|
| 1379 | </tr> |
|---|
| 1380 | <tr> |
|---|
| 1381 | <td class="left">Range</td> |
|---|
| 1382 | <td class="left">http</td> |
|---|
| 1383 | <td class="left">standard</td> |
|---|
| 1384 | <td class="left"><a href="#header.range" id="rfc.xref.header.range.4" title="Range">Section 3.1</a> |
|---|
| 1385 | </td> |
|---|
| 1386 | </tr> |
|---|
| 1387 | </tbody> |
|---|
| 1388 | </table> |
|---|
| 1389 | </div> |
|---|
| 1390 | <div id="rfc.section.5.3.p.3"> |
|---|
| 1391 | <p>The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> |
|---|
| 1392 | </div> |
|---|
| 1393 | </div> |
|---|
| 1394 | <div id="internet.media.type.http"> |
|---|
| 1395 | <h3 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a> <a href="#internet.media.type.http">Internet Media Type Registration</a></h3> |
|---|
| 1396 | <div id="rfc.section.5.4.p.1"> |
|---|
| 1397 | <p>IANA maintains the registry of Internet media types <a href="#BCP13" id="rfc.xref.BCP13.1"><cite title="Media Type Specifications and Registration Procedures">[BCP13]</cite></a> at <<a href="http://www.iana.org/assignments/media-types">http://www.iana.org/assignments/media-types</a>>. |
|---|
| 1398 | </p> |
|---|
| 1399 | </div> |
|---|
| 1400 | <div id="rfc.section.5.4.p.2"> |
|---|
| 1401 | <p>This document serves as the specification for the Internet media type "multipart/byteranges". |
|---|
| 1402 | The following has been registered with IANA. |
|---|
| 1403 | </p> |
|---|
| 1404 | </div> |
|---|
| 1405 | <div id="internet.media.type.multipart.byteranges.reg"> |
|---|
| 1406 | <h4 id="rfc.section.5.4.1"><a href="#rfc.section.5.4.1">5.4.1</a> <a href="#internet.media.type.multipart.byteranges.reg">Internet Media Type multipart/byteranges</a></h4> |
|---|
| 1407 | <div id="rfc.section.5.4.1.p.1"> |
|---|
| 1408 | <dl> |
|---|
| 1409 | <dt>Type name:</dt> |
|---|
| 1410 | <dd>multipart</dd> |
|---|
| 1411 | <dt>Subtype name:</dt> |
|---|
| 1412 | <dd>byteranges</dd> |
|---|
| 1413 | <dt>Required parameters:</dt> |
|---|
| 1414 | <dd>boundary</dd> |
|---|
| 1415 | <dt>Optional parameters:</dt> |
|---|
| 1416 | <dd>N/A</dd> |
|---|
| 1417 | <dt>Encoding considerations:</dt> |
|---|
| 1418 | <dd>only "7bit", "8bit", or "binary" are permitted</dd> |
|---|
| 1419 | <dt>Security considerations:</dt> |
|---|
| 1420 | <dd>see <a href="#security.considerations" title="Security Considerations">Section 6</a> |
|---|
| 1421 | </dd> |
|---|
| 1422 | <dt>Interoperability considerations:</dt> |
|---|
| 1423 | <dd>N/A</dd> |
|---|
| 1424 | <dt>Published specification:</dt> |
|---|
| 1425 | <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>). |
|---|
| 1426 | </dd> |
|---|
| 1427 | <dt>Applications that use this media type:</dt> |
|---|
| 1428 | <dd>HTTP components supporting multiple ranges in a single request.</dd> |
|---|
| 1429 | <dt>Fragment identifier considerations:</dt> |
|---|
| 1430 | <dd>N/A</dd> |
|---|
| 1431 | <dt>Additional information:</dt> |
|---|
| 1432 | <dd> |
|---|
| 1433 | <dl> |
|---|
| 1434 | <dt>Deprecated alias names for this type:</dt> |
|---|
| 1435 | <dd>N/A</dd> |
|---|
| 1436 | <dt>Magic number(s):</dt> |
|---|
| 1437 | <dd>N/A</dd> |
|---|
| 1438 | <dt>File extension(s):</dt> |
|---|
| 1439 | <dd>N/A</dd> |
|---|
| 1440 | <dt>Macintosh file type code(s):</dt> |
|---|
| 1441 | <dd>N/A</dd> |
|---|
| 1442 | </dl> |
|---|
| 1443 | </dd> |
|---|
| 1444 | <dt>Person and email address to contact for further information:</dt> |
|---|
| 1445 | <dd>See Authors' Addresses section.</dd> |
|---|
| 1446 | <dt>Intended usage:</dt> |
|---|
| 1447 | <dd>COMMON</dd> |
|---|
| 1448 | <dt>Restrictions on usage:</dt> |
|---|
| 1449 | <dd>N/A</dd> |
|---|
| 1450 | <dt>Author:</dt> |
|---|
| 1451 | <dd>See Authors' Addresses section.</dd> |
|---|
| 1452 | <dt>Change controller:</dt> |
|---|
| 1453 | <dd>IESG</dd> |
|---|
| 1454 | </dl> |
|---|
| 1455 | </div> |
|---|
| 1456 | </div> |
|---|
| 1457 | </div> |
|---|
| 1458 | </div> |
|---|
| 1459 | <div id="security.considerations"> |
|---|
| 1460 | <h2 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a href="#security.considerations">Security Considerations</a></h2> |
|---|
| 1461 | <div id="rfc.section.6.p.1"> |
|---|
| 1462 | <p>This section is meant to inform developers, information providers, and users of known |
|---|
| 1463 | security concerns specific to the HTTP range request mechanisms. More general security |
|---|
| 1464 | considerations are addressed in HTTP messaging <a href="#RFC7230" id="rfc.xref.RFC7230.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a> and semantics <a href="#RFC7231" id="rfc.xref.RFC7231.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>. |
|---|
| 1465 | </p> |
|---|
| 1466 | </div> |
|---|
| 1467 | <div id="overlapping.ranges"> |
|---|
| 1468 | <h3 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a> <a href="#overlapping.ranges">Denial-of-Service Attacks Using Range</a></h3> |
|---|
| 1469 | <div id="rfc.section.6.1.p.1"> |
|---|
| 1470 | <p>Unconstrained multiple range requests are susceptible to denial-of-service attacks |
|---|
| 1471 | because the effort required to request many overlapping ranges of the same data is |
|---|
| 1472 | tiny compared to the time, memory, and bandwidth consumed by attempting to serve the |
|---|
| 1473 | requested data in many parts. Servers ought to ignore, coalesce, or reject egregious |
|---|
| 1474 | range requests, such as requests for more than two overlapping ranges or for many |
|---|
| 1475 | small ranges in a single set, particularly when the ranges are requested out of order |
|---|
| 1476 | for no apparent reason. Multipart range requests are not designed to support random |
|---|
| 1477 | access. |
|---|
| 1478 | </p> |
|---|
| 1479 | </div> |
|---|
| 1480 | </div> |
|---|
| 1481 | </div> |
|---|
| 1482 | <div id="acks"> |
|---|
| 1483 | <h2 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a href="#acks">Acknowledgments</a></h2> |
|---|
| 1484 | <div id="rfc.section.7.p.1"> |
|---|
| 1485 | <p>See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 10</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>. |
|---|
| 1486 | </p> |
|---|
| 1487 | </div> |
|---|
| 1488 | </div> |
|---|
| 1489 | <h2 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References |
|---|
| 1490 | </h2> |
|---|
| 1491 | <h3 id="rfc.references.1"><a href="#rfc.section.8.1" id="rfc.section.8.1">8.1</a> Normative References |
|---|
| 1492 | </h3> |
|---|
| 1493 | <dl class="reference"> |
|---|
| 1494 | <dt id="RFC2046">[RFC2046]</dt> |
|---|
| 1495 | <dd>Freed, N. and N. Borenstein, “<a href="https://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC 2046, November 1996. |
|---|
| 1496 | </dd> |
|---|
| 1497 | <dt id="RFC2119">[RFC2119]</dt> |
|---|
| 1498 | <dd>Bradner, S., “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP 14, RFC 2119, March 1997. |
|---|
| 1499 | </dd> |
|---|
| 1500 | <dt id="RFC5234">[RFC5234]</dt> |
|---|
| 1501 | <dd>Crocker, D., Ed. and P. Overell, “<a href="https://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD 68, RFC 5234, January 2008. |
|---|
| 1502 | </dd> |
|---|
| 1503 | <dt id="RFC7230">[RFC7230]</dt> |
|---|
| 1504 | <dd>Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://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 2014. |
|---|
| 1505 | </dd> |
|---|
| 1506 | <dt id="RFC7231">[RFC7231]</dt> |
|---|
| 1507 | <dd>Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://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 2014. |
|---|
| 1508 | </dd> |
|---|
| 1509 | <dt id="RFC7232">[RFC7232]</dt> |
|---|
| 1510 | <dd>Fielding, R., Ed. and J. Reschke, Ed., “<a href="https://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 2014. |
|---|
| 1511 | </dd> |
|---|
| 1512 | <dt id="RFC7234">[RFC7234]</dt> |
|---|
| 1513 | <dd>Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, Ed., “<a href="https://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 2014. |
|---|
| 1514 | </dd> |
|---|
| 1515 | </dl> |
|---|
| 1516 | <h3 id="rfc.references.2"><a href="#rfc.section.8.2" id="rfc.section.8.2">8.2</a> Informative References |
|---|
| 1517 | </h3> |
|---|
| 1518 | <dl class="reference"> |
|---|
| 1519 | <dt id="BCP13">[BCP13]</dt> |
|---|
| 1520 | <dd>Freed, N., Klensin, J., and T. Hansen, “<a href="https://tools.ietf.org/html/rfc6838">Media Type Specifications and Registration Procedures</a>”, BCP 13, RFC 6838, January 2013. |
|---|
| 1521 | </dd> |
|---|
| 1522 | <dt id="BCP90">[BCP90]</dt> |
|---|
| 1523 | <dd>Klyne, G., Nottingham, M., and J. Mogul, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP 90, RFC 3864, September 2004. |
|---|
| 1524 | </dd> |
|---|
| 1525 | <dt id="RFC2616">[RFC2616]</dt> |
|---|
| 1526 | <dd>Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC 2616, June 1999. |
|---|
| 1527 | </dd> |
|---|
| 1528 | <dt id="RFC5226">[RFC5226]</dt> |
|---|
| 1529 | <dd>Narten, T. and H. Alvestrand, “<a href="https://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP 26, RFC 5226, May 2008. |
|---|
| 1530 | </dd> |
|---|
| 1531 | </dl> |
|---|
| 1532 | <div id="internet.media.type.multipart.byteranges"> |
|---|
| 1533 | <h2 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></h2> |
|---|
| 1534 | <div id="rfc.section.A.p.1"> |
|---|
| 1535 | <p>When a <a href="#status.206" class="smpl">206 (Partial Content)</a> response message includes the content of multiple ranges, they are transmitted as |
|---|
| 1536 | 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="https://tools.ietf.org/html/rfc2046#section-5.1">Section 5.1</a>) with the media type of "multipart/byteranges". |
|---|
| 1537 | </p> |
|---|
| 1538 | </div> |
|---|
| 1539 | <div id="rfc.section.A.p.2"> |
|---|
| 1540 | <p>The multipart/byteranges media type includes one or more body parts, each with its |
|---|
| 1541 | 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 |
|---|
| 1542 | each body part. |
|---|
| 1543 | </p> |
|---|
| 1544 | </div> |
|---|
| 1545 | <div id="rfc.section.A.p.3"> |
|---|
| 1546 | <p>Implementation Notes: </p> |
|---|
| 1547 | <ol> |
|---|
| 1548 | <li>Additional CRLFs might precede the first boundary string in the body.</li> |
|---|
| 1549 | <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 |
|---|
| 1550 | boundary string incorrectly. |
|---|
| 1551 | </li> |
|---|
| 1552 | <li>A number of clients and servers were coded to an early draft of the byteranges specification |
|---|
| 1553 | that used a media type of multipart/x-byteranges<span id="rfc.iref.m.1"></span><span id="rfc.iref.m.2"></span>, which is almost (but not quite) compatible with this type. |
|---|
| 1554 | </li> |
|---|
| 1555 | </ol> |
|---|
| 1556 | </div> |
|---|
| 1557 | <div id="rfc.section.A.p.4" class="avoidbreakafter"> |
|---|
| 1558 | <p>Despite the name, the "multipart/byteranges" media type is not limited to byte ranges. |
|---|
| 1559 | The following example uses an "exampleunit" range unit: |
|---|
| 1560 | </p> |
|---|
| 1561 | </div> |
|---|
| 1562 | <div id="rfc.figure.u.28"><pre class="text">HTTP/1.1 206 Partial Content |
|---|
| 1563 | Date: Tue, 14 Nov 1995 06:25:24 GMT |
|---|
| 1564 | Last-Modified: Tue, 14 July 04:58:08 GMT |
|---|
| 1565 | Content-Length: 2331785 |
|---|
| 1566 | Content-Type: multipart/byteranges; boundary=THIS_STRING_SEPARATES |
|---|
| 1567 | |
|---|
| 1568 | --THIS_STRING_SEPARATES |
|---|
| 1569 | Content-Type: video/example |
|---|
| 1570 | Content-Range: exampleunit 1.2-4.3/25 |
|---|
| 1571 | |
|---|
| 1572 | ...the first range... |
|---|
| 1573 | --THIS_STRING_SEPARATES |
|---|
| 1574 | Content-Type: video/example |
|---|
| 1575 | Content-Range: exampleunit 11.2-14.3/25 |
|---|
| 1576 | |
|---|
| 1577 | ...the second range |
|---|
| 1578 | --THIS_STRING_SEPARATES-- |
|---|
| 1579 | </pre></div> |
|---|
| 1580 | </div> |
|---|
| 1581 | <div id="changes.from.rfc.2616"> |
|---|
| 1582 | <h2 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> |
|---|
| 1583 | <div id="rfc.section.B.p.1"> |
|---|
| 1584 | <p>Servers are given more leeway in how they respond to a range request, in order to |
|---|
| 1585 | mitigate abuse by malicious (or just greedy) clients. (<a href="#header.range" id="rfc.xref.header.range.5" title="Range">Section 3.1</a>) |
|---|
| 1586 | </p> |
|---|
| 1587 | </div> |
|---|
| 1588 | <div id="rfc.section.B.p.2"> |
|---|
| 1589 | <p>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>) |
|---|
| 1590 | </p> |
|---|
| 1591 | </div> |
|---|
| 1592 | <div id="rfc.section.B.p.3"> |
|---|
| 1593 | <p>The Content-Range header field only has meaning when the status code explicitly defines |
|---|
| 1594 | its use. (<a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section 4.2</a>) |
|---|
| 1595 | </p> |
|---|
| 1596 | </div> |
|---|
| 1597 | <div id="rfc.section.B.p.4"> |
|---|
| 1598 | <p>This specification introduces a Range Unit Registry. (<a href="#range.unit.registry" title="Range Unit Registry">Section 5.1</a>) |
|---|
| 1599 | </p> |
|---|
| 1600 | </div> |
|---|
| 1601 | <div id="rfc.section.B.p.5"> |
|---|
| 1602 | <p>multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a>) |
|---|
| 1603 | </p> |
|---|
| 1604 | </div> |
|---|
| 1605 | </div> |
|---|
| 1606 | <div id="imported.abnf"> |
|---|
| 1607 | <h2 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a href="#imported.abnf">Imported ABNF</a></h2> |
|---|
| 1608 | <div id="rfc.section.C.p.1"> |
|---|
| 1609 | <p>The following core rules are included by reference, as defined in <a href="https://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 |
|---|
| 1610 | 0-9), DQUOTE (double quote), HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET |
|---|
| 1611 | (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII character). |
|---|
| 1612 | </p> |
|---|
| 1613 | </div> |
|---|
| 1614 | <div id="rfc.section.C.p.2"> |
|---|
| 1615 | <p>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>. |
|---|
| 1616 | </p> |
|---|
| 1617 | </div> |
|---|
| 1618 | <div id="rfc.section.C.p.3" class="avoidbreakafter"> |
|---|
| 1619 | <p>The rules below are defined in <a href="#RFC7230" id="rfc.xref.RFC7230.5"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>: |
|---|
| 1620 | </p> |
|---|
| 1621 | </div> |
|---|
| 1622 | <div id="rfc.figure.u.29"><pre class="inline"> <a href="#imported.abnf" class="smpl">OWS</a> = <OWS, see <a href="#RFC7230" id="rfc.xref.RFC7230.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.3</a>> |
|---|
| 1623 | <a href="#imported.abnf" class="smpl">token</a> = <token, see <a href="#RFC7230" id="rfc.xref.RFC7230.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>, <a href="p1-messaging.html#field.components" title="Field Value Components">Section 3.2.6</a>> |
|---|
| 1624 | </pre></div> |
|---|
| 1625 | <div id="rfc.section.C.p.4" class="avoidbreakafter"> |
|---|
| 1626 | <p>The rules below are defined in other parts:</p> |
|---|
| 1627 | </div> |
|---|
| 1628 | <div id="rfc.figure.u.30"><pre class="inline"> <a href="#imported.abnf" class="smpl">HTTP-date</a> = <HTTP-date, see <a href="#RFC7231" id="rfc.xref.RFC7231.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[RFC7231]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 7.1.1.1</a>> |
|---|
| 1629 | <a href="#imported.abnf" class="smpl">entity-tag</a> = <entity-tag, see <a href="#RFC7232" id="rfc.xref.RFC7232.6"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[RFC7232]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a>> |
|---|
| 1630 | </pre></div> |
|---|
| 1631 | </div> |
|---|
| 1632 | <div id="collected.abnf"> |
|---|
| 1633 | <h2 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a href="#collected.abnf">Collected ABNF</a></h2> |
|---|
| 1634 | <div id="rfc.section.D.p.1"> |
|---|
| 1635 | <p>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="#RFC7230" id="rfc.xref.RFC7230.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a>. |
|---|
| 1636 | </p> |
|---|
| 1637 | </div> |
|---|
| 1638 | <div id="rfc.figure.u.31"><pre class="inline"><a href="#header.accept-ranges" class="smpl">Accept-Ranges</a> = acceptable-ranges |
|---|
| 1639 | |
|---|
| 1640 | <a href="#header.content-range" class="smpl">Content-Range</a> = byte-content-range / other-content-range |
|---|
| 1641 | |
|---|
| 1642 | <a href="#imported.abnf" class="smpl">HTTP-date</a> = <HTTP-date, see [RFC7231], Section 7.1.1.1> |
|---|
| 1643 | |
|---|
| 1644 | <a href="#header.if-range" class="smpl">If-Range</a> = entity-tag / HTTP-date |
|---|
| 1645 | |
|---|
| 1646 | <a href="#imported.abnf" class="smpl">OWS</a> = <OWS, see [RFC7230], Section 3.2.3> |
|---|
| 1647 | |
|---|
| 1648 | <a href="#header.range" class="smpl">Range</a> = byte-ranges-specifier / other-ranges-specifier |
|---|
| 1649 | |
|---|
| 1650 | <a href="#header.accept-ranges" class="smpl">acceptable-ranges</a> = ( *( "," OWS ) range-unit *( OWS "," [ OWS |
|---|
| 1651 | range-unit ] ) ) / "none" |
|---|
| 1652 | |
|---|
| 1653 | <a href="#header.content-range" class="smpl">byte-content-range</a> = bytes-unit SP ( byte-range-resp / |
|---|
| 1654 | unsatisfied-range ) |
|---|
| 1655 | <a href="#header.content-range" class="smpl">byte-range</a> = first-byte-pos "-" last-byte-pos |
|---|
| 1656 | <a href="#header.content-range" class="smpl">byte-range-resp</a> = byte-range "/" ( complete-length / "*" ) |
|---|
| 1657 | <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> = *( "," OWS ) ( byte-range-spec / |
|---|
| 1658 | suffix-byte-range-spec ) *( OWS "," [ OWS ( byte-range-spec / |
|---|
| 1659 | suffix-byte-range-spec ) ] ) |
|---|
| 1660 | <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> = first-byte-pos "-" [ last-byte-pos ] |
|---|
| 1661 | <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = bytes-unit "=" byte-range-set |
|---|
| 1662 | <a href="#byte.ranges" class="smpl">bytes-unit</a> = "bytes" |
|---|
| 1663 | |
|---|
| 1664 | <a href="#header.content-range" class="smpl">complete-length</a> = 1*DIGIT |
|---|
| 1665 | |
|---|
| 1666 | <a href="#imported.abnf" class="smpl">entity-tag</a> = <entity-tag, see [RFC7232], Section 2.3> |
|---|
| 1667 | |
|---|
| 1668 | <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> = 1*DIGIT |
|---|
| 1669 | |
|---|
| 1670 | <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> = 1*DIGIT |
|---|
| 1671 | |
|---|
| 1672 | <a href="#header.content-range" class="smpl">other-content-range</a> = other-range-unit SP other-range-resp |
|---|
| 1673 | <a href="#header.content-range" class="smpl">other-range-resp</a> = *CHAR |
|---|
| 1674 | <a href="#header.range" class="smpl">other-range-set</a> = 1*VCHAR |
|---|
| 1675 | <a href="#range.units.other" class="smpl">other-range-unit</a> = token |
|---|
| 1676 | <a href="#header.range" class="smpl">other-ranges-specifier</a> = other-range-unit "=" other-range-set |
|---|
| 1677 | |
|---|
| 1678 | <a href="#range.units" class="smpl">range-unit</a> = bytes-unit / other-range-unit |
|---|
| 1679 | |
|---|
| 1680 | <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> = "-" suffix-length |
|---|
| 1681 | <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> = 1*DIGIT |
|---|
| 1682 | |
|---|
| 1683 | <a href="#imported.abnf" class="smpl">token</a> = <token, see [RFC7230], Section 3.2.6> |
|---|
| 1684 | |
|---|
| 1685 | <a href="#header.content-range" class="smpl">unsatisfied-range</a> = "*/" complete-length |
|---|
| 1686 | </pre></div> |
|---|
| 1687 | </div> |
|---|
| 1688 | <h2 id="rfc.index"><a href="#rfc.index">Index</a></h2> |
|---|
| 1689 | <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.R">R</a> |
|---|
| 1690 | </p> |
|---|
| 1691 | <div class="print2col"> |
|---|
| 1692 | <ul class="ind"> |
|---|
| 1693 | <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul> |
|---|
| 1694 | <li>206 Partial Content (status code) <a href="#rfc.section.4.1"><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> |
|---|
| 1695 | </ul> |
|---|
| 1696 | </li> |
|---|
| 1697 | <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul> |
|---|
| 1698 | <li>416 Range Not Satisfiable (status code) <a href="#rfc.section.4.4"><b>4.4</b></a>, <a href="#rfc.xref.status.416.1">5.2</a></li> |
|---|
| 1699 | </ul> |
|---|
| 1700 | </li> |
|---|
| 1701 | <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul> |
|---|
| 1702 | <li>Accept-Ranges header field <a href="#rfc.xref.header.accept-ranges.1">2</a>, <a href="#rfc.section.2.3"><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> |
|---|
| 1703 | </ul> |
|---|
| 1704 | </li> |
|---|
| 1705 | <li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul> |
|---|
| 1706 | <li><em>BCP13</em> <a href="#rfc.xref.BCP13.1">5.4</a>, <a href="#BCP13"><b>8.2</b></a></li> |
|---|
| 1707 | <li><em>BCP90</em> <a href="#rfc.xref.BCP90.1">5.3</a>, <a href="#BCP90"><b>8.2</b></a></li> |
|---|
| 1708 | </ul> |
|---|
| 1709 | </li> |
|---|
| 1710 | <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul> |
|---|
| 1711 | <li>Content-Range header field <a href="#rfc.xref.header.content-range.1">2</a>, <a href="#rfc.section.4.2"><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> |
|---|
| 1712 | </ul> |
|---|
| 1713 | </li> |
|---|
| 1714 | <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul> |
|---|
| 1715 | <li><tt>Grammar</tt> |
|---|
| 1716 | <ul> |
|---|
| 1717 | <li><tt>Accept-Ranges</tt> <a href="#rfc.iref.g.14"><b>2.3</b></a></li> |
|---|
| 1718 | <li><tt>acceptable-ranges</tt> <a href="#rfc.iref.g.15"><b>2.3</b></a></li> |
|---|
| 1719 | <li><tt>byte-content-range</tt> <a href="#rfc.iref.g.19"><b>4.2</b></a></li> |
|---|
| 1720 | <li><tt>byte-range</tt> <a href="#rfc.iref.g.21"><b>4.2</b></a></li> |
|---|
| 1721 | <li><tt>byte-range-resp</tt> <a href="#rfc.iref.g.20"><b>4.2</b></a></li> |
|---|
| 1722 | <li><tt>byte-range-set</tt> <a href="#rfc.iref.g.7"><b>2.1</b></a></li> |
|---|
| 1723 | <li><tt>byte-range-spec</tt> <a href="#rfc.iref.g.8"><b>2.1</b></a></li> |
|---|
| 1724 | <li><tt>byte-ranges-specifier</tt> <a href="#rfc.iref.g.6"><b>2.1</b></a></li> |
|---|
| 1725 | <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> |
|---|
| 1726 | <li><tt>complete-length</tt> <a href="#rfc.iref.g.25"><b>4.2</b></a></li> |
|---|
| 1727 | <li><tt>Content-Range</tt> <a href="#rfc.iref.g.18"><b>4.2</b></a></li> |
|---|
| 1728 | <li><tt>first-byte-pos</tt> <a href="#rfc.iref.g.9"><b>2.1</b></a></li> |
|---|
| 1729 | <li><tt>If-Range</tt> <a href="#rfc.iref.g.17"><b>3.2</b></a></li> |
|---|
| 1730 | <li><tt>last-byte-pos</tt> <a href="#rfc.iref.g.10"><b>2.1</b></a></li> |
|---|
| 1731 | <li><tt>other-content-range</tt> <a href="#rfc.iref.g.23"><b>4.2</b></a></li> |
|---|
| 1732 | <li><tt>other-range-resp</tt> <a href="#rfc.iref.g.24"><b>4.2</b></a></li> |
|---|
| 1733 | <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> |
|---|
| 1734 | <li><tt>Range</tt> <a href="#rfc.iref.g.16"><b>3.1</b></a></li> |
|---|
| 1735 | <li><tt>range-unit</tt> <a href="#rfc.iref.g.1"><b>2</b></a></li> |
|---|
| 1736 | <li><tt>ranges-specifier</tt> <a href="#rfc.iref.g.5"><b>2.1</b></a></li> |
|---|
| 1737 | <li><tt>suffix-byte-range-spec</tt> <a href="#rfc.iref.g.11"><b>2.1</b></a></li> |
|---|
| 1738 | <li><tt>suffix-length</tt> <a href="#rfc.iref.g.12"><b>2.1</b></a></li> |
|---|
| 1739 | <li><tt>unsatisfied-range</tt> <a href="#rfc.iref.g.22"><b>4.2</b></a></li> |
|---|
| 1740 | </ul> |
|---|
| 1741 | </li> |
|---|
| 1742 | </ul> |
|---|
| 1743 | </li> |
|---|
| 1744 | <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul> |
|---|
| 1745 | <li>If-Range header field <a href="#rfc.xref.header.if-range.1">3.1</a>, <a href="#rfc.section.3.2"><b>3.2</b></a>, <a href="#rfc.xref.header.if-range.2">5.3</a></li> |
|---|
| 1746 | </ul> |
|---|
| 1747 | </li> |
|---|
| 1748 | <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul> |
|---|
| 1749 | <li>Media Type |
|---|
| 1750 | <ul> |
|---|
| 1751 | <li>multipart/byteranges <a href="#rfc.section.5.4.1"><b>5.4.1</b></a>, <a href="#rfc.section.A"><b>A</b></a></li> |
|---|
| 1752 | <li>multipart/x-byteranges <a href="#rfc.iref.m.2">A</a></li> |
|---|
| 1753 | </ul> |
|---|
| 1754 | </li> |
|---|
| 1755 | <li>multipart/byteranges Media Type <a href="#rfc.section.5.4.1"><b>5.4.1</b></a>, <a href="#rfc.section.A"><b>A</b></a></li> |
|---|
| 1756 | <li>multipart/x-byteranges Media Type <a href="#rfc.iref.m.1">A</a></li> |
|---|
| 1757 | </ul> |
|---|
| 1758 | </li> |
|---|
| 1759 | <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul> |
|---|
| 1760 | <li>Range header field <a href="#rfc.xref.header.range.1">2</a>, <a href="#rfc.section.3.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>, <a href="#rfc.xref.header.range.5">B</a></li> |
|---|
| 1761 | <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> |
|---|
| 1762 | <li><em>Section 5.1</em> <a href="#rfc.xref.RFC2046.1">A</a></li> |
|---|
| 1763 | </ul> |
|---|
| 1764 | </li> |
|---|
| 1765 | <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>8.1</b></a></li> |
|---|
| 1766 | <li><em>RFC2616</em> <a href="#RFC2616"><b>8.2</b></a></li> |
|---|
| 1767 | <li><em>RFC5226</em> <a href="#rfc.xref.RFC5226.1">5.1.1</a>, <a href="#RFC5226"><b>8.2</b></a><ul> |
|---|
| 1768 | <li><em>Section 4.1</em> <a href="#rfc.xref.RFC5226.1">5.1.1</a></li> |
|---|
| 1769 | </ul> |
|---|
| 1770 | </li> |
|---|
| 1771 | <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> |
|---|
| 1772 | <li><em>Appendix B.1</em> <a href="#rfc.xref.RFC5234.2">C</a></li> |
|---|
| 1773 | </ul> |
|---|
| 1774 | </li> |
|---|
| 1775 | <li><em>RFC7230</em> <a href="#rfc.xref.RFC7230.1">1.1</a>, <a href="#rfc.xref.RFC7230.2">1.2</a>, <a href="#rfc.xref.RFC7230.3">6</a>, <a href="#rfc.xref.RFC7230.4">7</a>, <a href="#RFC7230"><b>8.1</b></a>, <a href="#rfc.xref.RFC7230.5">C</a>, <a href="#rfc.xref.RFC7230.6">C</a>, <a href="#rfc.xref.RFC7230.7">C</a>, <a href="#rfc.xref.RFC7230.8">D</a><ul> |
|---|
| 1776 | <li><em>Section 1.2</em> <a href="#rfc.xref.RFC7230.8">D</a></li> |
|---|
| 1777 | <li><em>Section 2.5</em> <a href="#rfc.xref.RFC7230.1">1.1</a></li> |
|---|
| 1778 | <li><em>Section 3.2.3</em> <a href="#rfc.xref.RFC7230.6">C</a></li> |
|---|
| 1779 | <li><em>Section 3.2.6</em> <a href="#rfc.xref.RFC7230.7">C</a></li> |
|---|
| 1780 | <li><em>Section 7</em> <a href="#rfc.xref.RFC7230.2">1.2</a></li> |
|---|
| 1781 | <li><em>Section 10</em> <a href="#rfc.xref.RFC7230.4">7</a></li> |
|---|
| 1782 | </ul> |
|---|
| 1783 | </li> |
|---|
| 1784 | <li><em>RFC7231</em> <a href="#rfc.xref.RFC7231.1">2.1</a>, <a href="#rfc.xref.RFC7231.2">6</a>, <a href="#RFC7231"><b>8.1</b></a>, <a href="#rfc.xref.RFC7231.3">C</a><ul> |
|---|
| 1785 | <li><em>Section 3</em> <a href="#rfc.xref.RFC7231.1">2.1</a></li> |
|---|
| 1786 | <li><em>Section 7.1.1.1</em> <a href="#rfc.xref.RFC7231.3">C</a></li> |
|---|
| 1787 | </ul> |
|---|
| 1788 | </li> |
|---|
| 1789 | <li><em>RFC7232</em> <a href="#rfc.xref.RFC7232.1">3.1</a>, <a href="#rfc.xref.RFC7232.2">3.2</a>, <a href="#rfc.xref.RFC7232.3">3.2</a>, <a href="#rfc.xref.RFC7232.4">3.2</a>, <a href="#rfc.xref.RFC7232.5">4.3</a>, <a href="#RFC7232"><b>8.1</b></a>, <a href="#rfc.xref.RFC7232.6">C</a><ul> |
|---|
| 1790 | <li><em>Section 2.1</em> <a href="#rfc.xref.RFC7232.5">4.3</a></li> |
|---|
| 1791 | <li><em>Section 2.2.2</em> <a href="#rfc.xref.RFC7232.2">3.2</a>, <a href="#rfc.xref.RFC7232.4">3.2</a></li> |
|---|
| 1792 | <li><em>Section 2.3</em> <a href="#rfc.xref.RFC7232.6">C</a></li> |
|---|
| 1793 | <li><em>Section 2.3.2</em> <a href="#rfc.xref.RFC7232.3">3.2</a></li> |
|---|
| 1794 | </ul> |
|---|
| 1795 | </li> |
|---|
| 1796 | <li><em>RFC7234</em> <a href="#rfc.xref.RFC7234.1">4.1</a>, <a href="#RFC7234"><b>8.1</b></a><ul> |
|---|
| 1797 | <li><em>Section 4.2.2</em> <a href="#rfc.xref.RFC7234.1">4.1</a></li> |
|---|
| 1798 | </ul> |
|---|
| 1799 | </li> |
|---|
| 1800 | </ul> |
|---|
| 1801 | </li> |
|---|
| 1802 | </ul> |
|---|
| 1803 | </div> |
|---|
| 1804 | <div class="avoidbreakinside"> |
|---|
| 1805 | <h2 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h2> |
|---|
| 1806 | <p><b>Roy T. Fielding</b> |
|---|
| 1807 | (editor) |
|---|
| 1808 | <br>Adobe Systems Incorporated<br>345 Park Ave<br>San Jose, CA 95110<br>USA<br>Email: fielding@gbiv.com<br>URI: <a href="http://roy.gbiv.com/">http://roy.gbiv.com/</a></p> |
|---|
| 1809 | <p><b>Yves Lafon</b> |
|---|
| 1810 | (editor) |
|---|
| 1811 | <br>World Wide Web Consortium<br>W3C / ERCIM<br>2004, rte des Lucioles<br>Sophia-Antipolis, AM 06902<br>France<br>Email: ylafon@w3.org<br>URI: <a href="http://www.raubacapeu.net/people/yves/">http://www.raubacapeu.net/people/yves/</a></p> |
|---|
| 1812 | <p><b>Julian F. Reschke</b> |
|---|
| 1813 | (editor) |
|---|
| 1814 | <br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW 48155<br>Germany<br>Email: julian.reschke@greenbytes.de<br>URI: <a href="http://greenbytes.de/tech/webdav/">http://greenbytes.de/tech/webdav/</a></p> |
|---|
| 1815 | </div> |
|---|
| 1816 | </body> |
|---|
| 1817 | </html> |
|---|
![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
