| 1 | <!DOCTYPE html |
|---|
| 2 | PUBLIC "-//W3C//DTD HTML 4.01//EN"> |
|---|
| 3 | <html lang="en"> |
|---|
| 4 | <head profile="http://www.w3.org/2006/03/hcard"> |
|---|
| 5 | <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> |
|---|
| 6 | <title>HTTP/1.1, part 3: Message Payload and Content Negotiation</title><style type="text/css" title="Xml2Rfc (sans serif)"> |
|---|
| 7 | a { |
|---|
| 8 | text-decoration: none; |
|---|
| 9 | } |
|---|
| 10 | a.smpl { |
|---|
| 11 | color: black; |
|---|
| 12 | } |
|---|
| 13 | a:hover { |
|---|
| 14 | text-decoration: underline; |
|---|
| 15 | } |
|---|
| 16 | a:active { |
|---|
| 17 | text-decoration: underline; |
|---|
| 18 | } |
|---|
| 19 | address { |
|---|
| 20 | margin-top: 1em; |
|---|
| 21 | margin-left: 2em; |
|---|
| 22 | font-style: normal; |
|---|
| 23 | } |
|---|
| 24 | body { |
|---|
| 25 | color: black; |
|---|
| 26 | font-family: verdana, helvetica, arial, sans-serif; |
|---|
| 27 | font-size: 10pt; |
|---|
| 28 | } |
|---|
| 29 | cite { |
|---|
| 30 | font-style: normal; |
|---|
| 31 | } |
|---|
| 32 | dd { |
|---|
| 33 | margin-right: 2em; |
|---|
| 34 | } |
|---|
| 35 | dl { |
|---|
| 36 | margin-left: 2em; |
|---|
| 37 | } |
|---|
| 38 | |
|---|
| 39 | dl.empty dd { |
|---|
| 40 | margin-top: .5em; |
|---|
| 41 | } |
|---|
| 42 | dl p { |
|---|
| 43 | margin-left: 0em; |
|---|
| 44 | } |
|---|
| 45 | dt { |
|---|
| 46 | margin-top: .5em; |
|---|
| 47 | } |
|---|
| 48 | h1 { |
|---|
| 49 | font-size: 14pt; |
|---|
| 50 | line-height: 21pt; |
|---|
| 51 | page-break-after: avoid; |
|---|
| 52 | } |
|---|
| 53 | h1.np { |
|---|
| 54 | page-break-before: always; |
|---|
| 55 | } |
|---|
| 56 | h1 a { |
|---|
| 57 | color: #333333; |
|---|
| 58 | } |
|---|
| 59 | h2 { |
|---|
| 60 | font-size: 12pt; |
|---|
| 61 | line-height: 15pt; |
|---|
| 62 | page-break-after: avoid; |
|---|
| 63 | } |
|---|
| 64 | h2 a { |
|---|
| 65 | color: black; |
|---|
| 66 | } |
|---|
| 67 | h3 { |
|---|
| 68 | font-size: 10pt; |
|---|
| 69 | page-break-after: avoid; |
|---|
| 70 | } |
|---|
| 71 | h3 a { |
|---|
| 72 | color: black; |
|---|
| 73 | } |
|---|
| 74 | h4 { |
|---|
| 75 | font-size: 10pt; |
|---|
| 76 | page-break-after: avoid; |
|---|
| 77 | } |
|---|
| 78 | h4 a { |
|---|
| 79 | color: black; |
|---|
| 80 | } |
|---|
| 81 | h5 { |
|---|
| 82 | font-size: 10pt; |
|---|
| 83 | page-break-after: avoid; |
|---|
| 84 | } |
|---|
| 85 | h5 a { |
|---|
| 86 | color: black; |
|---|
| 87 | } |
|---|
| 88 | img { |
|---|
| 89 | margin-left: 3em; |
|---|
| 90 | } |
|---|
| 91 | li { |
|---|
| 92 | margin-left: 2em; |
|---|
| 93 | margin-right: 2em; |
|---|
| 94 | } |
|---|
| 95 | ol { |
|---|
| 96 | margin-left: 2em; |
|---|
| 97 | margin-right: 2em; |
|---|
| 98 | } |
|---|
| 99 | ol p { |
|---|
| 100 | margin-left: 0em; |
|---|
| 101 | } |
|---|
| 102 | p { |
|---|
| 103 | margin-left: 2em; |
|---|
| 104 | margin-right: 2em; |
|---|
| 105 | } |
|---|
| 106 | pre { |
|---|
| 107 | margin-left: 3em; |
|---|
| 108 | background-color: lightyellow; |
|---|
| 109 | padding: .25em; |
|---|
| 110 | } |
|---|
| 111 | pre.text2 { |
|---|
| 112 | border-style: dotted; |
|---|
| 113 | border-width: 1px; |
|---|
| 114 | background-color: #f0f0f0; |
|---|
| 115 | width: 69em; |
|---|
| 116 | } |
|---|
| 117 | pre.inline { |
|---|
| 118 | background-color: white; |
|---|
| 119 | padding: 0em; |
|---|
| 120 | } |
|---|
| 121 | pre.text { |
|---|
| 122 | border-style: dotted; |
|---|
| 123 | border-width: 1px; |
|---|
| 124 | background-color: #f8f8f8; |
|---|
| 125 | width: 69em; |
|---|
| 126 | } |
|---|
| 127 | pre.drawing { |
|---|
| 128 | border-style: solid; |
|---|
| 129 | border-width: 1px; |
|---|
| 130 | background-color: #f8f8f8; |
|---|
| 131 | padding: 2em; |
|---|
| 132 | } |
|---|
| 133 | table { |
|---|
| 134 | margin-left: 2em; |
|---|
| 135 | } |
|---|
| 136 | table.header { |
|---|
| 137 | width: 95%; |
|---|
| 138 | font-size: 10pt; |
|---|
| 139 | color: white; |
|---|
| 140 | } |
|---|
| 141 | td.top { |
|---|
| 142 | vertical-align: top; |
|---|
| 143 | } |
|---|
| 144 | td.topnowrap { |
|---|
| 145 | vertical-align: top; |
|---|
| 146 | white-space: nowrap; |
|---|
| 147 | } |
|---|
| 148 | td.header { |
|---|
| 149 | background-color: gray; |
|---|
| 150 | width: 50%; |
|---|
| 151 | } |
|---|
| 152 | td.reference { |
|---|
| 153 | vertical-align: top; |
|---|
| 154 | white-space: nowrap; |
|---|
| 155 | padding-right: 1em; |
|---|
| 156 | } |
|---|
| 157 | thead { |
|---|
| 158 | display:table-header-group; |
|---|
| 159 | } |
|---|
| 160 | ul.toc { |
|---|
| 161 | list-style: none; |
|---|
| 162 | margin-left: 1.5em; |
|---|
| 163 | margin-right: 0em; |
|---|
| 164 | padding-left: 0em; |
|---|
| 165 | } |
|---|
| 166 | li.tocline0 { |
|---|
| 167 | line-height: 150%; |
|---|
| 168 | font-weight: bold; |
|---|
| 169 | font-size: 10pt; |
|---|
| 170 | margin-left: 0em; |
|---|
| 171 | margin-right: 0em; |
|---|
| 172 | } |
|---|
| 173 | li.tocline1 { |
|---|
| 174 | line-height: normal; |
|---|
| 175 | font-weight: normal; |
|---|
| 176 | font-size: 9pt; |
|---|
| 177 | margin-left: 0em; |
|---|
| 178 | margin-right: 0em; |
|---|
| 179 | } |
|---|
| 180 | li.tocline2 { |
|---|
| 181 | font-size: 0pt; |
|---|
| 182 | } |
|---|
| 183 | ul p { |
|---|
| 184 | margin-left: 0em; |
|---|
| 185 | } |
|---|
| 186 | ul.ind { |
|---|
| 187 | list-style: none; |
|---|
| 188 | margin-left: 1.5em; |
|---|
| 189 | margin-right: 0em; |
|---|
| 190 | padding-left: 0em; |
|---|
| 191 | } |
|---|
| 192 | li.indline0 { |
|---|
| 193 | font-weight: bold; |
|---|
| 194 | line-height: 200%; |
|---|
| 195 | margin-left: 0em; |
|---|
| 196 | margin-right: 0em; |
|---|
| 197 | } |
|---|
| 198 | li.indline1 { |
|---|
| 199 | font-weight: normal; |
|---|
| 200 | line-height: 150%; |
|---|
| 201 | margin-left: 0em; |
|---|
| 202 | margin-right: 0em; |
|---|
| 203 | } |
|---|
| 204 | .bcp14 { |
|---|
| 205 | font-style: normal; |
|---|
| 206 | text-transform: lowercase; |
|---|
| 207 | font-variant: small-caps; |
|---|
| 208 | } |
|---|
| 209 | .comment { |
|---|
| 210 | background-color: yellow; |
|---|
| 211 | } |
|---|
| 212 | .center { |
|---|
| 213 | text-align: center; |
|---|
| 214 | } |
|---|
| 215 | .error { |
|---|
| 216 | color: red; |
|---|
| 217 | font-style: italic; |
|---|
| 218 | font-weight: bold; |
|---|
| 219 | } |
|---|
| 220 | .figure { |
|---|
| 221 | font-weight: bold; |
|---|
| 222 | text-align: center; |
|---|
| 223 | font-size: 9pt; |
|---|
| 224 | } |
|---|
| 225 | .filename { |
|---|
| 226 | color: #333333; |
|---|
| 227 | font-weight: bold; |
|---|
| 228 | font-size: 12pt; |
|---|
| 229 | line-height: 21pt; |
|---|
| 230 | text-align: center; |
|---|
| 231 | } |
|---|
| 232 | .fn { |
|---|
| 233 | font-weight: bold; |
|---|
| 234 | } |
|---|
| 235 | .hidden { |
|---|
| 236 | display: none; |
|---|
| 237 | } |
|---|
| 238 | .left { |
|---|
| 239 | text-align: left; |
|---|
| 240 | } |
|---|
| 241 | .right { |
|---|
| 242 | text-align: right; |
|---|
| 243 | } |
|---|
| 244 | .title { |
|---|
| 245 | color: #990000; |
|---|
| 246 | font-size: 18pt; |
|---|
| 247 | line-height: 18pt; |
|---|
| 248 | font-weight: bold; |
|---|
| 249 | text-align: center; |
|---|
| 250 | margin-top: 36pt; |
|---|
| 251 | } |
|---|
| 252 | .vcardline { |
|---|
| 253 | display: block; |
|---|
| 254 | } |
|---|
| 255 | .warning { |
|---|
| 256 | font-size: 14pt; |
|---|
| 257 | background-color: yellow; |
|---|
| 258 | } |
|---|
| 259 | |
|---|
| 260 | |
|---|
| 261 | @media print { |
|---|
| 262 | .noprint { |
|---|
| 263 | display: none; |
|---|
| 264 | } |
|---|
| 265 | |
|---|
| 266 | a { |
|---|
| 267 | color: black; |
|---|
| 268 | text-decoration: none; |
|---|
| 269 | } |
|---|
| 270 | |
|---|
| 271 | table.header { |
|---|
| 272 | width: 90%; |
|---|
| 273 | } |
|---|
| 274 | |
|---|
| 275 | td.header { |
|---|
| 276 | width: 50%; |
|---|
| 277 | color: black; |
|---|
| 278 | background-color: white; |
|---|
| 279 | vertical-align: top; |
|---|
| 280 | font-size: 12pt; |
|---|
| 281 | } |
|---|
| 282 | |
|---|
| 283 | ul.toc a::after { |
|---|
| 284 | content: leader('.') target-counter(attr(href), page); |
|---|
| 285 | } |
|---|
| 286 | |
|---|
| 287 | a.iref { |
|---|
| 288 | content: target-counter(attr(href), page); |
|---|
| 289 | } |
|---|
| 290 | |
|---|
| 291 | .print2col { |
|---|
| 292 | column-count: 2; |
|---|
| 293 | -moz-column-count: 2; |
|---|
| 294 | column-fill: auto; |
|---|
| 295 | } |
|---|
| 296 | } |
|---|
| 297 | |
|---|
| 298 | @page { |
|---|
| 299 | @top-left { |
|---|
| 300 | content: "INTERNET DRAFT"; |
|---|
| 301 | } |
|---|
| 302 | @top-right { |
|---|
| 303 | content: "January 2008"; |
|---|
| 304 | } |
|---|
| 305 | @top-center { |
|---|
| 306 | content: "HTTP/1.1, Part 3"; |
|---|
| 307 | } |
|---|
| 308 | @bottom-left { |
|---|
| 309 | content: "Fielding, et al."; |
|---|
| 310 | } |
|---|
| 311 | @bottom-center { |
|---|
| 312 | content: "Standards Track"; |
|---|
| 313 | } |
|---|
| 314 | @bottom-right { |
|---|
| 315 | content: "[Page " counter(page) "]"; |
|---|
| 316 | } |
|---|
| 317 | } |
|---|
| 318 | |
|---|
| 319 | @page:first { |
|---|
| 320 | @top-left { |
|---|
| 321 | content: normal; |
|---|
| 322 | } |
|---|
| 323 | @top-right { |
|---|
| 324 | content: normal; |
|---|
| 325 | } |
|---|
| 326 | @top-center { |
|---|
| 327 | content: normal; |
|---|
| 328 | } |
|---|
| 329 | } |
|---|
| 330 | </style><link rel="Contents" href="#rfc.toc"> |
|---|
| 331 | <link rel="Author" href="#rfc.authors"> |
|---|
| 332 | <link rel="Copyright" href="#rfc.copyright"> |
|---|
| 333 | <link rel="Index" href="#rfc.index"> |
|---|
| 334 | <link rel="Chapter" title="1 Introduction" href="#rfc.section.1"> |
|---|
| 335 | <link rel="Chapter" title="2 Protocol Parameters" href="#rfc.section.2"> |
|---|
| 336 | <link rel="Chapter" title="3 Entity" href="#rfc.section.3"> |
|---|
| 337 | <link rel="Chapter" title="4 Content Negotiation" href="#rfc.section.4"> |
|---|
| 338 | <link rel="Chapter" title="5 Header Field Definitions" href="#rfc.section.5"> |
|---|
| 339 | <link rel="Chapter" title="6 IANA Considerations" href="#rfc.section.6"> |
|---|
| 340 | <link rel="Chapter" title="7 Security Considerations" href="#rfc.section.7"> |
|---|
| 341 | <link rel="Chapter" title="8 Acknowledgments" href="#rfc.section.8"> |
|---|
| 342 | <link rel="Chapter" href="#rfc.section.9" title="9 References"> |
|---|
| 343 | <link rel="Appendix" title="A Differences Between HTTP Entities and RFC 2045 Entities" href="#rfc.section.A"> |
|---|
| 344 | <link rel="Appendix" title="B Additional Features" href="#rfc.section.B"> |
|---|
| 345 | <link rel="Appendix" title="C Compatibility with Previous Versions" href="#rfc.section.C"> |
|---|
| 346 | <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> |
|---|
| 347 | <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.354, 2007/12/31 13:43:05, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> |
|---|
| 348 | <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> |
|---|
| 349 | <meta name="DC.Creator" content="Fielding, R."> |
|---|
| 350 | <meta name="DC.Creator" content="Gettys, J."> |
|---|
| 351 | <meta name="DC.Creator" content="Mogul, J."> |
|---|
| 352 | <meta name="DC.Creator" content="Frystyk, H."> |
|---|
| 353 | <meta name="DC.Creator" content="Masinter, L."> |
|---|
| 354 | <meta name="DC.Creator" content="Leach, P."> |
|---|
| 355 | <meta name="DC.Creator" content="Berners-Lee, T."> |
|---|
| 356 | <meta name="DC.Creator" content="Lafon, Y."> |
|---|
| 357 | <meta name="DC.Creator" content="Reschke, J. F."> |
|---|
| 358 | <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> |
|---|
| 359 | <meta name="DC.Date.Issued" scheme="ISO8601" content="2008-01"> |
|---|
| 360 | <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2068"> |
|---|
| 361 | <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> |
|---|
| 362 | <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> |
|---|
| 363 | </head> |
|---|
| 364 | <body> |
|---|
| 365 | <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1"> |
|---|
| 366 | <tr> |
|---|
| 367 | <td class="header left">Network Working Group</td> |
|---|
| 368 | <td class="header right">R. Fielding, Editor</td> |
|---|
| 369 | </tr> |
|---|
| 370 | <tr> |
|---|
| 371 | <td class="header left">Internet Draft</td> |
|---|
| 372 | <td class="header right">Day Software</td> |
|---|
| 373 | </tr> |
|---|
| 374 | <tr> |
|---|
| 375 | <td class="header left"> |
|---|
| 376 | <draft-ietf-httpbis-p3-payload-latest> |
|---|
| 377 | |
|---|
| 378 | </td> |
|---|
| 379 | <td class="header right">J. Gettys</td> |
|---|
| 380 | </tr> |
|---|
| 381 | <tr> |
|---|
| 382 | <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2068">2068</a>, |
|---|
| 383 | <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) |
|---|
| 384 | </td> |
|---|
| 385 | <td class="header right">One Laptop per Child</td> |
|---|
| 386 | </tr> |
|---|
| 387 | <tr> |
|---|
| 388 | <td class="header left">Intended status: Standards Track</td> |
|---|
| 389 | <td class="header right">J. Mogul</td> |
|---|
| 390 | </tr> |
|---|
| 391 | <tr> |
|---|
| 392 | <td class="header left">Expires: July 2008</td> |
|---|
| 393 | <td class="header right">HP</td> |
|---|
| 394 | </tr> |
|---|
| 395 | <tr> |
|---|
| 396 | <td class="header left"></td> |
|---|
| 397 | <td class="header right">H. Frystyk</td> |
|---|
| 398 | </tr> |
|---|
| 399 | <tr> |
|---|
| 400 | <td class="header left"></td> |
|---|
| 401 | <td class="header right">Microsoft</td> |
|---|
| 402 | </tr> |
|---|
| 403 | <tr> |
|---|
| 404 | <td class="header left"></td> |
|---|
| 405 | <td class="header right">L. Masinter</td> |
|---|
| 406 | </tr> |
|---|
| 407 | <tr> |
|---|
| 408 | <td class="header left"></td> |
|---|
| 409 | <td class="header right">Adobe Systems</td> |
|---|
| 410 | </tr> |
|---|
| 411 | <tr> |
|---|
| 412 | <td class="header left"></td> |
|---|
| 413 | <td class="header right">P. Leach</td> |
|---|
| 414 | </tr> |
|---|
| 415 | <tr> |
|---|
| 416 | <td class="header left"></td> |
|---|
| 417 | <td class="header right">Microsoft</td> |
|---|
| 418 | </tr> |
|---|
| 419 | <tr> |
|---|
| 420 | <td class="header left"></td> |
|---|
| 421 | <td class="header right">T. Berners-Lee</td> |
|---|
| 422 | </tr> |
|---|
| 423 | <tr> |
|---|
| 424 | <td class="header left"></td> |
|---|
| 425 | <td class="header right">W3C/MIT</td> |
|---|
| 426 | </tr> |
|---|
| 427 | <tr> |
|---|
| 428 | <td class="header left"></td> |
|---|
| 429 | <td class="header right">Y. Lafon, Editor</td> |
|---|
| 430 | </tr> |
|---|
| 431 | <tr> |
|---|
| 432 | <td class="header left"></td> |
|---|
| 433 | <td class="header right">W3C</td> |
|---|
| 434 | </tr> |
|---|
| 435 | <tr> |
|---|
| 436 | <td class="header left"></td> |
|---|
| 437 | <td class="header right">J. F. Reschke, Editor</td> |
|---|
| 438 | </tr> |
|---|
| 439 | <tr> |
|---|
| 440 | <td class="header left"></td> |
|---|
| 441 | <td class="header right">greenbytes</td> |
|---|
| 442 | </tr> |
|---|
| 443 | <tr> |
|---|
| 444 | <td class="header left"></td> |
|---|
| 445 | <td class="header right">January 2008</td> |
|---|
| 446 | </tr> |
|---|
| 447 | </table> |
|---|
| 448 | <p class="title">HTTP/1.1, part 3: Message Payload and Content Negotiation<br><span class="filename">draft-ietf-httpbis-p3-payload-latest</span></p> |
|---|
| 449 | <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1> |
|---|
| 450 | <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she |
|---|
| 451 | is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section |
|---|
| 452 | 6 of BCP 79. |
|---|
| 453 | </p> |
|---|
| 454 | <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note |
|---|
| 455 | that other groups may also distribute working documents as Internet-Drafts. |
|---|
| 456 | </p> |
|---|
| 457 | <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other |
|---|
| 458 | documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work |
|---|
| 459 | in progress”. |
|---|
| 460 | </p> |
|---|
| 461 | <p>The list of current Internet-Drafts can be accessed at <<a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>>. |
|---|
| 462 | </p> |
|---|
| 463 | <p>The list of Internet-Draft Shadow Directories can be accessed at <<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>>. |
|---|
| 464 | </p> |
|---|
| 465 | <p>This Internet-Draft will expire in July 2008.</p> |
|---|
| 466 | <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> |
|---|
| 467 | <p>Copyright © The IETF Trust (2008). All Rights Reserved.</p> |
|---|
| 468 | <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> |
|---|
| 469 | <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information |
|---|
| 470 | systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the |
|---|
| 471 | seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part |
|---|
| 472 | 3 defines HTTP message content, metadata, and content negotiation. |
|---|
| 473 | </p> |
|---|
| 474 | <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> |
|---|
| 475 | <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues |
|---|
| 476 | list is at <<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>> and related documents (including fancy diffs) can be found at <<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>>. |
|---|
| 477 | </p> |
|---|
| 478 | <hr class="noprint"> |
|---|
| 479 | <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1> |
|---|
| 480 | <ul class="toc"> |
|---|
| 481 | <li class="tocline0">1. <a href="#introduction">Introduction</a><ul class="toc"> |
|---|
| 482 | <li class="tocline1">1.1 <a href="#intro.requirements">Requirements</a></li> |
|---|
| 483 | </ul> |
|---|
| 484 | </li> |
|---|
| 485 | <li class="tocline0">2. <a href="#protocol.parameters">Protocol Parameters</a><ul class="toc"> |
|---|
| 486 | <li class="tocline1">2.1 <a href="#character.sets">Character Sets</a><ul class="toc"> |
|---|
| 487 | <li class="tocline1">2.1.1 <a href="#missing.charset">Missing Charset</a></li> |
|---|
| 488 | </ul> |
|---|
| 489 | </li> |
|---|
| 490 | <li class="tocline1">2.2 <a href="#content.codings">Content Codings</a></li> |
|---|
| 491 | <li class="tocline1">2.3 <a href="#media.types">Media Types</a><ul class="toc"> |
|---|
| 492 | <li class="tocline1">2.3.1 <a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li> |
|---|
| 493 | <li class="tocline1">2.3.2 <a href="#multipart.types">Multipart Types</a></li> |
|---|
| 494 | </ul> |
|---|
| 495 | </li> |
|---|
| 496 | <li class="tocline1">2.4 <a href="#quality.values">Quality Values</a></li> |
|---|
| 497 | <li class="tocline1">2.5 <a href="#language.tags">Language Tags</a></li> |
|---|
| 498 | </ul> |
|---|
| 499 | </li> |
|---|
| 500 | <li class="tocline0">3. <a href="#entity">Entity</a><ul class="toc"> |
|---|
| 501 | <li class="tocline1">3.1 <a href="#entity.header.fields">Entity Header Fields</a></li> |
|---|
| 502 | <li class="tocline1">3.2 <a href="#entity.body">Entity Body</a><ul class="toc"> |
|---|
| 503 | <li class="tocline1">3.2.1 <a href="#type">Type</a></li> |
|---|
| 504 | <li class="tocline1">3.2.2 <a href="#entity.length">Entity Length</a></li> |
|---|
| 505 | </ul> |
|---|
| 506 | </li> |
|---|
| 507 | </ul> |
|---|
| 508 | </li> |
|---|
| 509 | <li class="tocline0">4. <a href="#content.negotiation">Content Negotiation</a><ul class="toc"> |
|---|
| 510 | <li class="tocline1">4.1 <a href="#server-driven.negotiation">Server-driven Negotiation</a></li> |
|---|
| 511 | <li class="tocline1">4.2 <a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li> |
|---|
| 512 | <li class="tocline1">4.3 <a href="#transparent.negotiation">Transparent Negotiation</a></li> |
|---|
| 513 | </ul> |
|---|
| 514 | </li> |
|---|
| 515 | <li class="tocline0">5. <a href="#header.fields">Header Field Definitions</a><ul class="toc"> |
|---|
| 516 | <li class="tocline1">5.1 <a href="#header.accept">Accept</a></li> |
|---|
| 517 | <li class="tocline1">5.2 <a href="#header.accept-charset">Accept-Charset</a></li> |
|---|
| 518 | <li class="tocline1">5.3 <a href="#header.accept-encoding">Accept-Encoding</a></li> |
|---|
| 519 | <li class="tocline1">5.4 <a href="#header.accept-language">Accept-Language</a></li> |
|---|
| 520 | <li class="tocline1">5.5 <a href="#header.content-encoding">Content-Encoding</a></li> |
|---|
| 521 | <li class="tocline1">5.6 <a href="#header.content-language">Content-Language</a></li> |
|---|
| 522 | <li class="tocline1">5.7 <a href="#header.content-location">Content-Location</a></li> |
|---|
| 523 | <li class="tocline1">5.8 <a href="#header.content-md5">Content-MD5</a></li> |
|---|
| 524 | <li class="tocline1">5.9 <a href="#header.content-type">Content-Type</a></li> |
|---|
| 525 | </ul> |
|---|
| 526 | </li> |
|---|
| 527 | <li class="tocline0">6. <a href="#IANA.considerations">IANA Considerations</a></li> |
|---|
| 528 | <li class="tocline0">7. <a href="#security.considerations">Security Considerations</a><ul class="toc"> |
|---|
| 529 | <li class="tocline1">7.1 <a href="#privacy.issues.connected.to.accept.headers">Privacy Issues Connected to Accept Headers</a></li> |
|---|
| 530 | <li class="tocline1">7.2 <a href="#content-disposition.issues">Content-Disposition Issues</a></li> |
|---|
| 531 | </ul> |
|---|
| 532 | </li> |
|---|
| 533 | <li class="tocline0">8. <a href="#ack">Acknowledgments</a></li> |
|---|
| 534 | <li class="tocline0">9. <a href="#rfc.references">References</a><ul class="toc"> |
|---|
| 535 | <li class="tocline1">9.1 <a href="#rfc.references.1">Normative References</a></li> |
|---|
| 536 | <li class="tocline1">9.2 <a href="#rfc.references.2">Informative References</a></li> |
|---|
| 537 | <li class="tocline1">9.3 <a href="#rfc.references.3">References (to be categorized)</a></li> |
|---|
| 538 | </ul> |
|---|
| 539 | </li> |
|---|
| 540 | <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li> |
|---|
| 541 | <li class="tocline0">A. <a href="#differences.between.http.entities.and.rfc.2045.entities">Differences Between HTTP Entities and RFC 2045 Entities</a><ul class="toc"> |
|---|
| 542 | <li class="tocline1">A.1 <a href="#mime-version">MIME-Version</a></li> |
|---|
| 543 | <li class="tocline1">A.2 <a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li> |
|---|
| 544 | <li class="tocline1">A.3 <a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li> |
|---|
| 545 | <li class="tocline1">A.4 <a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li> |
|---|
| 546 | <li class="tocline1">A.5 <a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li> |
|---|
| 547 | <li class="tocline1">A.6 <a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li> |
|---|
| 548 | </ul> |
|---|
| 549 | </li> |
|---|
| 550 | <li class="tocline0">B. <a href="#additional.features">Additional Features</a><ul class="toc"> |
|---|
| 551 | <li class="tocline1">B.1 <a href="#content-disposition">Content-Disposition</a></li> |
|---|
| 552 | </ul> |
|---|
| 553 | </li> |
|---|
| 554 | <li class="tocline0">C. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc"> |
|---|
| 555 | <li class="tocline1">C.1 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li> |
|---|
| 556 | <li class="tocline1">C.2 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> |
|---|
| 557 | </ul> |
|---|
| 558 | </li> |
|---|
| 559 | <li class="tocline0">D. <a href="#rfc.section.D">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc"> |
|---|
| 560 | <li class="tocline1">D.1 <a href="#rfc.section.D.1">Since RFC2616</a></li> |
|---|
| 561 | <li class="tocline1">D.2 <a href="#rfc.section.D.2">Since draft-ietf-httpbis-p3-payload-00</a></li> |
|---|
| 562 | </ul> |
|---|
| 563 | </li> |
|---|
| 564 | <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li> |
|---|
| 565 | <li class="tocline0"><a href="#rfc.index">Index</a></li> |
|---|
| 566 | </ul> |
|---|
| 567 | <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> <a id="introduction" href="#introduction">Introduction</a></h1> |
|---|
| 568 | <p id="rfc.section.1.p.1">This document will define aspects of HTTP related to the payload of messages (message content), including metadata and media |
|---|
| 569 | types, along with HTTP content negotiation. Right now it only includes the extracted relevant sections of RFC 2616 without |
|---|
| 570 | edit. |
|---|
| 571 | </p> |
|---|
| 572 | <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a> <a id="intro.requirements" href="#intro.requirements">Requirements</a></h2> |
|---|
| 573 | <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" |
|---|
| 574 | in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>. |
|---|
| 575 | </p> |
|---|
| 576 | <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant." |
|---|
| 577 | </p> |
|---|
| 578 | <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1> |
|---|
| 579 | <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> <a id="character.sets" href="#character.sets">Character Sets</a></h2> |
|---|
| 580 | <p id="rfc.section.2.1.p.1">HTTP uses the same definition of the term "character set" as that described for MIME:</p> |
|---|
| 581 | <p id="rfc.section.2.1.p.2">The term "character set" is used in this document to refer to a method used with one or more tables to convert a sequence |
|---|
| 582 | of octets into a sequence of characters. Note that unconditional conversion in the other direction is not required, in that |
|---|
| 583 | not all characters may be available in a given character set and a character set may provide more than one sequence of octets |
|---|
| 584 | to represent a particular character. This definition is intended to allow various kinds of character encoding, from simple |
|---|
| 585 | single-table mappings such as US-ASCII to complex table switching methods such as those that use ISO-2022's techniques. However, |
|---|
| 586 | the definition associated with a MIME character set name <em class="bcp14">MUST</em> fully specify the mapping to be performed from octets to characters. In particular, use of external profiling information |
|---|
| 587 | to determine the exact mapping is not permitted. |
|---|
| 588 | </p> |
|---|
| 589 | <dl class="empty"> |
|---|
| 590 | <dd> <b>Note:</b> This use of the term "character set" is more commonly referred to as a "character encoding." However, since HTTP and MIME |
|---|
| 591 | share the same registry, it is important that the terminology also be shared. |
|---|
| 592 | </dd> |
|---|
| 593 | </dl> |
|---|
| 594 | <p id="rfc.section.2.1.p.4">HTTP character sets are identified by case-insensitive tokens. The complete set of tokens is defined by the IANA Character |
|---|
| 595 | Set registry (<<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>>). |
|---|
| 596 | </p> |
|---|
| 597 | <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span> charset = token |
|---|
| 598 | </pre><p id="rfc.section.2.1.p.6">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA |
|---|
| 599 | Character Set registry <em class="bcp14">MUST</em> represent the character set defined by that registry. Applications <em class="bcp14">SHOULD</em> limit their use of character sets to those defined by the IANA registry. |
|---|
| 600 | </p> |
|---|
| 601 | <p id="rfc.section.2.1.p.7">HTTP uses charset in two contexts: within an Accept-Charset request header (in which the charset value is an unquoted token) |
|---|
| 602 | and as the value of a parameter in a Content-Type header (within a request or response), in which case the parameter value |
|---|
| 603 | of the charset parameter may be quoted. |
|---|
| 604 | </p> |
|---|
| 605 | <p id="rfc.section.2.1.p.8">Implementors should be aware of IETF character set requirements <a href="#RFC2279" id="rfc.xref.RFC2279.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC2279]</cite></a> <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>. |
|---|
| 606 | </p> |
|---|
| 607 | <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a> <a id="missing.charset" href="#missing.charset">Missing Charset</a></h3> |
|---|
| 608 | <p id="rfc.section.2.1.1.p.1">Some HTTP/1.0 software has interpreted a Content-Type header without charset parameter incorrectly to mean "recipient should |
|---|
| 609 | guess." Senders wishing to defeat this behavior <em class="bcp14">MAY</em> include a charset parameter even when the charset is ISO-8859-1 (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>) and <em class="bcp14">SHOULD</em> do so when it is known that it will not confuse the recipient. |
|---|
| 610 | </p> |
|---|
| 611 | <p id="rfc.section.2.1.1.p.2">Unfortunately, some older HTTP/1.0 clients did not deal properly with an explicit charset parameter. HTTP/1.1 recipients <em class="bcp14">MUST</em> respect the charset label provided by the sender; and those user agents that have a provision to "guess" a charset <em class="bcp14">MUST</em> use the charset from the content-type field if they support that charset, rather than the recipient's preference, when initially |
|---|
| 612 | displaying a document. See <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 2.3.1</a>. |
|---|
| 613 | </p> |
|---|
| 614 | <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a> <a id="content.codings" href="#content.codings">Content Codings</a></h2> |
|---|
| 615 | <p id="rfc.section.2.2.p.1">Content coding values indicate an encoding transformation that has been or can be applied to an entity. Content codings are |
|---|
| 616 | primarily used to allow a document to be compressed or otherwise usefully transformed without losing the identity of its underlying |
|---|
| 617 | media type and without loss of information. Frequently, the entity is stored in coded form, transmitted directly, and only |
|---|
| 618 | decoded by the recipient. |
|---|
| 619 | </p> |
|---|
| 620 | <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.2"></span> content-coding = token |
|---|
| 621 | </pre><p id="rfc.section.2.2.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section 5.3</a>) and Content-Encoding (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section 5.5</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding |
|---|
| 622 | mechanism will be required to remove the encoding. |
|---|
| 623 | </p> |
|---|
| 624 | <p id="rfc.section.2.2.p.4">The Internet Assigned Numbers Authority (IANA) acts as a registry for content-coding value tokens. Initially, the registry |
|---|
| 625 | contains the following tokens: |
|---|
| 626 | </p> |
|---|
| 627 | <p id="rfc.section.2.2.p.5">gzip<span id="rfc.iref.g.3"></span> |
|---|
| 628 | </p> |
|---|
| 629 | <dl class="empty"> |
|---|
| 630 | <dd>An encoding format produced by the file compression program "gzip" (GNU zip) as described in <a href="#RFC1952" id="rfc.xref.RFC1952.1"><cite title="GZIP file format specification version 4.3">[RFC1952]</cite></a>. This format is a Lempel-Ziv coding (LZ77) with a 32 bit CRC. |
|---|
| 631 | </dd> |
|---|
| 632 | </dl> |
|---|
| 633 | <p id="rfc.section.2.2.p.6">compress<span id="rfc.iref.c.1"></span> |
|---|
| 634 | </p> |
|---|
| 635 | <dl class="empty"> |
|---|
| 636 | <dd>The encoding format produced by the common UNIX file compression program "compress". This format is an adaptive Lempel-Ziv-Welch |
|---|
| 637 | coding (LZW). |
|---|
| 638 | </dd> |
|---|
| 639 | <dd>Use of program names for the identification of encoding formats is not desirable and is discouraged for future encodings. |
|---|
| 640 | Their use here is representative of historical practice, not good design. For compatibility with previous implementations |
|---|
| 641 | of HTTP, applications <em class="bcp14">SHOULD</em> consider "x-gzip" and "x-compress" to be equivalent to "gzip" and "compress" respectively. |
|---|
| 642 | </dd> |
|---|
| 643 | </dl> |
|---|
| 644 | <p id="rfc.section.2.2.p.7">deflate<span id="rfc.iref.d.1"></span> |
|---|
| 645 | </p> |
|---|
| 646 | <dl class="empty"> |
|---|
| 647 | <dd>The "zlib" format defined in <a href="#RFC1950" id="rfc.xref.RFC1950.1"><cite title="ZLIB Compressed Data Format Specification version 3.3">[RFC1950]</cite></a> in combination with the "deflate" compression mechanism described in <a href="#RFC1951" id="rfc.xref.RFC1951.1"><cite title="DEFLATE Compressed Data Format Specification version 1.3">[RFC1951]</cite></a>. |
|---|
| 648 | </dd> |
|---|
| 649 | </dl> |
|---|
| 650 | <p id="rfc.section.2.2.p.8">identity<span id="rfc.iref.i.1"></span> |
|---|
| 651 | </p> |
|---|
| 652 | <dl class="empty"> |
|---|
| 653 | <dd>The default (identity) encoding; the use of no transformation whatsoever. This content-coding is used only in the Accept-Encoding |
|---|
| 654 | header, and <em class="bcp14">SHOULD NOT</em> be used in the Content-Encoding header. |
|---|
| 655 | </dd> |
|---|
| 656 | </dl> |
|---|
| 657 | <p id="rfc.section.2.2.p.9">New content-coding value tokens <em class="bcp14">SHOULD</em> be registered; to allow interoperability between clients and servers, specifications of the content coding algorithms needed |
|---|
| 658 | to implement a new value <em class="bcp14">SHOULD</em> be publicly available and adequate for independent implementation, and conform to the purpose of content coding defined in |
|---|
| 659 | this section. |
|---|
| 660 | </p> |
|---|
| 661 | <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a> <a id="media.types" href="#media.types">Media Types</a></h2> |
|---|
| 662 | <p id="rfc.section.2.3.p.1">HTTP uses Internet Media Types <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section 5.9</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section 5.1</a>) header fields in order to provide open and extensible data typing and type negotiation. |
|---|
| 663 | </p> |
|---|
| 664 | <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span> media-type = type "/" subtype *( ";" parameter ) |
|---|
| 665 | type = token |
|---|
| 666 | subtype = token |
|---|
| 667 | </pre><p id="rfc.section.2.3.p.3">Parameters <em class="bcp14">MAY</em> follow the type/subtype in the form of attribute/value pairs. |
|---|
| 668 | </p> |
|---|
| 669 | <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span> parameter = attribute "=" value |
|---|
| 670 | attribute = token |
|---|
| 671 | value = token | quoted-string |
|---|
| 672 | </pre><p id="rfc.section.2.3.p.5">The type, subtype, and parameter attribute names are case-insensitive. Parameter values might or might not be case-sensitive, |
|---|
| 673 | depending on the semantics of the parameter name. Linear white space (LWS) <em class="bcp14">MUST NOT</em> be used between the type and subtype, nor between an attribute and its value. The presence or absence of a parameter might |
|---|
| 674 | be significant to the processing of a media-type, depending on its definition within the media type registry. |
|---|
| 675 | </p> |
|---|
| 676 | <p id="rfc.section.2.3.p.6">Note that some older HTTP applications do not recognize media type parameters. When sending data to older HTTP applications, |
|---|
| 677 | implementations <em class="bcp14">SHOULD</em> only use media type parameters when they are required by that type/subtype definition. |
|---|
| 678 | </p> |
|---|
| 679 | <p id="rfc.section.2.3.p.7">Media-type values are registered with the Internet Assigned Number Authority (IANA). The media type registration process is |
|---|
| 680 | outlined in <a href="#RFC4288" id="rfc.xref.RFC4288.2"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>. Use of non-registered media types is discouraged. |
|---|
| 681 | </p> |
|---|
| 682 | <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a> <a id="canonicalization.and.text.defaults" href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3> |
|---|
| 683 | <p id="rfc.section.2.3.1.p.1">Internet media types are registered with a canonical form. An entity-body transferred via HTTP messages <em class="bcp14">MUST</em> be represented in the appropriate canonical form prior to its transmission except for "text" types, as defined in the next |
|---|
| 684 | paragraph. |
|---|
| 685 | </p> |
|---|
| 686 | <p id="rfc.section.2.3.1.p.2">When in canonical form, media subtypes of the "text" type use CRLF as the text line break. HTTP relaxes this requirement and |
|---|
| 687 | allows the transport of text media with plain CR or LF alone representing a line break when it is done consistently for an |
|---|
| 688 | entire entity-body. HTTP applications <em class="bcp14">MUST</em> accept CRLF, bare CR, and bare LF as being representative of a line break in text media received via HTTP. In addition, if |
|---|
| 689 | the text is represented in a character set that does not use octets 13 and 10 for CR and LF respectively, as is the case for |
|---|
| 690 | some multi-byte character sets, HTTP allows the use of whatever octet sequences are defined by that character set to represent |
|---|
| 691 | the equivalent of CR and LF for line breaks. This flexibility regarding line breaks applies only to text media in the entity-body; |
|---|
| 692 | a bare CR or LF <em class="bcp14">MUST NOT</em> be substituted for CRLF within any of the HTTP control structures (such as header fields and multipart boundaries). |
|---|
| 693 | </p> |
|---|
| 694 | <p id="rfc.section.2.3.1.p.3">If an entity-body is encoded with a content-coding, the underlying data <em class="bcp14">MUST</em> be in a form defined above prior to being encoded. |
|---|
| 695 | </p> |
|---|
| 696 | <p id="rfc.section.2.3.1.p.4">The "charset" parameter is used with some media types to define the character set (<a href="#character.sets" title="Character Sets">Section 2.1</a>) of the data. When no explicit charset parameter is provided by the sender, media subtypes of the "text" type are defined |
|---|
| 697 | to have a default charset value of "ISO-8859-1" when received via HTTP. Data in character sets other than "ISO-8859-1" or |
|---|
| 698 | its subsets <em class="bcp14">MUST</em> be labeled with an appropriate charset value. See <a href="#missing.charset" title="Missing Charset">Section 2.1.1</a> for compatibility problems. |
|---|
| 699 | </p> |
|---|
| 700 | <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a> <a id="multipart.types" href="#multipart.types">Multipart Types</a></h3> |
|---|
| 701 | <p id="rfc.section.2.3.2.p.1">MIME provides for a number of "multipart" types -- encapsulations of one or more entities within a single message-body. All |
|---|
| 702 | multipart types share a common syntax, as defined in <a href="http://tools.ietf.org/html/rfc2046#section-5.1.1">Section 5.1.1</a> of <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, and <em class="bcp14">MUST</em> include a boundary parameter as part of the media type value. The message body is itself a protocol element and <em class="bcp14">MUST</em> therefore use only CRLF to represent line breaks between body-parts. Unlike in RFC 2046, the epilogue of any multipart message <em class="bcp14">MUST</em> be empty; HTTP applications <em class="bcp14">MUST NOT</em> transmit the epilogue (even if the original multipart contains an epilogue). These restrictions exist in order to preserve |
|---|
| 703 | the self-delimiting nature of a multipart message-body, wherein the "end" of the message-body is indicated by the ending multipart |
|---|
| 704 | boundary. |
|---|
| 705 | </p> |
|---|
| 706 | <p id="rfc.section.2.3.2.p.2">In general, HTTP treats a multipart message-body no differently than any other media type: strictly as payload. The one exception |
|---|
| 707 | is the "multipart/byteranges" type (<a href="p5-range.html#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a> of <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) when it appears in a 206 (Partial Content) response. |
|---|
| 708 | </p> |
|---|
| 709 | <p id="rfc.section.2.3.2.p.3">In general, an HTTP user agent <em class="bcp14">SHOULD</em> follow the same or similar behavior as a MIME user agent would upon receipt of a multipart type. If an application receives |
|---|
| 710 | an unrecognized multipart subtype, the application <em class="bcp14">MUST</em> treat it as being equivalent to "multipart/mixed". |
|---|
| 711 | </p> |
|---|
| 712 | <dl class="empty"> |
|---|
| 713 | <dd> <b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request |
|---|
| 714 | method, as described in <a href="#RFC1867" id="rfc.xref.RFC1867.1"><cite title="Form-based File Upload in HTML">[RFC1867]</cite></a>. |
|---|
| 715 | </dd> |
|---|
| 716 | </dl> |
|---|
| 717 | <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a> <a id="quality.values" href="#quality.values">Quality Values</a></h2> |
|---|
| 718 | <p id="rfc.section.2.4.p.1">HTTP content negotiation (<a href="#content.negotiation" title="Content Negotiation">Section 4</a>) uses short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight |
|---|
| 719 | is normalized to a real number in the range 0 through 1, where 0 is the minimum and 1 the maximum value. If a parameter has |
|---|
| 720 | a quality value of 0, then content with this parameter is `not acceptable' for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion. |
|---|
| 721 | </p> |
|---|
| 722 | <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.10"></span> qvalue = ( "0" [ "." 0*3DIGIT ] ) |
|---|
| 723 | | ( "1" [ "." 0*3("0") ] ) |
|---|
| 724 | </pre><p id="rfc.section.2.4.p.3">"Quality values" is a misnomer, since these values merely represent relative degradation in desired quality.</p> |
|---|
| 725 | <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a> <a id="language.tags" href="#language.tags">Language Tags</a></h2> |
|---|
| 726 | <p id="rfc.section.2.5.p.1">A language tag identifies a natural language spoken, written, or otherwise conveyed by human beings for communication of information |
|---|
| 727 | to other human beings. Computer languages are explicitly excluded. HTTP uses language tags within the Accept-Language and |
|---|
| 728 | Content-Language fields. |
|---|
| 729 | </p> |
|---|
| 730 | <p id="rfc.section.2.5.p.2">The syntax and registry of HTTP language tags is the same as that defined by <a href="#RFC1766" id="rfc.xref.RFC1766.1"><cite title="Tags for the Identification of Languages">[RFC1766]</cite></a>. In summary, a language tag is composed of 1 or more parts: A primary language tag and a possibly empty series of subtags: |
|---|
| 731 | </p> |
|---|
| 732 | <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span> language-tag = primary-tag *( "-" subtag ) |
|---|
| 733 | primary-tag = 1*8ALPHA |
|---|
| 734 | subtag = 1*8ALPHA |
|---|
| 735 | </pre><p id="rfc.section.2.5.p.4">White space is not allowed within the tag and all tags are case-insensitive. The name space of language tags is administered |
|---|
| 736 | by the IANA. Example tags include: |
|---|
| 737 | </p> |
|---|
| 738 | <div id="rfc.figure.u.7"></div><pre class="text"> en, en-US, en-cockney, i-cherokee, x-pig-latin |
|---|
| 739 | </pre><p id="rfc.section.2.5.p.6">where any two-letter primary-tag is an ISO-639 language abbreviation and any two-letter initial subtag is an ISO-3166 country |
|---|
| 740 | code. (The last three tags above are not registered tags; all but the last are examples of tags which could be registered |
|---|
| 741 | in future.) |
|---|
| 742 | </p> |
|---|
| 743 | <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="entity" href="#entity">Entity</a></h1> |
|---|
| 744 | <p id="rfc.section.3.p.1">Request and Response messages <em class="bcp14">MAY</em> transfer an entity if not otherwise restricted by the request method or response status code. An entity consists of entity-header |
|---|
| 745 | fields and an entity-body, although some responses will only include the entity-headers. |
|---|
| 746 | </p> |
|---|
| 747 | <p id="rfc.section.3.p.2">In this section, both sender and recipient refer to either the client or the server, depending on who sends and who receives |
|---|
| 748 | the entity. |
|---|
| 749 | </p> |
|---|
| 750 | <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a> <a id="entity.header.fields" href="#entity.header.fields">Entity Header Fields</a></h2> |
|---|
| 751 | <p id="rfc.section.3.1.p.1">Entity-header fields define metainformation about the entity-body or, if no body is present, about the resource identified |
|---|
| 752 | by the request. Some of this metainformation is <em class="bcp14">OPTIONAL</em>; some might be <em class="bcp14">REQUIRED</em> by portions of this specification. |
|---|
| 753 | </p> |
|---|
| 754 | <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span> entity-header = Allow ; <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#header.allow" title="Allow">Section 10.1</a> |
|---|
| 755 | | Content-Encoding ; <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section 5.5</a> |
|---|
| 756 | | Content-Language ; <a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section 5.6</a> |
|---|
| 757 | | Content-Length ; <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.content-length" title="Content-Length">Section 8.2</a> |
|---|
| 758 | | Content-Location ; <a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section 5.7</a> |
|---|
| 759 | | Content-MD5 ; <a href="#header.content-md5" id="rfc.xref.header.content-md5.1" title="Content-MD5">Section 5.8</a> |
|---|
| 760 | | Content-Range ; <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a> |
|---|
| 761 | | Content-Type ; <a href="#header.content-type" id="rfc.xref.header.content-type.2" title="Content-Type">Section 5.9</a> |
|---|
| 762 | | Expires ; <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.expires" title="Expires">Section 3.3</a> |
|---|
| 763 | | Last-Modified ; <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 6.6</a> |
|---|
| 764 | | extension-header |
|---|
| 765 | |
|---|
| 766 | extension-header = message-header |
|---|
| 767 | </pre><p id="rfc.section.3.1.p.3">The extension-header mechanism allows additional entity-header fields to be defined without changing the protocol, but these |
|---|
| 768 | fields cannot be assumed to be recognizable by the recipient. Unrecognized header fields <em class="bcp14">SHOULD</em> be ignored by the recipient and <em class="bcp14">MUST</em> be forwarded by transparent proxies. |
|---|
| 769 | </p> |
|---|
| 770 | <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="entity.body" href="#entity.body">Entity Body</a></h2> |
|---|
| 771 | <p id="rfc.section.3.2.p.1">The entity-body (if any) sent with an HTTP request or response is in a format and encoding defined by the entity-header fields.</p> |
|---|
| 772 | <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.16"></span> entity-body = *OCTET |
|---|
| 773 | </pre><p id="rfc.section.3.2.p.3">An entity-body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure |
|---|
| 774 | safe and proper transfer of the message. |
|---|
| 775 | </p> |
|---|
| 776 | <h3 id="rfc.section.3.2.1"><a href="#rfc.section.3.2.1">3.2.1</a> <a id="type" href="#type">Type</a></h3> |
|---|
| 777 | <p id="rfc.section.3.2.1.p.1">When an entity-body is included with a message, the data type of that body is determined via the header fields Content-Type |
|---|
| 778 | and Content-Encoding. These define a two-layer, ordered encoding model: |
|---|
| 779 | </p> |
|---|
| 780 | <div id="rfc.figure.u.10"></div><pre class="text"> entity-body := Content-Encoding( Content-Type( data ) ) |
|---|
| 781 | </pre><p id="rfc.section.3.2.1.p.3">Content-Type specifies the media type of the underlying data. Content-Encoding may be used to indicate any additional content |
|---|
| 782 | codings applied to the data, usually for the purpose of data compression, that are a property of the requested resource. There |
|---|
| 783 | is no default encoding. |
|---|
| 784 | </p> |
|---|
| 785 | <p id="rfc.section.3.2.1.p.4">Any HTTP/1.1 message containing an entity-body <em class="bcp14">SHOULD</em> include a Content-Type header field defining the media type of that body. If and only if the media type is not given by a |
|---|
| 786 | Content-Type field, the recipient <em class="bcp14">MAY</em> attempt to guess the media type via inspection of its content and/or the name extension(s) of the URI used to identify the |
|---|
| 787 | resource. If the media type remains unknown, the recipient <em class="bcp14">SHOULD</em> treat it as type "application/octet-stream". |
|---|
| 788 | </p> |
|---|
| 789 | <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a> <a id="entity.length" href="#entity.length">Entity Length</a></h3> |
|---|
| 790 | <p id="rfc.section.3.2.2.p.1">The entity-length of a message is the length of the message-body before any transfer-codings have been applied. <a href="p1-messaging.html#message.length" title="Message Length">Section 4.4</a> of <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> defines how the transfer-length of a message-body is determined. |
|---|
| 791 | </p> |
|---|
| 792 | <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="content.negotiation" href="#content.negotiation">Content Negotiation</a></h1> |
|---|
| 793 | <p id="rfc.section.4.p.1">Most HTTP responses include an entity which contains information for interpretation by a human user. Naturally, it is desirable |
|---|
| 794 | to supply the user with the "best available" entity corresponding to the request. Unfortunately for servers and caches, not |
|---|
| 795 | all users have the same preferences for what is "best," and not all user agents are equally capable of rendering all entity |
|---|
| 796 | types. For that reason, HTTP has provisions for several mechanisms for "content negotiation" -- the process of selecting the |
|---|
| 797 | best representation for a given response when there are multiple representations available. |
|---|
| 798 | </p> |
|---|
| 799 | <dl class="empty"> |
|---|
| 800 | <dd> <b>Note:</b> This is not called "format negotiation" because the alternate representations may be of the same media type, but use different |
|---|
| 801 | capabilities of that type, be in different languages, etc. |
|---|
| 802 | </dd> |
|---|
| 803 | </dl> |
|---|
| 804 | <p id="rfc.section.4.p.2">Any response containing an entity-body <em class="bcp14">MAY</em> be subject to negotiation, including error responses. |
|---|
| 805 | </p> |
|---|
| 806 | <p id="rfc.section.4.p.3">There are two kinds of content negotiation which are possible in HTTP: server-driven and agent-driven negotiation. These two |
|---|
| 807 | kinds of negotiation are orthogonal and thus may be used separately or in combination. One method of combination, referred |
|---|
| 808 | to as transparent negotiation, occurs when a cache uses the agent-driven negotiation information provided by the origin server |
|---|
| 809 | in order to provide server-driven negotiation for subsequent requests. |
|---|
| 810 | </p> |
|---|
| 811 | <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a> <a id="server-driven.negotiation" href="#server-driven.negotiation">Server-driven Negotiation</a></h2> |
|---|
| 812 | <p id="rfc.section.4.1.p.1">If the selection of the best representation for a response is made by an algorithm located at the server, it is called server-driven |
|---|
| 813 | negotiation. Selection is based on the available representations of the response (the dimensions over which it can vary; e.g. |
|---|
| 814 | language, content-coding, etc.) and the contents of particular header fields in the request message or on other information |
|---|
| 815 | pertaining to the request (such as the network address of the client). |
|---|
| 816 | </p> |
|---|
| 817 | <p id="rfc.section.4.1.p.2">Server-driven negotiation is advantageous when the algorithm for selecting from among the available representations is difficult |
|---|
| 818 | to describe to the user agent, or when the server desires to send its "best guess" to the client along with the first response |
|---|
| 819 | (hoping to avoid the round-trip delay of a subsequent request if the "best guess" is good enough for the user). In order to |
|---|
| 820 | improve the server's guess, the user agent <em class="bcp14">MAY</em> include request header fields (Accept, Accept-Language, Accept-Encoding, etc.) which describe its preferences for such a response. |
|---|
| 821 | </p> |
|---|
| 822 | <p id="rfc.section.4.1.p.3">Server-driven negotiation has disadvantages: </p> |
|---|
| 823 | <ol> |
|---|
| 824 | <li>It is impossible for the server to accurately determine what might be "best" for any given user, since that would require |
|---|
| 825 | complete knowledge of both the capabilities of the user agent and the intended use for the response (e.g., does the user want |
|---|
| 826 | to view it on screen or print it on paper?). |
|---|
| 827 | </li> |
|---|
| 828 | <li>Having the user agent describe its capabilities in every request can be both very inefficient (given that only a small percentage |
|---|
| 829 | of responses have multiple representations) and a potential violation of the user's privacy. |
|---|
| 830 | </li> |
|---|
| 831 | <li>It complicates the implementation of an origin server and the algorithms for generating responses to a request.</li> |
|---|
| 832 | <li>It may limit a public cache's ability to use the same response for multiple user's requests.</li> |
|---|
| 833 | </ol> |
|---|
| 834 | <p id="rfc.section.4.1.p.4">HTTP/1.1 includes the following request-header fields for enabling server-driven negotiation through description of user agent |
|---|
| 835 | capabilities and user preferences: Accept (<a href="#header.accept" id="rfc.xref.header.accept.2" title="Accept">Section 5.1</a>), Accept-Charset (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.1" title="Accept-Charset">Section 5.2</a>), Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.2" title="Accept-Encoding">Section 5.3</a>), Accept-Language (<a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section 5.4</a>), and User-Agent (<a href="p2-semantics.html#header.user-agent" title="User-Agent">Section 10.9</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). However, an origin server is not limited to these dimensions and <em class="bcp14">MAY</em> vary the response based on any aspect of the request, including information outside the request-header fields or within extension |
|---|
| 836 | header fields not defined by this specification. |
|---|
| 837 | </p> |
|---|
| 838 | <p id="rfc.section.4.1.p.5">The Vary header field (<a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) can be used to express the parameters the server uses to select a representation that is subject to server-driven negotiation. |
|---|
| 839 | </p> |
|---|
| 840 | <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a> <a id="agent-driven.negotiation" href="#agent-driven.negotiation">Agent-driven Negotiation</a></h2> |
|---|
| 841 | <p id="rfc.section.4.2.p.1">With agent-driven negotiation, selection of the best representation for a response is performed by the user agent after receiving |
|---|
| 842 | an initial response from the origin server. Selection is based on a list of the available representations of the response |
|---|
| 843 | included within the header fields or entity-body of the initial response, with each representation identified by its own URI. |
|---|
| 844 | Selection from among the representations may be performed automatically (if the user agent is capable of doing so) or manually |
|---|
| 845 | by the user selecting from a generated (possibly hypertext) menu. |
|---|
| 846 | </p> |
|---|
| 847 | <p id="rfc.section.4.2.p.2">Agent-driven negotiation is advantageous when the response would vary over commonly-used dimensions (such as type, language, |
|---|
| 848 | or encoding), when the origin server is unable to determine a user agent's capabilities from examining the request, and generally |
|---|
| 849 | when public caches are used to distribute server load and reduce network usage. |
|---|
| 850 | </p> |
|---|
| 851 | <p id="rfc.section.4.2.p.3">Agent-driven negotiation suffers from the disadvantage of needing a second request to obtain the best alternate representation. |
|---|
| 852 | This second request is only efficient when caching is used. In addition, this specification does not define any mechanism |
|---|
| 853 | for supporting automatic selection, though it also does not prevent any such mechanism from being developed as an extension |
|---|
| 854 | and used within HTTP/1.1. |
|---|
| 855 | </p> |
|---|
| 856 | <p id="rfc.section.4.2.p.4">HTTP/1.1 defines the 300 (Multiple Choices) and 406 (Not Acceptable) status codes for enabling agent-driven negotiation when |
|---|
| 857 | the server is unwilling or unable to provide a varying response using server-driven negotiation. |
|---|
| 858 | </p> |
|---|
| 859 | <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a> <a id="transparent.negotiation" href="#transparent.negotiation">Transparent Negotiation</a></h2> |
|---|
| 860 | <p id="rfc.section.4.3.p.1">Transparent negotiation is a combination of both server-driven and agent-driven negotiation. When a cache is supplied with |
|---|
| 861 | a form of the list of available representations of the response (as in agent-driven negotiation) and the dimensions of variance |
|---|
| 862 | are completely understood by the cache, then the cache becomes capable of performing server-driven negotiation on behalf of |
|---|
| 863 | the origin server for subsequent requests on that resource. |
|---|
| 864 | </p> |
|---|
| 865 | <p id="rfc.section.4.3.p.2">Transparent negotiation has the advantage of distributing the negotiation work that would otherwise be required of the origin |
|---|
| 866 | server and also removing the second request delay of agent-driven negotiation when the cache is able to correctly guess the |
|---|
| 867 | right response. |
|---|
| 868 | </p> |
|---|
| 869 | <p id="rfc.section.4.3.p.3">This specification does not define any mechanism for transparent negotiation, though it also does not prevent any such mechanism |
|---|
| 870 | from being developed as an extension that could be used within HTTP/1.1. |
|---|
| 871 | </p> |
|---|
| 872 | <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="header.fields" href="#header.fields">Header Field Definitions</a></h1> |
|---|
| 873 | <p id="rfc.section.5.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to the payload of messages.</p> |
|---|
| 874 | <p id="rfc.section.5.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who |
|---|
| 875 | receives the entity. |
|---|
| 876 | </p> |
|---|
| 877 | <div id="rfc.iref.a.1"></div> |
|---|
| 878 | <div id="rfc.iref.h.1"></div> |
|---|
| 879 | <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a> <a id="header.accept" href="#header.accept">Accept</a></h2> |
|---|
| 880 | <p id="rfc.section.5.1.p.1">The Accept request-header field can be used to specify certain media types which are acceptable for the response. Accept headers |
|---|
| 881 | can be used to indicate that the request is specifically limited to a small set of desired types, as in the case of a request |
|---|
| 882 | for an in-line image. |
|---|
| 883 | </p> |
|---|
| 884 | <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span> Accept = "Accept" ":" |
|---|
| 885 | #( media-range [ accept-params ] ) |
|---|
| 886 | |
|---|
| 887 | media-range = ( "*/*" |
|---|
| 888 | | ( type "/" "*" ) |
|---|
| 889 | | ( type "/" subtype ) |
|---|
| 890 | ) *( ";" parameter ) |
|---|
| 891 | accept-params = ";" "q" "=" qvalue *( accept-extension ) |
|---|
| 892 | accept-extension = ";" token [ "=" ( token | quoted-string ) ] |
|---|
| 893 | </pre><p id="rfc.section.5.1.p.3">The asterisk "*" character is used to group media types into ranges, with "*/*" indicating all media types and "type/*" indicating |
|---|
| 894 | all subtypes of that type. The media-range <em class="bcp14">MAY</em> include media type parameters that are applicable to that range. |
|---|
| 895 | </p> |
|---|
| 896 | <p id="rfc.section.5.1.p.4">Each media-range <em class="bcp14">MAY</em> be followed by one or more accept-params, beginning with the "q" parameter for indicating a relative quality factor. The first |
|---|
| 897 | "q" parameter (if any) separates the media-range parameter(s) from the accept-params. Quality factors allow the user or user |
|---|
| 898 | agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="#quality.values" title="Quality Values">Section 2.4</a>). The default value is q=1. |
|---|
| 899 | </p> |
|---|
| 900 | <dl class="empty"> |
|---|
| 901 | <dd> <b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice. |
|---|
| 902 | Although this prevents any media type parameter named "q" from being used with a media range, such an event is believed to |
|---|
| 903 | be unlikely given the lack of any "q" parameters in the IANA media type registry and the rare usage of any media type parameters |
|---|
| 904 | in Accept. Future media types are discouraged from registering any parameter named "q". |
|---|
| 905 | </dd> |
|---|
| 906 | </dl> |
|---|
| 907 | <p id="rfc.section.5.1.p.5">The example</p> |
|---|
| 908 | <div id="rfc.figure.u.12"></div><pre class="text"> Accept: audio/*; q=0.2, audio/basic |
|---|
| 909 | </pre><p id="rfc.section.5.1.p.7"> <em class="bcp14">SHOULD</em> be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in |
|---|
| 910 | quality." |
|---|
| 911 | </p> |
|---|
| 912 | <p id="rfc.section.5.1.p.8">If no Accept header field is present, then it is assumed that the client accepts all media types. If an Accept header field |
|---|
| 913 | is present, and if the server cannot send a response which is acceptable according to the combined Accept field value, then |
|---|
| 914 | the server <em class="bcp14">SHOULD</em> send a 406 (not acceptable) response. |
|---|
| 915 | </p> |
|---|
| 916 | <p id="rfc.section.5.1.p.9">A more elaborate example is</p> |
|---|
| 917 | <div id="rfc.figure.u.13"></div><pre class="text"> Accept: text/plain; q=0.5, text/html, |
|---|
| 918 | text/x-dvi; q=0.8, text/x-c |
|---|
| 919 | </pre><p id="rfc.section.5.1.p.11">Verbally, this would be interpreted as "text/html and text/x-c are the preferred media types, but if they do not exist, then |
|---|
| 920 | send the text/x-dvi entity, and if that does not exist, send the text/plain entity." |
|---|
| 921 | </p> |
|---|
| 922 | <p id="rfc.section.5.1.p.12">Media ranges can be overridden by more specific media ranges or specific media types. If more than one media range applies |
|---|
| 923 | to a given type, the most specific reference has precedence. For example, |
|---|
| 924 | </p> |
|---|
| 925 | <div id="rfc.figure.u.14"></div><pre class="text"> Accept: text/*, text/html, text/html;level=1, */* |
|---|
| 926 | </pre><p id="rfc.section.5.1.p.14">have the following precedence:</p> |
|---|
| 927 | <div id="rfc.figure.u.15"></div><pre class="text"> 1) text/html;level=1 |
|---|
| 928 | 2) text/html |
|---|
| 929 | 3) text/* |
|---|
| 930 | 4) */* |
|---|
| 931 | </pre><p id="rfc.section.5.1.p.16">The media type quality factor associated with a given type is determined by finding the media range with the highest precedence |
|---|
| 932 | which matches that type. For example, |
|---|
| 933 | </p> |
|---|
| 934 | <div id="rfc.figure.u.16"></div><pre class="text"> Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1, |
|---|
| 935 | text/html;level=2;q=0.4, */*;q=0.5 |
|---|
| 936 | </pre><p id="rfc.section.5.1.p.18">would cause the following values to be associated:</p> |
|---|
| 937 | <div id="rfc.figure.u.17"></div><pre class="text"> text/html;level=1 = 1 |
|---|
| 938 | text/html = 0.7 |
|---|
| 939 | text/plain = 0.3 |
|---|
| 940 | image/jpeg = 0.5 |
|---|
| 941 | text/html;level=2 = 0.4 |
|---|
| 942 | text/html;level=3 = 0.7 |
|---|
| 943 | </pre><p id="rfc.section.5.1.p.20"> <b>Note:</b> A user agent might be provided with a default set of quality values for certain media ranges. However, unless the user agent |
|---|
| 944 | is a closed system which cannot interact with other rendering agents, this default set ought to be configurable by the user. |
|---|
| 945 | </p> |
|---|
| 946 | <div id="rfc.iref.a.2"></div> |
|---|
| 947 | <div id="rfc.iref.h.2"></div> |
|---|
| 948 | <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a> <a id="header.accept-charset" href="#header.accept-charset">Accept-Charset</a></h2> |
|---|
| 949 | <p id="rfc.section.5.2.p.1">The Accept-Charset request-header field can be used to indicate what character sets are acceptable for the response. This |
|---|
| 950 | field allows clients capable of understanding more comprehensive or special-purpose character sets to signal that capability |
|---|
| 951 | to a server which is capable of representing documents in those character sets. |
|---|
| 952 | </p> |
|---|
| 953 | <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.21"></span> Accept-Charset = "Accept-Charset" ":" |
|---|
| 954 | 1#( ( charset | "*" )[ ";" "q" "=" qvalue ] ) |
|---|
| 955 | </pre><p id="rfc.section.5.2.p.3">Character set values are described in <a href="#character.sets" title="Character Sets">Section 2.1</a>. Each charset <em class="bcp14">MAY</em> be given an associated quality value which represents the user's preference for that charset. The default value is q=1. An |
|---|
| 956 | example is |
|---|
| 957 | </p> |
|---|
| 958 | <div id="rfc.figure.u.19"></div><pre class="text"> Accept-Charset: iso-8859-5, unicode-1-1;q=0.8 |
|---|
| 959 | </pre><p id="rfc.section.5.2.p.5">The special value "*", if present in the Accept-Charset field, matches every character set (including ISO-8859-1) which is |
|---|
| 960 | not mentioned elsewhere in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character sets |
|---|
| 961 | not explicitly mentioned get a quality value of 0, except for ISO-8859-1, which gets a quality value of 1 if not explicitly |
|---|
| 962 | mentioned. |
|---|
| 963 | </p> |
|---|
| 964 | <p id="rfc.section.5.2.p.6">If no Accept-Charset header is present, the default is that any character set is acceptable. If an Accept-Charset header is |
|---|
| 965 | present, and if the server cannot send a response which is acceptable according to the Accept-Charset header, then the server <em class="bcp14">SHOULD</em> send an error response with the 406 (not acceptable) status code, though the sending of an unacceptable response is also allowed. |
|---|
| 966 | </p> |
|---|
| 967 | <div id="rfc.iref.a.3"></div> |
|---|
| 968 | <div id="rfc.iref.h.3"></div> |
|---|
| 969 | <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a> <a id="header.accept-encoding" href="#header.accept-encoding">Accept-Encoding</a></h2> |
|---|
| 970 | <p id="rfc.section.5.3.p.1">The Accept-Encoding request-header field is similar to Accept, but restricts the content-codings (<a href="#content.codings" title="Content Codings">Section 2.2</a>) that are acceptable in the response. |
|---|
| 971 | </p> |
|---|
| 972 | <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span> Accept-Encoding = "Accept-Encoding" ":" |
|---|
| 973 | #( codings [ ";" "q" "=" qvalue ] ) |
|---|
| 974 | codings = ( content-coding | "*" ) |
|---|
| 975 | </pre><p id="rfc.section.5.3.p.3">Examples of its use are:</p> |
|---|
| 976 | <div id="rfc.figure.u.21"></div><pre class="text"> Accept-Encoding: compress, gzip |
|---|
| 977 | Accept-Encoding: |
|---|
| 978 | Accept-Encoding: * |
|---|
| 979 | Accept-Encoding: compress;q=0.5, gzip;q=1.0 |
|---|
| 980 | Accept-Encoding: gzip;q=1.0, identity; q=0.5, *;q=0 |
|---|
| 981 | </pre><p id="rfc.section.5.3.p.5">A server tests whether a content-coding is acceptable, according to an Accept-Encoding field, using these rules: </p> |
|---|
| 982 | <ol> |
|---|
| 983 | <li>If the content-coding is one of the content-codings listed in the Accept-Encoding field, then it is acceptable, unless it |
|---|
| 984 | is accompanied by a qvalue of 0. (As defined in <a href="#quality.values" title="Quality Values">Section 2.4</a>, a qvalue of 0 means "not acceptable.") |
|---|
| 985 | </li> |
|---|
| 986 | <li>The special "*" symbol in an Accept-Encoding field matches any available content-coding not explicitly listed in the header |
|---|
| 987 | field. |
|---|
| 988 | </li> |
|---|
| 989 | <li>If multiple content-codings are acceptable, then the acceptable content-coding with the highest non-zero qvalue is preferred.</li> |
|---|
| 990 | <li>The "identity" content-coding is always acceptable, unless specifically refused because the Accept-Encoding field includes |
|---|
| 991 | "identity;q=0", or because the field includes "*;q=0" and does not explicitly include the "identity" content-coding. If the |
|---|
| 992 | Accept-Encoding field-value is empty, then only the "identity" encoding is acceptable. |
|---|
| 993 | </li> |
|---|
| 994 | </ol> |
|---|
| 995 | <p id="rfc.section.5.3.p.6">If an Accept-Encoding field is present in a request, and if the server cannot send a response which is acceptable according |
|---|
| 996 | to the Accept-Encoding header, then the server <em class="bcp14">SHOULD</em> send an error response with the 406 (Not Acceptable) status code. |
|---|
| 997 | </p> |
|---|
| 998 | <p id="rfc.section.5.3.p.7">If no Accept-Encoding field is present in a request, the server <em class="bcp14">MAY</em> assume that the client will accept any content coding. In this case, if "identity" is one of the available content-codings, |
|---|
| 999 | then the server <em class="bcp14">SHOULD</em> use the "identity" content-coding, unless it has additional information that a different content-coding is meaningful to the |
|---|
| 1000 | client. |
|---|
| 1001 | </p> |
|---|
| 1002 | <dl class="empty"> |
|---|
| 1003 | <dd> <b>Note:</b> If the request does not include an Accept-Encoding field, and if the "identity" content-coding is unavailable, then content-codings |
|---|
| 1004 | commonly understood by HTTP/1.0 clients (i.e., "gzip" and "compress") are preferred; some older clients improperly display |
|---|
| 1005 | messages sent with other content-codings. The server might also make this decision based on information about the particular |
|---|
| 1006 | user-agent or client. |
|---|
| 1007 | </dd> |
|---|
| 1008 | <dd> <b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues will |
|---|
| 1009 | not work and are not permitted with x-gzip or x-compress. |
|---|
| 1010 | </dd> |
|---|
| 1011 | </dl> |
|---|
| 1012 | <div id="rfc.iref.a.4"></div> |
|---|
| 1013 | <div id="rfc.iref.h.4"></div> |
|---|
| 1014 | <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a> <a id="header.accept-language" href="#header.accept-language">Accept-Language</a></h2> |
|---|
| 1015 | <p id="rfc.section.5.4.p.1">The Accept-Language request-header field is similar to Accept, but restricts the set of natural languages that are preferred |
|---|
| 1016 | as a response to the request. Language tags are defined in <a href="#language.tags" title="Language Tags">Section 2.5</a>. |
|---|
| 1017 | </p> |
|---|
| 1018 | <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span> Accept-Language = "Accept-Language" ":" |
|---|
| 1019 | 1#( language-range [ ";" "q" "=" qvalue ] ) |
|---|
| 1020 | language-range = ( ( 1*8ALPHA *( "-" 1*8ALPHA ) ) | "*" ) |
|---|
| 1021 | </pre><p id="rfc.section.5.4.p.3">Each language-range <em class="bcp14">MAY</em> be given an associated quality value which represents an estimate of the user's preference for the languages specified by |
|---|
| 1022 | that range. The quality value defaults to "q=1". For example, |
|---|
| 1023 | </p> |
|---|
| 1024 | <div id="rfc.figure.u.23"></div><pre class="text"> Accept-Language: da, en-gb;q=0.8, en;q=0.7 |
|---|
| 1025 | </pre><p id="rfc.section.5.4.p.5">would mean: "I prefer Danish, but will accept British English and other types of English." A language-range matches a language-tag |
|---|
| 1026 | if it exactly equals the tag, or if it exactly equals a prefix of the tag such that the first tag character following the |
|---|
| 1027 | prefix is "-". The special range "*", if present in the Accept-Language field, matches every tag not matched by any other |
|---|
| 1028 | range present in the Accept-Language field. |
|---|
| 1029 | </p> |
|---|
| 1030 | <dl class="empty"> |
|---|
| 1031 | <dd> <b>Note:</b> This use of a prefix matching rule does not imply that language tags are assigned to languages in such a way that it is always |
|---|
| 1032 | true that if a user understands a language with a certain tag, then this user will also understand all languages with tags |
|---|
| 1033 | for which this tag is a prefix. The prefix rule simply allows the use of prefix tags if this is the case. |
|---|
| 1034 | </dd> |
|---|
| 1035 | </dl> |
|---|
| 1036 | <p id="rfc.section.5.4.p.6">The language quality factor assigned to a language-tag by the Accept-Language field is the quality value of the longest language-range |
|---|
| 1037 | in the field that matches the language-tag. If no language-range in the field matches the tag, the language quality factor |
|---|
| 1038 | assigned is 0. If no Accept-Language header is present in the request, the server <em class="bcp14">SHOULD</em> assume that all languages are equally acceptable. If an Accept-Language header is present, then all languages which are assigned |
|---|
| 1039 | a quality factor greater than 0 are acceptable. |
|---|
| 1040 | </p> |
|---|
| 1041 | <p id="rfc.section.5.4.p.7">It might be contrary to the privacy expectations of the user to send an Accept-Language header with the complete linguistic |
|---|
| 1042 | preferences of the user in every request. For a discussion of this issue, see <a href="#privacy.issues.connected.to.accept.headers" title="Privacy Issues Connected to Accept Headers">Section 7.1</a>. |
|---|
| 1043 | </p> |
|---|
| 1044 | <p id="rfc.section.5.4.p.8">As intelligibility is highly dependent on the individual user, it is recommended that client applications make the choice |
|---|
| 1045 | of linguistic preference available to the user. If the choice is not made available, then the Accept-Language header field <em class="bcp14">MUST NOT</em> be given in the request. |
|---|
| 1046 | </p> |
|---|
| 1047 | <dl class="empty"> |
|---|
| 1048 | <dd> <b>Note:</b> When making the choice of linguistic preference available to the user, we remind implementors of the fact that users are not |
|---|
| 1049 | familiar with the details of language matching as described above, and should provide appropriate guidance. As an example, |
|---|
| 1050 | users might assume that on selecting "en-gb", they will be served any kind of English document if British English is not available. |
|---|
| 1051 | A user agent might suggest in such a case to add "en" to get the best matching behavior. |
|---|
| 1052 | </dd> |
|---|
| 1053 | </dl> |
|---|
| 1054 | <div id="rfc.iref.c.2"></div> |
|---|
| 1055 | <div id="rfc.iref.h.5"></div> |
|---|
| 1056 | <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a> <a id="header.content-encoding" href="#header.content-encoding">Content-Encoding</a></h2> |
|---|
| 1057 | <p id="rfc.section.5.5.p.1">The Content-Encoding entity-header field is used as a modifier to the media-type. When present, its value indicates what additional |
|---|
| 1058 | content codings have been applied to the entity-body, and thus what decoding mechanisms must be applied in order to obtain |
|---|
| 1059 | the media-type referenced by the Content-Type header field. Content-Encoding is primarily used to allow a document to be compressed |
|---|
| 1060 | without losing the identity of its underlying media type. |
|---|
| 1061 | </p> |
|---|
| 1062 | <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.26"></span> Content-Encoding = "Content-Encoding" ":" 1#content-coding |
|---|
| 1063 | </pre><p id="rfc.section.5.5.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section 2.2</a>. An example of its use is |
|---|
| 1064 | </p> |
|---|
| 1065 | <div id="rfc.figure.u.25"></div><pre class="text"> Content-Encoding: gzip |
|---|
| 1066 | </pre><p id="rfc.section.5.5.p.5">The content-coding is a characteristic of the entity identified by the Request-URI. Typically, the entity-body is stored with |
|---|
| 1067 | this encoding and is only decoded before rendering or analogous usage. However, a non-transparent proxy <em class="bcp14">MAY</em> modify the content-coding if the new coding is known to be acceptable to the recipient, unless the "no-transform" cache-control |
|---|
| 1068 | directive is present in the message. |
|---|
| 1069 | </p> |
|---|
| 1070 | <p id="rfc.section.5.5.p.6">If the content-coding of an entity is not "identity", then the response <em class="bcp14">MUST</em> include a Content-Encoding entity-header (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.3" title="Content-Encoding">Section 5.5</a>) that lists the non-identity content-coding(s) used. |
|---|
| 1071 | </p> |
|---|
| 1072 | <p id="rfc.section.5.5.p.7">If the content-coding of an entity in a request message is not acceptable to the origin server, the server <em class="bcp14">SHOULD</em> respond with a status code of 415 (Unsupported Media Type). |
|---|
| 1073 | </p> |
|---|
| 1074 | <p id="rfc.section.5.5.p.8">If multiple encodings have been applied to an entity, the content codings <em class="bcp14">MUST</em> be listed in the order in which they were applied. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other entity-header fields not defined by this specification. |
|---|
| 1075 | </p> |
|---|
| 1076 | <div id="rfc.iref.c.3"></div> |
|---|
| 1077 | <div id="rfc.iref.h.6"></div> |
|---|
| 1078 | <h2 id="rfc.section.5.6"><a href="#rfc.section.5.6">5.6</a> <a id="header.content-language" href="#header.content-language">Content-Language</a></h2> |
|---|
| 1079 | <p id="rfc.section.5.6.p.1">The Content-Language entity-header field describes the natural language(s) of the intended audience for the enclosed entity. |
|---|
| 1080 | Note that this might not be equivalent to all the languages used within the entity-body. |
|---|
| 1081 | </p> |
|---|
| 1082 | <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.27"></span> Content-Language = "Content-Language" ":" 1#language-tag |
|---|
| 1083 | </pre><p id="rfc.section.5.6.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section 2.5</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate entities according to the user's |
|---|
| 1084 | own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate field is |
|---|
| 1085 | </p> |
|---|
| 1086 | <div id="rfc.figure.u.27"></div><pre class="text"> Content-Language: da |
|---|
| 1087 | </pre><p id="rfc.section.5.6.p.5">If no Content-Language is specified, the default is that the content is intended for all language audiences. This might mean |
|---|
| 1088 | that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language |
|---|
| 1089 | it is intended. |
|---|
| 1090 | </p> |
|---|
| 1091 | <p id="rfc.section.5.6.p.6">Multiple languages <em class="bcp14">MAY</em> be listed for content that is intended for multiple audiences. For example, a rendition of the "Treaty of Waitangi," presented |
|---|
| 1092 | simultaneously in the original Maori and English versions, would call for |
|---|
| 1093 | </p> |
|---|
| 1094 | <div id="rfc.figure.u.28"></div><pre class="text"> Content-Language: mi, en |
|---|
| 1095 | </pre><p id="rfc.section.5.6.p.8">However, just because multiple languages are present within an entity does not mean that it is intended for multiple linguistic |
|---|
| 1096 | audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin," which is clearly intended |
|---|
| 1097 | to be used by an English-literate audience. In this case, the Content-Language would properly only include "en". |
|---|
| 1098 | </p> |
|---|
| 1099 | <p id="rfc.section.5.6.p.9">Content-Language <em class="bcp14">MAY</em> be applied to any media type -- it is not limited to textual documents. |
|---|
| 1100 | </p> |
|---|
| 1101 | <div id="rfc.iref.c.4"></div> |
|---|
| 1102 | <div id="rfc.iref.h.7"></div> |
|---|
| 1103 | <h2 id="rfc.section.5.7"><a href="#rfc.section.5.7">5.7</a> <a id="header.content-location" href="#header.content-location">Content-Location</a></h2> |
|---|
| 1104 | <p id="rfc.section.5.7.p.1">The Content-Location entity-header field <em class="bcp14">MAY</em> be used to supply the resource location for the entity enclosed in the message when that entity is accessible from a location |
|---|
| 1105 | separate from the requested resource's URI. A server <em class="bcp14">SHOULD</em> provide a Content-Location for the variant corresponding to the response entity; especially in the case where a resource has |
|---|
| 1106 | multiple entities associated with it, and those entities actually have separate locations by which they might be individually |
|---|
| 1107 | accessed, the server <em class="bcp14">SHOULD</em> provide a Content-Location for the particular variant which is returned. |
|---|
| 1108 | </p> |
|---|
| 1109 | <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.28"></span> Content-Location = "Content-Location" ":" |
|---|
| 1110 | ( absoluteURI | relativeURI ) |
|---|
| 1111 | </pre><p id="rfc.section.5.7.p.3">The value of Content-Location also defines the base URI for the entity.</p> |
|---|
| 1112 | <p id="rfc.section.5.7.p.4">The Content-Location value is not a replacement for the original requested URI; it is only a statement of the location of |
|---|
| 1113 | the resource corresponding to this particular entity at the time of the request. Future requests <em class="bcp14">MAY</em> specify the Content-Location URI as the request-URI if the desire is to identify the source of that particular entity. |
|---|
| 1114 | </p> |
|---|
| 1115 | <p id="rfc.section.5.7.p.5">A cache cannot assume that an entity with a Content-Location different from the URI used to retrieve it can be used to respond |
|---|
| 1116 | to later requests on that Content-Location URI. However, the Content-Location can be used to differentiate between multiple |
|---|
| 1117 | entities retrieved from a single requested resource, as described in <a href="p6-cache.html#caching.negotiated.responses" title="Caching Negotiated Responses">Section 2.6</a> of <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. |
|---|
| 1118 | </p> |
|---|
| 1119 | <p id="rfc.section.5.7.p.6">If the Content-Location is a relative URI, the relative URI is interpreted relative to the Request-URI.</p> |
|---|
| 1120 | <p id="rfc.section.5.7.p.7">The meaning of the Content-Location header in PUT or POST requests is undefined; servers are free to ignore it in those cases.</p> |
|---|
| 1121 | <div id="rfc.iref.c.5"></div> |
|---|
| 1122 | <div id="rfc.iref.h.8"></div> |
|---|
| 1123 | <h2 id="rfc.section.5.8"><a href="#rfc.section.5.8">5.8</a> <a id="header.content-md5" href="#header.content-md5">Content-MD5</a></h2> |
|---|
| 1124 | <p id="rfc.section.5.8.p.1">The Content-MD5 entity-header field, as defined in <a href="#RFC1864" id="rfc.xref.RFC1864.1"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>, is an MD5 digest of the entity-body for the purpose of providing an end-to-end message integrity check (MIC) of the entity-body. |
|---|
| 1125 | (Note: a MIC is good for detecting accidental modification of the entity-body in transit, but is not proof against malicious |
|---|
| 1126 | attacks.) |
|---|
| 1127 | </p> |
|---|
| 1128 | <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span> Content-MD5 = "Content-MD5" ":" md5-digest |
|---|
| 1129 | md5-digest = <base64 of 128 bit MD5 digest as per <a href="#RFC1864" id="rfc.xref.RFC1864.2"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>> |
|---|
| 1130 | </pre><p id="rfc.section.5.8.p.3">The Content-MD5 header field <em class="bcp14">MAY</em> be generated by an origin server or client to function as an integrity check of the entity-body. Only origin servers or clients <em class="bcp14">MAY</em> generate the Content-MD5 header field; proxies and gateways <em class="bcp14">MUST NOT</em> generate it, as this would defeat its value as an end-to-end integrity check. Any recipient of the entity-body, including |
|---|
| 1131 | gateways and proxies, <em class="bcp14">MAY</em> check that the digest value in this header field matches that of the entity-body as received. |
|---|
| 1132 | </p> |
|---|
| 1133 | <p id="rfc.section.5.8.p.4">The MD5 digest is computed based on the content of the entity-body, including any content-coding that has been applied, but |
|---|
| 1134 | not including any transfer-encoding applied to the message-body. If the message is received with a transfer-encoding, that |
|---|
| 1135 | encoding <em class="bcp14">MUST</em> be removed prior to checking the Content-MD5 value against the received entity. |
|---|
| 1136 | </p> |
|---|
| 1137 | <p id="rfc.section.5.8.p.5">This has the result that the digest is computed on the octets of the entity-body exactly as, and in the order that, they would |
|---|
| 1138 | be sent if no transfer-encoding were being applied. |
|---|
| 1139 | </p> |
|---|
| 1140 | <p id="rfc.section.5.8.p.6">HTTP extends RFC 1864 to permit the digest to be computed for MIME composite media-types (e.g., multipart/* and message/rfc822), |
|---|
| 1141 | but this does not change how the digest is computed as defined in the preceding paragraph. |
|---|
| 1142 | </p> |
|---|
| 1143 | <p id="rfc.section.5.8.p.7">There are several consequences of this. The entity-body for composite types <em class="bcp14">MAY</em> contain many body-parts, each with its own MIME and HTTP headers (including Content-MD5, Content-Transfer-Encoding, and Content-Encoding |
|---|
| 1144 | headers). If a body-part has a Content-Transfer-Encoding or Content-Encoding header, it is assumed that the content of the |
|---|
| 1145 | body-part has had the encoding applied, and the body-part is included in the Content-MD5 digest as is -- i.e., after the application. |
|---|
| 1146 | The Transfer-Encoding header field is not allowed within body-parts. |
|---|
| 1147 | </p> |
|---|
| 1148 | <p id="rfc.section.5.8.p.8">Conversion of all line breaks to CRLF <em class="bcp14">MUST NOT</em> be done before computing or checking the digest: the line break convention used in the text actually transmitted <em class="bcp14">MUST</em> be left unaltered when computing the digest. |
|---|
| 1149 | </p> |
|---|
| 1150 | <dl class="empty"> |
|---|
| 1151 | <dd> <b>Note:</b> while the definition of Content-MD5 is exactly the same for HTTP as in RFC 1864 for MIME entity-bodies, there are several |
|---|
| 1152 | ways in which the application of Content-MD5 to HTTP entity-bodies differs from its application to MIME entity-bodies. One |
|---|
| 1153 | is that HTTP, unlike MIME, does not use Content-Transfer-Encoding, and does use Transfer-Encoding and Content-Encoding. Another |
|---|
| 1154 | is that HTTP more frequently uses binary content types than MIME, so it is worth noting that, in such cases, the byte order |
|---|
| 1155 | used to compute the digest is the transmission byte order defined for the type. Lastly, HTTP allows transmission of text types |
|---|
| 1156 | with any of several line break conventions and not just the canonical form using CRLF. |
|---|
| 1157 | </dd> |
|---|
| 1158 | </dl> |
|---|
| 1159 | <div id="rfc.iref.c.6"></div> |
|---|
| 1160 | <div id="rfc.iref.h.9"></div> |
|---|
| 1161 | <h2 id="rfc.section.5.9"><a href="#rfc.section.5.9">5.9</a> <a id="header.content-type" href="#header.content-type">Content-Type</a></h2> |
|---|
| 1162 | <p id="rfc.section.5.9.p.1">The Content-Type entity-header field indicates the media type of the entity-body sent to the recipient or, in the case of |
|---|
| 1163 | the HEAD method, the media type that would have been sent had the request been a GET. |
|---|
| 1164 | </p> |
|---|
| 1165 | <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.31"></span> Content-Type = "Content-Type" ":" media-type |
|---|
| 1166 | </pre><p id="rfc.section.5.9.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section 2.3</a>. An example of the field is |
|---|
| 1167 | </p> |
|---|
| 1168 | <div id="rfc.figure.u.32"></div><pre class="text"> Content-Type: text/html; charset=ISO-8859-4 |
|---|
| 1169 | </pre><p id="rfc.section.5.9.p.5">Further discussion of methods for identifying the media type of an entity is provided in <a href="#type" title="Type">Section 3.2.1</a>. |
|---|
| 1170 | </p> |
|---|
| 1171 | <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> |
|---|
| 1172 | <p id="rfc.section.6.p.1">TBD.</p> |
|---|
| 1173 | <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> |
|---|
| 1174 | <p id="rfc.section.7.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1 |
|---|
| 1175 | as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does |
|---|
| 1176 | make some suggestions for reducing security risks. |
|---|
| 1177 | </p> |
|---|
| 1178 | <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a> <a id="privacy.issues.connected.to.accept.headers" href="#privacy.issues.connected.to.accept.headers">Privacy Issues Connected to Accept Headers</a></h2> |
|---|
| 1179 | <p id="rfc.section.7.1.p.1">Accept request-headers can reveal information about the user to all servers which are accessed. The Accept-Language header |
|---|
| 1180 | in particular can reveal information the user would consider to be of a private nature, because the understanding of particular |
|---|
| 1181 | languages is often strongly correlated to the membership of a particular ethnic group. User agents which offer the option |
|---|
| 1182 | to configure the contents of an Accept-Language header to be sent in every request are strongly encouraged to let the configuration |
|---|
| 1183 | process include a message which makes the user aware of the loss of privacy involved. |
|---|
| 1184 | </p> |
|---|
| 1185 | <p id="rfc.section.7.1.p.2">An approach that limits the loss of privacy would be for a user agent to omit the sending of Accept-Language headers by default, |
|---|
| 1186 | and to ask the user whether or not to start sending Accept-Language headers to a server if it detects, by looking for any |
|---|
| 1187 | Vary response-header fields generated by the server, that such sending could improve the quality of service. |
|---|
| 1188 | </p> |
|---|
| 1189 | <p id="rfc.section.7.1.p.3">Elaborate user-customized accept header fields sent in every request, in particular if these include quality values, can be |
|---|
| 1190 | used by servers as relatively reliable and long-lived user identifiers. Such user identifiers would allow content providers |
|---|
| 1191 | to do click-trail tracking, and would allow collaborating content providers to match cross-server click-trails or form submissions |
|---|
| 1192 | of individual users. Note that for many users not behind a proxy, the network address of the host running the user agent will |
|---|
| 1193 | also serve as a long-lived user identifier. In environments where proxies are used to enhance privacy, user agents ought to |
|---|
| 1194 | be conservative in offering accept header configuration options to end users. As an extreme privacy measure, proxies could |
|---|
| 1195 | filter the accept headers in relayed requests. General purpose user agents which provide a high degree of header configurability <em class="bcp14">SHOULD</em> warn users about the loss of privacy which can be involved. |
|---|
| 1196 | </p> |
|---|
| 1197 | <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a> <a id="content-disposition.issues" href="#content-disposition.issues">Content-Disposition Issues</a></h2> |
|---|
| 1198 | <p id="rfc.section.7.2.p.1"> <a href="#RFC1806" id="rfc.xref.RFC1806.1"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header">[RFC1806]</cite></a>, from which the often implemented Content-Disposition (see <a href="#content-disposition" id="rfc.xref.content-disposition.1" title="Content-Disposition">Appendix B.1</a>) header in HTTP is derived, has a number of very serious security considerations. Content-Disposition is not part of the |
|---|
| 1199 | HTTP standard, but since it is widely implemented, we are documenting its use and risks for implementors. See <a href="#RFC2183" id="rfc.xref.RFC2183.1"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field">[RFC2183]</cite></a> (which updates <a href="#RFC1806" id="rfc.xref.RFC1806.2"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header">[RFC1806]</cite></a>) for details. |
|---|
| 1200 | </p> |
|---|
| 1201 | <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> <a id="ack" href="#ack">Acknowledgments</a></h1> |
|---|
| 1202 | <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References |
|---|
| 1203 | </h1> |
|---|
| 1204 | <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References |
|---|
| 1205 | </h2> |
|---|
| 1206 | <table summary="Normative References"> |
|---|
| 1207 | <tr> |
|---|
| 1208 | <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> |
|---|
| 1209 | <td class="top">International Organization for Standardization, “ |
|---|
| 1210 | Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1 |
|---|
| 1211 | ”, ISO/IEC 8859-1:1998, 1998. |
|---|
| 1212 | </td> |
|---|
| 1213 | </tr> |
|---|
| 1214 | <tr> |
|---|
| 1215 | <td class="reference"><b id="Part1">[Part1]</b></td> |
|---|
| 1216 | <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-latest (work in progress), January 2008. |
|---|
| 1217 | </td> |
|---|
| 1218 | </tr> |
|---|
| 1219 | <tr> |
|---|
| 1220 | <td class="reference"><b id="Part2">[Part2]</b></td> |
|---|
| 1221 | <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), January 2008. |
|---|
| 1222 | </td> |
|---|
| 1223 | </tr> |
|---|
| 1224 | <tr> |
|---|
| 1225 | <td class="reference"><b id="Part4">[Part4]</b></td> |
|---|
| 1226 | <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-latest (work in progress), January 2008. |
|---|
| 1227 | </td> |
|---|
| 1228 | </tr> |
|---|
| 1229 | <tr> |
|---|
| 1230 | <td class="reference"><b id="Part5">[Part5]</b></td> |
|---|
| 1231 | <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-latest (work in progress), January 2008. |
|---|
| 1232 | </td> |
|---|
| 1233 | </tr> |
|---|
| 1234 | <tr> |
|---|
| 1235 | <td class="reference"><b id="Part6">[Part6]</b></td> |
|---|
| 1236 | <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), January 2008. |
|---|
| 1237 | </td> |
|---|
| 1238 | </tr> |
|---|
| 1239 | <tr> |
|---|
| 1240 | <td class="reference"><b id="RFC1950">[RFC1950]</b></td> |
|---|
| 1241 | <td class="top"><a title="Aladdin Enterprises">Deutsch, L.P.</a> and J-L. Gailly, “<a href="http://tools.ietf.org/html/rfc1950">ZLIB Compressed Data Format Specification version 3.3</a>”, RFC 1950, May 1996.<br>RFC1950 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference |
|---|
| 1242 | was present since <a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> (published in 1997), therefore it is unlikely to cause problems in practice. |
|---|
| 1243 | </td> |
|---|
| 1244 | </tr> |
|---|
| 1245 | <tr> |
|---|
| 1246 | <td class="reference"><b id="RFC1951">[RFC1951]</b></td> |
|---|
| 1247 | <td class="top"><a title="Aladdin Enterprises">Deutsch, P.</a>, “<a href="http://tools.ietf.org/html/rfc1951">DEFLATE Compressed Data Format Specification version 1.3</a>”, RFC 1951, May 1996.<br>RFC1951 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference |
|---|
| 1248 | was present since <a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> (published in 1997), therefore it is unlikely to cause problems in practice. |
|---|
| 1249 | </td> |
|---|
| 1250 | </tr> |
|---|
| 1251 | <tr> |
|---|
| 1252 | <td class="reference"><b id="RFC1952">[RFC1952]</b></td> |
|---|
| 1253 | <td class="top"><a title="Aladdin Enterprises">Deutsch, P.</a>, <a>Gailly, J-L.</a>, <a>Adler, M.</a>, <a>Deutsch, L.P.</a>, and <a>G. Randers-Pehrson</a>, “<a href="http://tools.ietf.org/html/rfc1952">GZIP file format specification version 4.3</a>”, RFC 1952, May 1996.<br>RFC1952 is an Informational RFC, thus it may be less stable than this specification. On the other hand, this downward reference |
|---|
| 1254 | was present since <a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> (published in 1997), therefore it is unlikely to cause problems in practice. |
|---|
| 1255 | </td> |
|---|
| 1256 | </tr> |
|---|
| 1257 | <tr> |
|---|
| 1258 | <td class="reference"><b id="RFC2119">[RFC2119]</b></td> |
|---|
| 1259 | <td class="top"><a title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP 14, RFC 2119, March 1997. |
|---|
| 1260 | </td> |
|---|
| 1261 | </tr> |
|---|
| 1262 | </table> |
|---|
| 1263 | <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References |
|---|
| 1264 | </h2> |
|---|
| 1265 | <table summary="Informative References"> |
|---|
| 1266 | <tr> |
|---|
| 1267 | <td class="reference"><b id="RFC2068">[RFC2068]</b></td> |
|---|
| 1268 | <td class="top"><a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, <a title="MIT Laboratory for Computer Science">Gettys, J.</a>, <a title="Digital Equipment Corporation, Western Research Laboratory">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Nielsen, H.</a>, and <a title="MIT Laboratory for Computer Science">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2068">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC 2068, January 1997. |
|---|
| 1269 | </td> |
|---|
| 1270 | </tr> |
|---|
| 1271 | <tr> |
|---|
| 1272 | <td class="reference"><b id="RFC2616">[RFC2616]</b></td> |
|---|
| 1273 | <td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC 2616, June 1999. |
|---|
| 1274 | </td> |
|---|
| 1275 | </tr> |
|---|
| 1276 | </table> |
|---|
| 1277 | <h2 id="rfc.references.3"><a href="#rfc.section.9.3" id="rfc.section.9.3">9.3</a> References (to be categorized) |
|---|
| 1278 | </h2> |
|---|
| 1279 | <table summary="References (to be categorized)"> |
|---|
| 1280 | <tr> |
|---|
| 1281 | <td class="reference"><b id="RFC1766">[RFC1766]</b></td> |
|---|
| 1282 | <td class="top"><a title="UNINETT">Alvestrand, H.</a>, “<a href="http://tools.ietf.org/html/rfc1766">Tags for the Identification of Languages</a>”, RFC 1766, March 1995. |
|---|
| 1283 | </td> |
|---|
| 1284 | </tr> |
|---|
| 1285 | <tr> |
|---|
| 1286 | <td class="reference"><b id="RFC1806">[RFC1806]</b></td> |
|---|
| 1287 | <td class="top"><a title="New Century Systems">Troost, R.</a> and <a title="QUALCOMM Incorporated">S. Dorner</a>, “<a href="http://tools.ietf.org/html/rfc1806">Communicating Presentation Information in Internet Messages: The Content-Disposition Header</a>”, RFC 1806, June 1995. |
|---|
| 1288 | </td> |
|---|
| 1289 | </tr> |
|---|
| 1290 | <tr> |
|---|
| 1291 | <td class="reference"><b id="RFC1864">[RFC1864]</b></td> |
|---|
| 1292 | <td class="top"><a title="Carnegie Mellon University">Myers, J.</a> and <a title="Dover Beach Consulting, Inc.">M. Rose</a>, “<a href="http://tools.ietf.org/html/rfc1864">The Content-MD5 Header Field</a>”, RFC 1864, October 1995. |
|---|
| 1293 | </td> |
|---|
| 1294 | </tr> |
|---|
| 1295 | <tr> |
|---|
| 1296 | <td class="reference"><b id="RFC1867">[RFC1867]</b></td> |
|---|
| 1297 | <td class="top"><a title="Xerox Palo Alto Research Center">Masinter, L.</a> and <a title="XSoft, Xerox Corporation">E. Nebel</a>, “<a href="http://tools.ietf.org/html/rfc1867">Form-based File Upload in HTML</a>”, RFC 1867, November 1995. |
|---|
| 1298 | </td> |
|---|
| 1299 | </tr> |
|---|
| 1300 | <tr> |
|---|
| 1301 | <td class="reference"><b id="RFC1945">[RFC1945]</b></td> |
|---|
| 1302 | <td class="top"><a title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC 1945, May 1996. |
|---|
| 1303 | </td> |
|---|
| 1304 | </tr> |
|---|
| 1305 | <tr> |
|---|
| 1306 | <td class="reference"><b id="RFC2045">[RFC2045]</b></td> |
|---|
| 1307 | <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a title="First Virtual Holdings">N.S. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>”, RFC 2045, November 1996. |
|---|
| 1308 | </td> |
|---|
| 1309 | </tr> |
|---|
| 1310 | <tr> |
|---|
| 1311 | <td class="reference"><b id="RFC2046">[RFC2046]</b></td> |
|---|
| 1312 | <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC 2046, November 1996. |
|---|
| 1313 | </td> |
|---|
| 1314 | </tr> |
|---|
| 1315 | <tr> |
|---|
| 1316 | <td class="reference"><b id="RFC2049">[RFC2049]</b></td> |
|---|
| 1317 | <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <a title="First Virtual Holdings">N.S. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2049">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</a>”, RFC 2049, November 1996. |
|---|
| 1318 | </td> |
|---|
| 1319 | </tr> |
|---|
| 1320 | <tr> |
|---|
| 1321 | <td class="reference"><b id="RFC2076">[RFC2076]</b></td> |
|---|
| 1322 | <td class="top"><a title="Stockholm University/KTH">Palme, J.</a>, “<a href="http://tools.ietf.org/html/rfc2076">Common Internet Message Headers</a>”, RFC 2076, February 1997. |
|---|
| 1323 | </td> |
|---|
| 1324 | </tr> |
|---|
| 1325 | <tr> |
|---|
| 1326 | <td class="reference"><b id="RFC2110">[RFC2110]</b></td> |
|---|
| 1327 | <td class="top"><a title="Stockholm University and KTH">Palme, J.</a> and <a title="Microsoft Corporation">A. Hopmann</a>, “<a href="http://tools.ietf.org/html/rfc2110">MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)</a>”, RFC 2110, March 1997. |
|---|
| 1328 | </td> |
|---|
| 1329 | </tr> |
|---|
| 1330 | <tr> |
|---|
| 1331 | <td class="reference"><b id="RFC2183">[RFC2183]</b></td> |
|---|
| 1332 | <td class="top"><a title="New Century Systems">Troost, R.</a>, <a title="QUALCOMM Incorporated">Dorner, S.</a>, and <a title="Department of Computer Science">K. Moore</a>, “<a href="http://tools.ietf.org/html/rfc2183">Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</a>”, RFC 2183, August 1997. |
|---|
| 1333 | </td> |
|---|
| 1334 | </tr> |
|---|
| 1335 | <tr> |
|---|
| 1336 | <td class="reference"><b id="RFC2277">[RFC2277]</b></td> |
|---|
| 1337 | <td class="top"><a title="UNINETT">Alvestrand, H.T.</a>, “<a href="http://tools.ietf.org/html/rfc2277">IETF Policy on Character Sets and Languages</a>”, BCP 18, RFC 2277, January 1998. |
|---|
| 1338 | </td> |
|---|
| 1339 | </tr> |
|---|
| 1340 | <tr> |
|---|
| 1341 | <td class="reference"><b id="RFC2279">[RFC2279]</b></td> |
|---|
| 1342 | <td class="top"><a title="Alis Technologies">Yergeau, F.</a>, “<a href="http://tools.ietf.org/html/rfc2279">UTF-8, a transformation format of ISO 10646</a>”, RFC 2279, January 1998. |
|---|
| 1343 | </td> |
|---|
| 1344 | </tr> |
|---|
| 1345 | <tr> |
|---|
| 1346 | <td class="reference"><b id="RFC4288">[RFC4288]</b></td> |
|---|
| 1347 | <td class="top"><a title="Sun Microsystems">Freed, N.</a> and <a>J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP 13, RFC 4288, December 2005. |
|---|
| 1348 | </td> |
|---|
| 1349 | </tr> |
|---|
| 1350 | <tr> |
|---|
| 1351 | <td class="reference"><b id="RFC822">[RFC822]</b></td> |
|---|
| 1352 | <td class="top"><a title="University of Delaware, Dept. of Electrical Engineering">Crocker, D.H.</a>, “<a href="http://tools.ietf.org/html/rfc822">Standard for the format of ARPA Internet text messages</a>”, STD 11, RFC 822, August 1982. |
|---|
| 1353 | </td> |
|---|
| 1354 | </tr> |
|---|
| 1355 | </table> |
|---|
| 1356 | <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1> |
|---|
| 1357 | <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span> |
|---|
| 1358 | (editor) |
|---|
| 1359 | <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Day Software</span><span class="adr"><span class="street-address vcardline">23 Corporate Plaza DR, Suite 280</span><span class="vcardline"><span class="locality">Newport Beach</span>, <span class="region">CA</span> <span class="postal-code">92660</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel">Phone: <a href="tel:+1-949-706-5300"><span class="value">+1-949-706-5300</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1-949-706-5305"><span class="value">+1-949-706-5305</span></a></span><span class="vcardline">EMail: <a><span class="email">fielding@gbiv.com</span></a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/" class="url">http://roy.gbiv.com/</a></span></address> |
|---|
| 1360 | <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">One Laptop per Child</span><span class="adr"><span class="street-address vcardline">21 Oak Knoll Road</span><span class="vcardline"><span class="locality">Carlisle</span>, <span class="region">MA</span> <span class="postal-code">01741</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">jg@laptop.org</span></a></span><span class="vcardline">URI: <a href="http://www.laptop.org/" class="url">http://www.laptop.org/</a></span></address> |
|---|
| 1361 | <address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Hewlett-Packard Company</span><span class="adr"><span class="street-address vcardline">HP Labs, Large Scale Systems Group</span><span class="street-address vcardline">1501 Page Mill Road, MS 1177</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">CA</span> <span class="postal-code">94304</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">JeffMogul@acm.org</span></a></span></address> |
|---|
| 1362 | <address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span> <span class="postal-code">98052</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">henrikn@microsoft.com</span></a></span></address> |
|---|
| 1363 | <address class="vcard"><span class="vcardline"><span class="fn">Larry Masinter</span><span class="n hidden"><span class="family-name">Masinter</span><span class="given-name">Larry</span></span></span><span class="org vcardline">Adobe Systems, Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span> <span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">LMM@acm.org</span></a></span><span class="vcardline">URI: <a href="http://larry.masinter.net/" class="url">http://larry.masinter.net/</a></span></address> |
|---|
| 1364 | <address class="vcard"><span class="vcardline"><span class="fn">Paul J. Leach</span><span class="n hidden"><span class="family-name">Leach</span><span class="given-name">Paul J.</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span> <span class="postal-code">98052</span></span></span><span class="vcardline">EMail: <a><span class="email">paulle@microsoft.com</span></a></span></address> |
|---|
| 1365 | <address class="vcard"><span class="vcardline"><span class="fn">Tim Berners-Lee</span><span class="n hidden"><span class="family-name">Berners-Lee</span><span class="given-name">Tim</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Computer Science and Artificial Intelligence Laboratory</span><span class="street-address vcardline">The Stata Center, Building 32</span><span class="street-address vcardline">32 Vassar Street</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span> <span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">timbl@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.w3.org/People/Berners-Lee/" class="url">http://www.w3.org/People/Berners-Lee/</a></span></address> |
|---|
| 1366 | <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span> |
|---|
| 1367 | (editor) |
|---|
| 1368 | <span class="n hidden"><span class="family-name">Lafon</span><span class="given-name">Yves</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">W3C / ERCIM</span><span class="street-address vcardline">2004, rte des Lucioles</span><span class="vcardline"><span class="locality">Sophia-Antipolis</span>, <span class="region">AM</span> <span class="postal-code">06902</span></span><span class="country-name vcardline">France</span></span><span class="vcardline">EMail: <a><span class="email">ylafon@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.raubacapeu.net/people/yves/" class="url">http://www.raubacapeu.net/people/yves/</a></span></address> |
|---|
| 1369 | <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span> |
|---|
| 1370 | (editor) |
|---|
| 1371 | <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span> <span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">EMail: <a><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address> |
|---|
| 1372 | <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a> <a id="differences.between.http.entities.and.rfc.2045.entities" href="#differences.between.http.entities.and.rfc.2045.entities">Differences Between HTTP Entities and RFC 2045 Entities</a></h1> |
|---|
| 1373 | <p id="rfc.section.A.p.1">HTTP/1.1 uses many of the constructs defined for Internet Mail (<a href="#RFC822" id="rfc.xref.RFC822.1"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>) and the Multipurpose Internet Mail Extensions (MIME <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>) to allow entities to be transmitted in an open variety of representations and with extensible mechanisms. However, RFC 2045 |
|---|
| 1374 | discusses mail, and HTTP has a few features that are different from those described in RFC 2045. These differences were carefully |
|---|
| 1375 | chosen to optimize performance over binary connections, to allow greater freedom in the use of new media types, to make date |
|---|
| 1376 | comparisons easier, and to acknowledge the practice of some early HTTP servers and clients. |
|---|
| 1377 | </p> |
|---|
| 1378 | <p id="rfc.section.A.p.2">This appendix describes specific areas where HTTP differs from RFC 2045. Proxies and gateways to strict MIME environments <em class="bcp14">SHOULD</em> be aware of these differences and provide the appropriate conversions where necessary. Proxies and gateways from MIME environments |
|---|
| 1379 | to HTTP also need to be aware of the differences because some conversions might be required. |
|---|
| 1380 | </p> |
|---|
| 1381 | <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a> <a id="mime-version" href="#mime-version">MIME-Version</a></h2> |
|---|
| 1382 | <p id="rfc.section.A.1.p.1">HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages <em class="bcp14">MAY</em> include a single MIME-Version general-header field to indicate what version of the MIME protocol was used to construct the |
|---|
| 1383 | message. Use of the MIME-Version header field indicates that the message is in full compliance with the MIME protocol (as |
|---|
| 1384 | defined in <a href="#RFC2045" id="rfc.xref.RFC2045.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>). Proxies/gateways are responsible for ensuring full compliance (where possible) when exporting HTTP messages to strict MIME |
|---|
| 1385 | environments. |
|---|
| 1386 | </p> |
|---|
| 1387 | <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.32"></span> MIME-Version = "MIME-Version" ":" 1*DIGIT "." 1*DIGIT |
|---|
| 1388 | </pre><p id="rfc.section.A.1.p.3">MIME version "1.0" is the default for use in HTTP/1.1. However, HTTP/1.1 message parsing and semantics are defined by this |
|---|
| 1389 | document and not the MIME specification. |
|---|
| 1390 | </p> |
|---|
| 1391 | <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a> <a id="conversion.to.canonical.form" href="#conversion.to.canonical.form">Conversion to Canonical Form</a></h2> |
|---|
| 1392 | <p id="rfc.section.A.2.p.1"> <a href="#RFC2045" id="rfc.xref.RFC2045.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a> requires that an Internet mail entity be converted to canonical form prior to being transferred, as described in <a href="http://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 2.3.1</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line |
|---|
| 1393 | break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break within text content when a message is transmitted |
|---|
| 1394 | over HTTP. |
|---|
| 1395 | </p> |
|---|
| 1396 | <p id="rfc.section.A.2.p.2">Where it is possible, a proxy or gateway from HTTP to a strict MIME environment <em class="bcp14">SHOULD</em> translate all line breaks within the text media types described in <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section 2.3.1</a> of this document to the RFC 2049 canonical form of CRLF. Note, however, that this might be complicated by the presence of |
|---|
| 1397 | a Content-Encoding and by the fact that HTTP allows the use of some character sets which do not use octets 13 and 10 to represent |
|---|
| 1398 | CR and LF, as is the case for some multi-byte character sets. |
|---|
| 1399 | </p> |
|---|
| 1400 | <p id="rfc.section.A.2.p.3">Implementors should note that conversion will break any cryptographic checksums applied to the original content unless the |
|---|
| 1401 | original content is already in canonical form. Therefore, the canonical form is recommended for any content that uses such |
|---|
| 1402 | checksums in HTTP. |
|---|
| 1403 | </p> |
|---|
| 1404 | <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a> <a id="introduction.of.content-encoding" href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h2> |
|---|
| 1405 | <p id="rfc.section.A.3.p.1">RFC 2045 does not include any concept equivalent to HTTP/1.1's Content-Encoding header field. Since this acts as a modifier |
|---|
| 1406 | on the media type, proxies and gateways from HTTP to MIME-compliant protocols <em class="bcp14">MUST</em> either change the value of the Content-Type header field or decode the entity-body before forwarding the message. (Some experimental |
|---|
| 1407 | applications of Content-Type for Internet mail have used a media-type parameter of ";conversions=<content-coding>" to perform |
|---|
| 1408 | a function equivalent to Content-Encoding. However, this parameter is not part of RFC 2045). |
|---|
| 1409 | </p> |
|---|
| 1410 | <h2 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a> <a id="no.content-transfer-encoding" href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></h2> |
|---|
| 1411 | <p id="rfc.section.A.4.p.1">HTTP does not use the Content-Transfer-Encoding field of RFC 2045. Proxies and gateways from MIME-compliant protocols to HTTP <em class="bcp14">MUST</em> remove any Content-Transfer-Encoding prior to delivering the response message to an HTTP client. |
|---|
| 1412 | </p> |
|---|
| 1413 | <p id="rfc.section.A.4.p.2">Proxies and gateways from HTTP to MIME-compliant protocols are responsible for ensuring that the message is in the correct |
|---|
| 1414 | format and encoding for safe transport on that protocol, where "safe transport" is defined by the limitations of the protocol |
|---|
| 1415 | being used. Such a proxy or gateway <em class="bcp14">SHOULD</em> label the data with an appropriate Content-Transfer-Encoding if doing so will improve the likelihood of safe transport over |
|---|
| 1416 | the destination protocol. |
|---|
| 1417 | </p> |
|---|
| 1418 | <h2 id="rfc.section.A.5"><a href="#rfc.section.A.5">A.5</a> <a id="introduction.of.transfer-encoding" href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></h2> |
|---|
| 1419 | <p id="rfc.section.A.5.p.1">HTTP/1.1 introduces the Transfer-Encoding header field (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 8.7</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). Proxies/gateways <em class="bcp14">MUST</em> remove any transfer-coding prior to forwarding a message via a MIME-compliant protocol. |
|---|
| 1420 | </p> |
|---|
| 1421 | <h2 id="rfc.section.A.6"><a href="#rfc.section.A.6">A.6</a> <a id="mhtml.line.length" href="#mhtml.line.length">MHTML and Line Length Limitations</a></h2> |
|---|
| 1422 | <p id="rfc.section.A.6.p.1">HTTP implementations which share code with MHTML <a href="#RFC2110" id="rfc.xref.RFC2110.1"><cite title="MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2110]</cite></a> implementations need to be aware of MIME line length limitations. Since HTTP does not have this limitation, HTTP does not |
|---|
| 1423 | fold long lines. MHTML messages being transported by HTTP follow all conventions of MHTML, including line length limitations |
|---|
| 1424 | and folding, canonicalization, etc., since HTTP transports all message-bodies as payload (see <a href="#multipart.types" title="Multipart Types">Section 2.3.2</a>) and does not interpret the content or any MIME header lines that might be contained therein. |
|---|
| 1425 | </p> |
|---|
| 1426 | <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a> <a id="additional.features" href="#additional.features">Additional Features</a></h1> |
|---|
| 1427 | <p id="rfc.section.B.p.1"> <a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a> and <a href="#RFC2068" id="rfc.xref.RFC2068.4"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> document protocol elements used by some existing HTTP implementations, but not consistently and correctly across most HTTP/1.1 |
|---|
| 1428 | applications. Implementors are advised to be aware of these features, but cannot rely upon their presence in, or interoperability |
|---|
| 1429 | with, other HTTP/1.1 applications. Some of these describe proposed experimental features, and some describe features that |
|---|
| 1430 | experimental deployment found lacking that are now addressed in the base HTTP/1.1 specification. |
|---|
| 1431 | </p> |
|---|
| 1432 | <p id="rfc.section.B.p.2">A number of other headers, such as Content-Disposition and Title, from SMTP and MIME are also often implemented (see <a href="#RFC2076" id="rfc.xref.RFC2076.1"><cite title="Common Internet Message Headers">[RFC2076]</cite></a>). |
|---|
| 1433 | </p> |
|---|
| 1434 | <div id="rfc.iref.h.10"></div> |
|---|
| 1435 | <div id="rfc.iref.c.7"></div> |
|---|
| 1436 | <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a> <a id="content-disposition" href="#content-disposition">Content-Disposition</a></h2> |
|---|
| 1437 | <p id="rfc.section.B.1.p.1">The Content-Disposition response-header field has been proposed as a means for the origin server to suggest a default filename |
|---|
| 1438 | if the user requests that the content is saved to a file. This usage is derived from the definition of Content-Disposition |
|---|
| 1439 | in <a href="#RFC1806" id="rfc.xref.RFC1806.3"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header">[RFC1806]</cite></a>. |
|---|
| 1440 | </p> |
|---|
| 1441 | <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.33"></span><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span> content-disposition = "Content-Disposition" ":" |
|---|
| 1442 | disposition-type *( ";" disposition-parm ) |
|---|
| 1443 | disposition-type = "attachment" | disp-extension-token |
|---|
| 1444 | disposition-parm = filename-parm | disp-extension-parm |
|---|
| 1445 | filename-parm = "filename" "=" quoted-string |
|---|
| 1446 | disp-extension-token = token |
|---|
| 1447 | disp-extension-parm = token "=" ( token | quoted-string ) |
|---|
| 1448 | </pre><p id="rfc.section.B.1.p.3">An example is</p> |
|---|
| 1449 | <div id="rfc.figure.u.35"></div><pre class="text"> Content-Disposition: attachment; filename="fname.ext" |
|---|
| 1450 | </pre><p id="rfc.section.B.1.p.5">The receiving user agent <em class="bcp14">SHOULD NOT</em> respect any directory path information present in the filename-parm parameter, which is the only parameter believed to apply |
|---|
| 1451 | to HTTP implementations at this time. The filename <em class="bcp14">SHOULD</em> be treated as a terminal component only. |
|---|
| 1452 | </p> |
|---|
| 1453 | <p id="rfc.section.B.1.p.6">If this header is used in a response with the application/octet-stream content-type, the implied suggestion is that the user |
|---|
| 1454 | agent should not display the response, but directly enter a `save response as...' dialog. |
|---|
| 1455 | </p> |
|---|
| 1456 | <p id="rfc.section.B.1.p.7">See <a href="#content-disposition.issues" title="Content-Disposition Issues">Section 7.2</a> for Content-Disposition security issues. |
|---|
| 1457 | </p> |
|---|
| 1458 | <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1> |
|---|
| 1459 | <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a> <a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2> |
|---|
| 1460 | <p id="rfc.section.C.1.p.1">Charset wildcarding is introduced to avoid explosion of character set names in accept headers. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section 5.2</a>) |
|---|
| 1461 | </p> |
|---|
| 1462 | <p id="rfc.section.C.1.p.2">Content-Base was deleted from the specification: it was not implemented widely, and there is no simple, safe way to introduce |
|---|
| 1463 | it without a robust extension mechanism. In addition, it is used in a similar, but not identical fashion in MHTML <a href="#RFC2110" id="rfc.xref.RFC2110.2"><cite title="MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2110]</cite></a>. |
|---|
| 1464 | </p> |
|---|
| 1465 | <p id="rfc.section.C.1.p.3">A content-coding of "identity" was introduced, to solve problems discovered in caching. (<a href="#content.codings" title="Content Codings">Section 2.2</a>) |
|---|
| 1466 | </p> |
|---|
| 1467 | <p id="rfc.section.C.1.p.4">Quality Values of zero should indicate that "I don't want something" to allow clients to refuse a representation. (<a href="#quality.values" title="Quality Values">Section 2.4</a>) |
|---|
| 1468 | </p> |
|---|
| 1469 | <p id="rfc.section.C.1.p.5">The Alternates<span id="rfc.iref.a.5"></span><span id="rfc.iref.h.11"></span>, Content-Version<span id="rfc.iref.c.8"></span><span id="rfc.iref.h.12"></span>, Derived-From<span id="rfc.iref.d.2"></span><span id="rfc.iref.h.13"></span>, Link<span id="rfc.iref.l.1"></span><span id="rfc.iref.h.14"></span>, URI<span id="rfc.iref.u.1"></span><span id="rfc.iref.h.15"></span>, Public<span id="rfc.iref.p.1"></span><span id="rfc.iref.h.16"></span> and Content-Base<span id="rfc.iref.c.9"></span><span id="rfc.iref.h.17"></span> header fields were defined in previous versions of this specification, but not commonly implemented. See <a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. |
|---|
| 1470 | </p> |
|---|
| 1471 | <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> |
|---|
| 1472 | <p id="rfc.section.C.2.p.1">Clarify contexts that charset is used in. (<a href="#character.sets" title="Character Sets">Section 2.1</a>) |
|---|
| 1473 | </p> |
|---|
| 1474 | <p id="rfc.section.C.2.p.2">Remove reference to non-existant identity transfer-coding value tokens. (<a href="#no.content-transfer-encoding" title="No Content-Transfer-Encoding">Appendix A.4</a>) |
|---|
| 1475 | </p> |
|---|
| 1476 | <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> Change Log (to be removed by RFC Editor before publication) |
|---|
| 1477 | </h1> |
|---|
| 1478 | <h2 id="rfc.section.D.1"><a href="#rfc.section.D.1">D.1</a> Since RFC2616 |
|---|
| 1479 | </h2> |
|---|
| 1480 | <p id="rfc.section.D.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. |
|---|
| 1481 | </p> |
|---|
| 1482 | <h2 id="rfc.section.D.2"><a href="#rfc.section.D.2">D.2</a> Since draft-ietf-httpbis-p3-payload-00 |
|---|
| 1483 | </h2> |
|---|
| 1484 | <p id="rfc.section.D.2.p.1">Closed issues: </p> |
|---|
| 1485 | <ul> |
|---|
| 1486 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/8">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/8</a>>: "Media Type Registrations" (<<a href="http://purl.org/NET/http-errata#media-reg">http://purl.org/NET/http-errata#media-reg</a>>) |
|---|
| 1487 | </li> |
|---|
| 1488 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/14">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/14</a>>: "Clarification regarding quoting of charset values" (<<a href="http://purl.org/NET/http-errata#charactersets">http://purl.org/NET/http-errata#charactersets</a>>) |
|---|
| 1489 | </li> |
|---|
| 1490 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/16">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/16</a>>: "Remove 'identity' token references" (<<a href="http://purl.org/NET/http-errata#identity">http://purl.org/NET/http-errata#identity</a>>) |
|---|
| 1491 | </li> |
|---|
| 1492 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/25">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/25</a>>: "Accept-Encoding BNF" |
|---|
| 1493 | </li> |
|---|
| 1494 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/46">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/46</a>>: "RFC1700 references" |
|---|
| 1495 | </li> |
|---|
| 1496 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/66</a>>: "ISO-8859-1 Reference" |
|---|
| 1497 | </li> |
|---|
| 1498 | <li> <<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/68">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/68</a>>: "Encoding References Normative" |
|---|
| 1499 | </li> |
|---|
| 1500 | </ul> |
|---|
| 1501 | <p id="rfc.section.D.2.p.2">Other changes: </p> |
|---|
| 1502 | <ul> |
|---|
| 1503 | <li>Start work on categorizing references as "Normative" or "Informative".</li> |
|---|
| 1504 | </ul> |
|---|
| 1505 | <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> |
|---|
| 1506 | <p>Copyright © The IETF Trust (2008).</p> |
|---|
| 1507 | <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the |
|---|
| 1508 | authors retain all their rights. |
|---|
| 1509 | </p> |
|---|
| 1510 | <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION |
|---|
| 1511 | HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE |
|---|
| 1512 | DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN |
|---|
| 1513 | WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
|---|
| 1514 | </p> |
|---|
| 1515 | <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1> |
|---|
| 1516 | <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might |
|---|
| 1517 | be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any |
|---|
| 1518 | license under such rights might or might not be available; nor does it represent that it has made any independent effort to |
|---|
| 1519 | identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and |
|---|
| 1520 | BCP 79. |
|---|
| 1521 | </p> |
|---|
| 1522 | <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result |
|---|
| 1523 | of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users |
|---|
| 1524 | of this specification can be obtained from the IETF on-line IPR repository at <<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>>. |
|---|
| 1525 | </p> |
|---|
| 1526 | <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary |
|---|
| 1527 | rights that may cover technology that may be required to implement this standard. Please address the information to the IETF |
|---|
| 1528 | at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>. |
|---|
| 1529 | </p> |
|---|
| 1530 | <h1>Acknowledgement</h1> |
|---|
| 1531 | <p>Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).</p> |
|---|
| 1532 | <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> |
|---|
| 1533 | <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.U">U</a> |
|---|
| 1534 | </p> |
|---|
| 1535 | <div class="print2col"> |
|---|
| 1536 | <ul class="ind"> |
|---|
| 1537 | <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind"> |
|---|
| 1538 | <li class="indline1">Accept header <a class="iref" href="#rfc.xref.header.accept.1">2.3</a>, <a class="iref" href="#rfc.xref.header.accept.2">4.1</a>, <a class="iref" href="#rfc.iref.a.1"><b>5.1</b></a></li> |
|---|
| 1539 | <li class="indline1">Accept-Charset header <a class="iref" href="#rfc.xref.header.accept-charset.1">4.1</a>, <a class="iref" href="#rfc.iref.a.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.accept-charset.2">C.1</a></li> |
|---|
| 1540 | <li class="indline1">Accept-Encoding header <a class="iref" href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.accept-encoding.2">4.1</a>, <a class="iref" href="#rfc.iref.a.3"><b>5.3</b></a></li> |
|---|
| 1541 | <li class="indline1">Accept-Language header <a class="iref" href="#rfc.xref.header.accept-language.1">4.1</a>, <a class="iref" href="#rfc.iref.a.4"><b>5.4</b></a></li> |
|---|
| 1542 | <li class="indline1">Alternates header <a class="iref" href="#rfc.iref.a.5"><b>C.1</b></a></li> |
|---|
| 1543 | </ul> |
|---|
| 1544 | </li> |
|---|
| 1545 | <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind"> |
|---|
| 1546 | <li class="indline1">compress <a class="iref" href="#rfc.iref.c.1">2.2</a></li> |
|---|
| 1547 | <li class="indline1">Content-Base header <a class="iref" href="#rfc.iref.c.9"><b>C.1</b></a></li> |
|---|
| 1548 | <li class="indline1">Content-Disposition header <a class="iref" href="#rfc.xref.content-disposition.1">7.2</a>, <a class="iref" href="#rfc.iref.c.7"><b>B.1</b></a></li> |
|---|
| 1549 | <li class="indline1">Content-Encoding header <a class="iref" href="#rfc.xref.header.content-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">3.1</a>, <a class="iref" href="#rfc.iref.c.2"><b>5.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">5.5</a></li> |
|---|
| 1550 | <li class="indline1">Content-Language header <a class="iref" href="#rfc.xref.header.content-language.1">3.1</a>, <a class="iref" href="#rfc.iref.c.3"><b>5.6</b></a></li> |
|---|
| 1551 | <li class="indline1">Content-Location header <a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.c.4"><b>5.7</b></a></li> |
|---|
| 1552 | <li class="indline1">Content-MD5 header <a class="iref" href="#rfc.xref.header.content-md5.1">3.1</a>, <a class="iref" href="#rfc.iref.c.5"><b>5.8</b></a></li> |
|---|
| 1553 | <li class="indline1">Content-Type header <a class="iref" href="#rfc.xref.header.content-type.1">2.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">3.1</a>, <a class="iref" href="#rfc.iref.c.6"><b>5.9</b></a></li> |
|---|
| 1554 | <li class="indline1">Content-Version header <a class="iref" href="#rfc.iref.c.8"><b>C.1</b></a></li> |
|---|
| 1555 | </ul> |
|---|
| 1556 | </li> |
|---|
| 1557 | <li class="indline0"><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul class="ind"> |
|---|
| 1558 | <li class="indline1">deflate <a class="iref" href="#rfc.iref.d.1">2.2</a></li> |
|---|
| 1559 | <li class="indline1">Derived-From header <a class="iref" href="#rfc.iref.d.2"><b>C.1</b></a></li> |
|---|
| 1560 | </ul> |
|---|
| 1561 | </li> |
|---|
| 1562 | <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind"> |
|---|
| 1563 | <li class="indline1"><tt>Grammar</tt> |
|---|
| 1564 | <ul class="ind"> |
|---|
| 1565 | <li class="indline1"><tt>Accept</tt> <a class="iref" href="#rfc.iref.g.17"><b>5.1</b></a></li> |
|---|
| 1566 | <li class="indline1"><tt>Accept-Charset</tt> <a class="iref" href="#rfc.iref.g.21"><b>5.2</b></a></li> |
|---|
| 1567 | <li class="indline1"><tt>Accept-Encoding</tt> <a class="iref" href="#rfc.iref.g.22"><b>5.3</b></a></li> |
|---|
| 1568 | <li class="indline1"><tt>accept-extension</tt> <a class="iref" href="#rfc.iref.g.20"><b>5.1</b></a></li> |
|---|
| 1569 | <li class="indline1"><tt>Accept-Language</tt> <a class="iref" href="#rfc.iref.g.24"><b>5.4</b></a></li> |
|---|
| 1570 | <li class="indline1"><tt>accept-params</tt> <a class="iref" href="#rfc.iref.g.19"><b>5.1</b></a></li> |
|---|
| 1571 | <li class="indline1"><tt>attribute</tt> <a class="iref" href="#rfc.iref.g.8"><b>2.3</b></a></li> |
|---|
| 1572 | <li class="indline1"><tt>charset</tt> <a class="iref" href="#rfc.iref.g.1"><b>2.1</b></a></li> |
|---|
| 1573 | <li class="indline1"><tt>codings</tt> <a class="iref" href="#rfc.iref.g.23"><b>5.3</b></a></li> |
|---|
| 1574 | <li class="indline1"><tt>content-coding</tt> <a class="iref" href="#rfc.iref.g.2"><b>2.2</b></a></li> |
|---|
| 1575 | <li class="indline1"><tt>content-disposition</tt> <a class="iref" href="#rfc.iref.g.33"><b>B.1</b></a></li> |
|---|
| 1576 | <li class="indline1"><tt>Content-Encoding</tt> <a class="iref" href="#rfc.iref.g.26"><b>5.5</b></a></li> |
|---|
| 1577 | <li class="indline1"><tt>Content-Language</tt> <a class="iref" href="#rfc.iref.g.27"><b>5.6</b></a></li> |
|---|
| 1578 | <li class="indline1"><tt>Content-Location</tt> <a class="iref" href="#rfc.iref.g.28"><b>5.7</b></a></li> |
|---|
| 1579 | <li class="indline1"><tt>Content-MD5</tt> <a class="iref" href="#rfc.iref.g.29"><b>5.8</b></a></li> |
|---|
| 1580 | <li class="indline1"><tt>Content-Type</tt> <a class="iref" href="#rfc.iref.g.31"><b>5.9</b></a></li> |
|---|
| 1581 | <li class="indline1"><tt>disp-extension-parm</tt> <a class="iref" href="#rfc.iref.g.38"><b>B.1</b></a></li> |
|---|
| 1582 | <li class="indline1"><tt>disp-extension-token</tt> <a class="iref" href="#rfc.iref.g.37"><b>B.1</b></a></li> |
|---|
| 1583 | <li class="indline1"><tt>disposition-parm</tt> <a class="iref" href="#rfc.iref.g.35"><b>B.1</b></a></li> |
|---|
| 1584 | <li class="indline1"><tt>disposition-type</tt> <a class="iref" href="#rfc.iref.g.34"><b>B.1</b></a></li> |
|---|
| 1585 | <li class="indline1"><tt>entity-body</tt> <a class="iref" href="#rfc.iref.g.16"><b>3.2</b></a></li> |
|---|
| 1586 | <li class="indline1"><tt>entity-header</tt> <a class="iref" href="#rfc.iref.g.14"><b>3.1</b></a></li> |
|---|
| 1587 | <li class="indline1"><tt>extension-header</tt> <a class="iref" href="#rfc.iref.g.15"><b>3.1</b></a></li> |
|---|
| 1588 | <li class="indline1"><tt>filename-parm</tt> <a class="iref" href="#rfc.iref.g.36"><b>B.1</b></a></li> |
|---|
| 1589 | <li class="indline1"><tt>language-range</tt> <a class="iref" href="#rfc.iref.g.25"><b>5.4</b></a></li> |
|---|
| 1590 | <li class="indline1"><tt>language-tag</tt> <a class="iref" href="#rfc.iref.g.11"><b>2.5</b></a></li> |
|---|
| 1591 | <li class="indline1"><tt>md5-digest</tt> <a class="iref" href="#rfc.iref.g.30"><b>5.8</b></a></li> |
|---|
| 1592 | <li class="indline1"><tt>media-range</tt> <a class="iref" href="#rfc.iref.g.18"><b>5.1</b></a></li> |
|---|
| 1593 | <li class="indline1"><tt>media-type</tt> <a class="iref" href="#rfc.iref.g.4"><b>2.3</b></a></li> |
|---|
| 1594 | <li class="indline1"><tt>MIME-Version</tt> <a class="iref" href="#rfc.iref.g.32"><b>A.1</b></a></li> |
|---|
| 1595 | <li class="indline1"><tt>parameter</tt> <a class="iref" href="#rfc.iref.g.7"><b>2.3</b></a></li> |
|---|
| 1596 | <li class="indline1"><tt>primary-tag</tt> <a class="iref" href="#rfc.iref.g.12"><b>2.5</b></a></li> |
|---|
| 1597 | <li class="indline1"><tt>qvalue</tt> <a class="iref" href="#rfc.iref.g.10"><b>2.4</b></a></li> |
|---|
| 1598 | <li class="indline1"><tt>subtag</tt> <a class="iref" href="#rfc.iref.g.13"><b>2.5</b></a></li> |
|---|
| 1599 | <li class="indline1"><tt>subtype</tt> <a class="iref" href="#rfc.iref.g.6"><b>2.3</b></a></li> |
|---|
| 1600 | <li class="indline1"><tt>type</tt> <a class="iref" href="#rfc.iref.g.5"><b>2.3</b></a></li> |
|---|
| 1601 | <li class="indline1"><tt>value</tt> <a class="iref" href="#rfc.iref.g.9"><b>2.3</b></a></li> |
|---|
| 1602 | </ul> |
|---|
| 1603 | </li> |
|---|
| 1604 | <li class="indline1">gzip <a class="iref" href="#rfc.iref.g.3">2.2</a></li> |
|---|
| 1605 | </ul> |
|---|
| 1606 | </li> |
|---|
| 1607 | <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind"> |
|---|
| 1608 | <li class="indline1">Headers |
|---|
| 1609 | <ul class="ind"> |
|---|
| 1610 | <li class="indline1">Accept <a class="iref" href="#rfc.xref.header.accept.1">2.3</a>, <a class="iref" href="#rfc.xref.header.accept.2">4.1</a>, <a class="iref" href="#rfc.iref.h.1"><b>5.1</b></a></li> |
|---|
| 1611 | <li class="indline1">Accept-Charset <a class="iref" href="#rfc.xref.header.accept-charset.1">4.1</a>, <a class="iref" href="#rfc.iref.h.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.accept-charset.2">C.1</a></li> |
|---|
| 1612 | <li class="indline1">Accept-Encoding <a class="iref" href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.accept-encoding.2">4.1</a>, <a class="iref" href="#rfc.iref.h.3"><b>5.3</b></a></li> |
|---|
| 1613 | <li class="indline1">Accept-Language <a class="iref" href="#rfc.xref.header.accept-language.1">4.1</a>, <a class="iref" href="#rfc.iref.h.4"><b>5.4</b></a></li> |
|---|
| 1614 | <li class="indline1">Alternate <a class="iref" href="#rfc.iref.h.11"><b>C.1</b></a></li> |
|---|
| 1615 | <li class="indline1">Content-Base <a class="iref" href="#rfc.iref.h.17"><b>C.1</b></a></li> |
|---|
| 1616 | <li class="indline1">Content-Disposition <a class="iref" href="#rfc.xref.content-disposition.1">7.2</a>, <a class="iref" href="#rfc.iref.h.10"><b>B.1</b></a></li> |
|---|
| 1617 | <li class="indline1">Content-Encoding <a class="iref" href="#rfc.xref.header.content-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">3.1</a>, <a class="iref" href="#rfc.iref.h.5"><b>5.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">5.5</a></li> |
|---|
| 1618 | <li class="indline1">Content-Language <a class="iref" href="#rfc.xref.header.content-language.1">3.1</a>, <a class="iref" href="#rfc.iref.h.6"><b>5.6</b></a></li> |
|---|
| 1619 | <li class="indline1">Content-Location <a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.h.7"><b>5.7</b></a></li> |
|---|
| 1620 | <li class="indline1">Content-MD5 <a class="iref" href="#rfc.xref.header.content-md5.1">3.1</a>, <a class="iref" href="#rfc.iref.h.8"><b>5.8</b></a></li> |
|---|
| 1621 | <li class="indline1">Content-Type <a class="iref" href="#rfc.xref.header.content-type.1">2.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">3.1</a>, <a class="iref" href="#rfc.iref.h.9"><b>5.9</b></a></li> |
|---|
| 1622 | <li class="indline1">Content-Version <a class="iref" href="#rfc.iref.h.12"><b>C.1</b></a></li> |
|---|
| 1623 | <li class="indline1">Derived-From <a class="iref" href="#rfc.iref.h.13"><b>C.1</b></a></li> |
|---|
| 1624 | <li class="indline1">Link <a class="iref" href="#rfc.iref.h.14"><b>C.1</b></a></li> |
|---|
| 1625 | <li class="indline1">Public <a class="iref" href="#rfc.iref.h.16"><b>C.1</b></a></li> |
|---|
| 1626 | <li class="indline1">URI <a class="iref" href="#rfc.iref.h.15"><b>C.1</b></a></li> |
|---|
| 1627 | </ul> |
|---|
| 1628 | </li> |
|---|
| 1629 | </ul> |
|---|
| 1630 | </li> |
|---|
| 1631 | <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind"> |
|---|
| 1632 | <li class="indline1">identity <a class="iref" href="#rfc.iref.i.1">2.2</a></li> |
|---|
| 1633 | <li class="indline1"><em>ISO-8859-1</em> <a class="iref" href="#rfc.xref.ISO-8859-1.1">2.1.1</a>, <a class="iref" href="#ISO-8859-1"><b>9.1</b></a></li> |
|---|
| 1634 | </ul> |
|---|
| 1635 | </li> |
|---|
| 1636 | <li class="indline0"><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul class="ind"> |
|---|
| 1637 | <li class="indline1">Link header <a class="iref" href="#rfc.iref.l.1"><b>C.1</b></a></li> |
|---|
| 1638 | </ul> |
|---|
| 1639 | </li> |
|---|
| 1640 | <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"> |
|---|
| 1641 | <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">3.1</a>, <a class="iref" href="#rfc.xref.Part1.2">3.2</a>, <a class="iref" href="#rfc.xref.Part1.3">3.2.2</a>, <a class="iref" href="#Part1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part1.4">A.5</a><ul class="ind"> |
|---|
| 1642 | <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.2">3.2</a></li> |
|---|
| 1643 | <li class="indline1"><em>Section 4.4</em> <a class="iref" href="#rfc.xref.Part1.3">3.2.2</a></li> |
|---|
| 1644 | <li class="indline1"><em>Section 8.2</em> <a class="iref" href="#rfc.xref.Part1.1">3.1</a></li> |
|---|
| 1645 | <li class="indline1"><em>Section 8.7</em> <a class="iref" href="#rfc.xref.Part1.4">A.5</a></li> |
|---|
| 1646 | </ul> |
|---|
| 1647 | </li> |
|---|
| 1648 | <li class="indline1"><em>Part2</em> <a class="iref" href="#rfc.xref.Part2.1">3.1</a>, <a class="iref" href="#rfc.xref.Part2.2">4.1</a>, <a class="iref" href="#Part2"><b>9.1</b></a><ul class="ind"> |
|---|
| 1649 | <li class="indline1"><em>Section 10.1</em> <a class="iref" href="#rfc.xref.Part2.1">3.1</a></li> |
|---|
| 1650 | <li class="indline1"><em>Section 10.9</em> <a class="iref" href="#rfc.xref.Part2.2">4.1</a></li> |
|---|
| 1651 | </ul> |
|---|
| 1652 | </li> |
|---|
| 1653 | <li class="indline1"><em>Part4</em> <a class="iref" href="#rfc.xref.Part4.1">3.1</a>, <a class="iref" href="#Part4"><b>9.1</b></a><ul class="ind"> |
|---|
| 1654 | <li class="indline1"><em>Section 6.6</em> <a class="iref" href="#rfc.xref.Part4.1">3.1</a></li> |
|---|
| 1655 | </ul> |
|---|
| 1656 | </li> |
|---|
| 1657 | <li class="indline1"><em>Part5</em> <a class="iref" href="#rfc.xref.Part5.1">2.3.2</a>, <a class="iref" href="#rfc.xref.Part5.2">3.1</a>, <a class="iref" href="#Part5"><b>9.1</b></a><ul class="ind"> |
|---|
| 1658 | <li class="indline1"><em>Section 5.2</em> <a class="iref" href="#rfc.xref.Part5.2">3.1</a></li> |
|---|
| 1659 | <li class="indline1"><em>Section A</em> <a class="iref" href="#rfc.xref.Part5.1">2.3.2</a></li> |
|---|
| 1660 | </ul> |
|---|
| 1661 | </li> |
|---|
| 1662 | <li class="indline1"><em>Part6</em> <a class="iref" href="#rfc.xref.Part6.1">3.1</a>, <a class="iref" href="#rfc.xref.Part6.2">4.1</a>, <a class="iref" href="#rfc.xref.Part6.3">5.7</a>, <a class="iref" href="#Part6"><b>9.1</b></a><ul class="ind"> |
|---|
| 1663 | <li class="indline1"><em>Section 2.6</em> <a class="iref" href="#rfc.xref.Part6.3">5.7</a></li> |
|---|
| 1664 | <li class="indline1"><em>Section 3.3</em> <a class="iref" href="#rfc.xref.Part6.1">3.1</a></li> |
|---|
| 1665 | <li class="indline1"><em>Section 3.5</em> <a class="iref" href="#rfc.xref.Part6.2">4.1</a></li> |
|---|
| 1666 | </ul> |
|---|
| 1667 | </li> |
|---|
| 1668 | <li class="indline1">Public header <a class="iref" href="#rfc.iref.p.1"><b>C.1</b></a></li> |
|---|
| 1669 | </ul> |
|---|
| 1670 | </li> |
|---|
| 1671 | <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind"> |
|---|
| 1672 | <li class="indline1"><em>RFC1766</em> <a class="iref" href="#rfc.xref.RFC1766.1">2.5</a>, <a class="iref" href="#RFC1766"><b>9.3</b></a></li> |
|---|
| 1673 | <li class="indline1"><em>RFC1806</em> <a class="iref" href="#rfc.xref.RFC1806.1">7.2</a>, <a class="iref" href="#rfc.xref.RFC1806.2">7.2</a>, <a class="iref" href="#RFC1806"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC1806.3">B.1</a></li> |
|---|
| 1674 | <li class="indline1"><em>RFC1864</em> <a class="iref" href="#rfc.xref.RFC1864.1">5.8</a>, <a class="iref" href="#rfc.xref.RFC1864.2">5.8</a>, <a class="iref" href="#RFC1864"><b>9.3</b></a></li> |
|---|
| 1675 | <li class="indline1"><em>RFC1867</em> <a class="iref" href="#rfc.xref.RFC1867.1">2.3.2</a>, <a class="iref" href="#RFC1867"><b>9.3</b></a></li> |
|---|
| 1676 | <li class="indline1"><em>RFC1945</em> <a class="iref" href="#RFC1945"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li> |
|---|
| 1677 | <li class="indline1"><em>RFC1950</em> <a class="iref" href="#rfc.xref.RFC1950.1">2.2</a>, <a class="iref" href="#RFC1950"><b>9.1</b></a></li> |
|---|
| 1678 | <li class="indline1"><em>RFC1951</em> <a class="iref" href="#rfc.xref.RFC1951.1">2.2</a>, <a class="iref" href="#RFC1951"><b>9.1</b></a></li> |
|---|
| 1679 | <li class="indline1"><em>RFC1952</em> <a class="iref" href="#rfc.xref.RFC1952.1">2.2</a>, <a class="iref" href="#RFC1952"><b>9.1</b></a></li> |
|---|
| 1680 | <li class="indline1"><em>RFC2045</em> <a class="iref" href="#RFC2045"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC2045.1">A</a>, <a class="iref" href="#rfc.xref.RFC2045.2">A.1</a>, <a class="iref" href="#rfc.xref.RFC2045.3">A.2</a></li> |
|---|
| 1681 | <li class="indline1"><em>RFC2046</em> <a class="iref" href="#rfc.xref.RFC2046.1">2.3.2</a>, <a class="iref" href="#RFC2046"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC2046.2">A.2</a><ul class="ind"> |
|---|
| 1682 | <li class="indline1"><em>Section 5.1.1</em> <a class="iref" href="#rfc.xref.RFC2046.1">2.3.2</a></li> |
|---|
| 1683 | </ul> |
|---|
| 1684 | </li> |
|---|
| 1685 | <li class="indline1"><em>RFC2049</em> <a class="iref" href="#RFC2049"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC2049.1">A.2</a><ul class="ind"> |
|---|
| 1686 | <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.RFC2049.1">A.2</a></li> |
|---|
| 1687 | </ul> |
|---|
| 1688 | </li> |
|---|
| 1689 | <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">§</a>, <a class="iref" href="#rfc.xref.RFC2068.2">§</a>, <a class="iref" href="#rfc.xref.RFC2068.3">§</a>, <a class="iref" href="#RFC2068"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.4">B</a>, <a class="iref" href="#rfc.xref.RFC2068.5">C.1</a></li> |
|---|
| 1690 | <li class="indline1"><em>RFC2076</em> <a class="iref" href="#RFC2076"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC2076.1">B</a></li> |
|---|
| 1691 | <li class="indline1"><em>RFC2110</em> <a class="iref" href="#RFC2110"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC2110.1">A.6</a>, <a class="iref" href="#rfc.xref.RFC2110.2">C.1</a></li> |
|---|
| 1692 | <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>9.1</b></a></li> |
|---|
| 1693 | <li class="indline1"><em>RFC2183</em> <a class="iref" href="#rfc.xref.RFC2183.1">7.2</a>, <a class="iref" href="#RFC2183"><b>9.3</b></a></li> |
|---|
| 1694 | <li class="indline1"><em>RFC2277</em> <a class="iref" href="#rfc.xref.RFC2277.1">2.1</a>, <a class="iref" href="#RFC2277"><b>9.3</b></a></li> |
|---|
| 1695 | <li class="indline1"><em>RFC2279</em> <a class="iref" href="#rfc.xref.RFC2279.1">2.1</a>, <a class="iref" href="#RFC2279"><b>9.3</b></a></li> |
|---|
| 1696 | <li class="indline1"><em>RFC2616</em> <a class="iref" href="#RFC2616"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">D.1</a></li> |
|---|
| 1697 | <li class="indline1"><em>RFC4288</em> <a class="iref" href="#rfc.xref.RFC4288.1">2.3</a>, <a class="iref" href="#rfc.xref.RFC4288.2">2.3</a>, <a class="iref" href="#RFC4288"><b>9.3</b></a></li> |
|---|
| 1698 | <li class="indline1"><em>RFC822</em> <a class="iref" href="#RFC822"><b>9.3</b></a>, <a class="iref" href="#rfc.xref.RFC822.1">A</a></li> |
|---|
| 1699 | </ul> |
|---|
| 1700 | </li> |
|---|
| 1701 | <li class="indline0"><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul class="ind"> |
|---|
| 1702 | <li class="indline1">URI header <a class="iref" href="#rfc.iref.u.1"><b>C.1</b></a></li> |
|---|
| 1703 | </ul> |
|---|
| 1704 | </li> |
|---|
| 1705 | </ul> |
|---|
| 1706 | </div> |
|---|
| 1707 | </body> |
|---|
| 1708 | </html> |
|---|
![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
