![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 1099 for draft-ietf-httpbis/02/p3-payload.html
- Timestamp:
- 01/01/11 17:23:02 (11 years ago)
- File:
-
- 1 edited
-
draft-ietf-httpbis/02/p3-payload.html (modified) (37 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/02/p3-payload.html
r231 r1099 2 2 PUBLIC "-//W3C//DTD HTML 4.01//EN"> 3 3 <html lang="en"> 4 <head profile="http://www.w3.org/2006/03/hcard ">4 <head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/"> 5 5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> 6 6 <title>HTTP/1.1, part 3: Message Payload and Content Negotiation</title><style type="text/css" title="Xml2Rfc (sans serif)"> … … 37 37 } 38 38 39 dl.empty dd { 39 ul.empty { 40 list-style-type: none; 41 } 42 ul.empty li { 40 43 margin-top: .5em; 41 44 } … … 62 65 page-break-after: avoid; 63 66 } 64 h2 a { 65 color: black; 66 } 67 h3 { 67 h3, h4, h5, h6 { 68 68 font-size: 10pt; 69 69 page-break-after: avoid; 70 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 { 71 h2 a, h3 a, h4 a, h5 a, h6 a { 86 72 color: black; 87 73 } … … 135 121 } 136 122 table.header { 123 border-spacing: 1px; 137 124 width: 95%; 138 125 font-size: 10pt; … … 146 133 white-space: nowrap; 147 134 } 148 t d.header{135 table.header td { 149 136 background-color: gray; 150 137 width: 50%; 151 138 } 152 t d.header a {139 table.header a { 153 140 color: white; 154 141 } … … 161 148 display:table-header-group; 162 149 } 163 ul.toc {150 ul.toc, ul.toc ul { 164 151 list-style: none; 165 152 margin-left: 1.5em; … … 167 154 padding-left: 0em; 168 155 } 169 li.tocline0{156 ul.toc li { 170 157 line-height: 150%; 171 158 font-weight: bold; … … 174 161 margin-right: 0em; 175 162 } 176 li.tocline1{163 ul.toc li li { 177 164 line-height: normal; 178 165 font-weight: normal; … … 181 168 margin-right: 0em; 182 169 } 183 li. tocline2{170 li.excluded { 184 171 font-size: 0pt; 185 172 } … … 187 174 margin-left: 0em; 188 175 } 189 ul.ind {176 ul.ind, ul.ind ul { 190 177 list-style: none; 191 178 margin-left: 1.5em; 192 179 margin-right: 0em; 193 180 padding-left: 0em; 194 } 195 li.indline0 { 181 page-break-before: avoid; 182 } 183 ul.ind li { 196 184 font-weight: bold; 197 185 line-height: 200%; … … 199 187 margin-right: 0em; 200 188 } 201 li.indline1{189 ul.ind li li { 202 190 font-weight: normal; 203 191 line-height: 150%; 204 192 margin-left: 0em; 205 193 margin-right: 0em; 194 } 195 .avoidbreak { 196 page-break-inside: avoid; 206 197 } 207 198 .bcp14 { … … 288 279 } 289 280 290 a.iref{281 ul.ind li li a { 291 282 content: target-counter(attr(href), page); 292 283 } … … 301 292 @page { 302 293 @top-left { 303 content: "I NTERNET DRAFT";294 content: "Internet-Draft"; 304 295 } 305 296 @top-right { … … 349 340 <link rel="Appendix" title="C Compatibility with Previous Versions" href="#rfc.section.C"> 350 341 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 351 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.365, 2008-03-07 07:17:25, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 352 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 353 <meta name="DC.Creator" content="Fielding, R."> 354 <meta name="DC.Creator" content="Gettys, J."> 355 <meta name="DC.Creator" content="Mogul, J."> 356 <meta name="DC.Creator" content="Frystyk, H."> 357 <meta name="DC.Creator" content="Masinter, L."> 358 <meta name="DC.Creator" content="Leach, P."> 359 <meta name="DC.Creator" content="Berners-Lee, T."> 360 <meta name="DC.Creator" content="Lafon, Y."> 361 <meta name="DC.Creator" content="Reschke, J. F."> 362 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-02"> 363 <meta name="DC.Date.Issued" scheme="ISO8601" content="2008-02"> 364 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 365 <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."> 342 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.537, 2010-12-30 14:21:59, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 343 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 344 <meta name="dct.creator" content="Fielding, R."> 345 <meta name="dct.creator" content="Gettys, J."> 346 <meta name="dct.creator" content="Mogul, J."> 347 <meta name="dct.creator" content="Frystyk, H."> 348 <meta name="dct.creator" content="Masinter, L."> 349 <meta name="dct.creator" content="Leach, P."> 350 <meta name="dct.creator" content="Berners-Lee, T."> 351 <meta name="dct.creator" content="Lafon, Y."> 352 <meta name="dct.creator" content="Reschke, J. F."> 353 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-02"> 354 <meta name="dct.issued" scheme="ISO8601" content="2008-02-24"> 355 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 356 <meta name="dct.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."> 357 <meta name="description" 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."> 366 358 </head> 367 359 <body> 368 <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1"> 369 <tr> 370 <td class="header left">Network Working Group</td> 371 <td class="header right">R. Fielding, Editor</td> 372 </tr> 373 <tr> 374 <td class="header left">Internet Draft</td> 375 <td class="header right">Day Software</td> 376 </tr> 377 <tr> 378 <td class="header left"> 379 <draft-ietf-httpbis-p3-payload-02> 380 381 </td> 382 <td class="header right">J. Gettys</td> 383 </tr> 384 <tr> 385 <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 386 </td> 387 <td class="header right">One Laptop per Child</td> 388 </tr> 389 <tr> 390 <td class="header left">Intended status: Standards Track</td> 391 <td class="header right">J. Mogul</td> 392 </tr> 393 <tr> 394 <td class="header left">Expires: August 2008</td> 395 <td class="header right">HP</td> 396 </tr> 397 <tr> 398 <td class="header left"></td> 399 <td class="header right">H. Frystyk</td> 400 </tr> 401 <tr> 402 <td class="header left"></td> 403 <td class="header right">Microsoft</td> 404 </tr> 405 <tr> 406 <td class="header left"></td> 407 <td class="header right">L. Masinter</td> 408 </tr> 409 <tr> 410 <td class="header left"></td> 411 <td class="header right">Adobe Systems</td> 412 </tr> 413 <tr> 414 <td class="header left"></td> 415 <td class="header right">P. Leach</td> 416 </tr> 417 <tr> 418 <td class="header left"></td> 419 <td class="header right">Microsoft</td> 420 </tr> 421 <tr> 422 <td class="header left"></td> 423 <td class="header right">T. Berners-Lee</td> 424 </tr> 425 <tr> 426 <td class="header left"></td> 427 <td class="header right">W3C/MIT</td> 428 </tr> 429 <tr> 430 <td class="header left"></td> 431 <td class="header right">Y. Lafon, Editor</td> 432 </tr> 433 <tr> 434 <td class="header left"></td> 435 <td class="header right">W3C</td> 436 </tr> 437 <tr> 438 <td class="header left"></td> 439 <td class="header right">J. F. Reschke, Editor</td> 440 </tr> 441 <tr> 442 <td class="header left"></td> 443 <td class="header right">greenbytes</td> 444 </tr> 445 <tr> 446 <td class="header left"></td> 447 <td class="header right">February 24, 2008</td> 448 </tr> 360 <table class="header"> 361 <tbody> 362 <tr> 363 <td class="left">Network Working Group</td> 364 <td class="right">R. Fielding, Editor</td> 365 </tr> 366 <tr> 367 <td class="left">Internet-Draft</td> 368 <td class="right">Day Software</td> 369 </tr> 370 <tr> 371 <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 372 </td> 373 <td class="right">J. Gettys</td> 374 </tr> 375 <tr> 376 <td class="left">Intended status: Standards Track</td> 377 <td class="right">One Laptop per Child</td> 378 </tr> 379 <tr> 380 <td class="left">Expires: August 27, 2008</td> 381 <td class="right">J. Mogul</td> 382 </tr> 383 <tr> 384 <td class="left"></td> 385 <td class="right">HP</td> 386 </tr> 387 <tr> 388 <td class="left"></td> 389 <td class="right">H. Frystyk</td> 390 </tr> 391 <tr> 392 <td class="left"></td> 393 <td class="right">Microsoft</td> 394 </tr> 395 <tr> 396 <td class="left"></td> 397 <td class="right">L. Masinter</td> 398 </tr> 399 <tr> 400 <td class="left"></td> 401 <td class="right">Adobe Systems</td> 402 </tr> 403 <tr> 404 <td class="left"></td> 405 <td class="right">P. Leach</td> 406 </tr> 407 <tr> 408 <td class="left"></td> 409 <td class="right">Microsoft</td> 410 </tr> 411 <tr> 412 <td class="left"></td> 413 <td class="right">T. Berners-Lee</td> 414 </tr> 415 <tr> 416 <td class="left"></td> 417 <td class="right">W3C/MIT</td> 418 </tr> 419 <tr> 420 <td class="left"></td> 421 <td class="right">Y. Lafon, Editor</td> 422 </tr> 423 <tr> 424 <td class="left"></td> 425 <td class="right">W3C</td> 426 </tr> 427 <tr> 428 <td class="left"></td> 429 <td class="right">J. Reschke, Editor</td> 430 </tr> 431 <tr> 432 <td class="left"></td> 433 <td class="right">greenbytes</td> 434 </tr> 435 <tr> 436 <td class="left"></td> 437 <td class="right">February 24, 2008</td> 438 </tr> 439 </tbody> 449 440 </table> 450 441 <p class="title">HTTP/1.1, part 3: Message Payload and Content Negotiation<br><span class="filename">draft-ietf-httpbis-p3-payload-02</span></p> … … 461 452 in progress”. 462 453 </p> 463 <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>>.464 </p> 465 <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>>.466 </p> 467 <p>This Internet-Draft will expire in August2008.</p>454 <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>. 455 </p> 456 <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>. 457 </p> 458 <p>This Internet-Draft will expire on August 27, 2008.</p> 468 459 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 469 460 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information … … 481 472 <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1> 482 473 <ul class="toc"> 483 <li class="tocline0">1. <a href="#introduction">Introduction</a><ul class="toc">484 <li class="tocline1">1.1 <a href="#intro.requirements">Requirements</a></li>474 <li>1. <a href="#introduction">Introduction</a><ul> 475 <li>1.1 <a href="#intro.requirements">Requirements</a></li> 485 476 </ul> 486 477 </li> 487 <li class="tocline0">2. <a href="#notation">Notational Conventions and Generic Grammar</a></li>488 <li class="tocline0">3. <a href="#protocol.parameters">Protocol Parameters</a><ul class="toc">489 <li class="tocline1">3.1 <a href="#character.sets">Character Sets</a><ul class="toc">490 <li class="tocline1">3.1.1 <a href="#missing.charset">Missing Charset</a></li>478 <li>2. <a href="#notation">Notational Conventions and Generic Grammar</a></li> 479 <li>3. <a href="#protocol.parameters">Protocol Parameters</a><ul> 480 <li>3.1 <a href="#character.sets">Character Sets</a><ul> 481 <li>3.1.1 <a href="#missing.charset">Missing Charset</a></li> 491 482 </ul> 492 483 </li> 493 <li class="tocline1">3.2 <a href="#content.codings">Content Codings</a></li>494 <li class="tocline1">3.3 <a href="#media.types">Media Types</a><ul class="toc">495 <li class="tocline1">3.3.1 <a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>496 <li class="tocline1">3.3.2 <a href="#multipart.types">Multipart Types</a></li>484 <li>3.2 <a href="#content.codings">Content Codings</a></li> 485 <li>3.3 <a href="#media.types">Media Types</a><ul> 486 <li>3.3.1 <a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li> 487 <li>3.3.2 <a href="#multipart.types">Multipart Types</a></li> 497 488 </ul> 498 489 </li> 499 <li class="tocline1">3.4 <a href="#quality.values">Quality Values</a></li>500 <li class="tocline1">3.5 <a href="#language.tags">Language Tags</a></li>490 <li>3.4 <a href="#quality.values">Quality Values</a></li> 491 <li>3.5 <a href="#language.tags">Language Tags</a></li> 501 492 </ul> 502 493 </li> 503 <li class="tocline0">4. <a href="#entity">Entity</a><ul class="toc">504 <li class="tocline1">4.1 <a href="#entity.header.fields">Entity Header Fields</a></li>505 <li class="tocline1">4.2 <a href="#entity.body">Entity Body</a><ul class="toc">506 <li class="tocline1">4.2.1 <a href="#type">Type</a></li>507 <li class="tocline1">4.2.2 <a href="#entity.length">Entity Length</a></li>494 <li>4. <a href="#entity">Entity</a><ul> 495 <li>4.1 <a href="#entity.header.fields">Entity Header Fields</a></li> 496 <li>4.2 <a href="#entity.body">Entity Body</a><ul> 497 <li>4.2.1 <a href="#type">Type</a></li> 498 <li>4.2.2 <a href="#entity.length">Entity Length</a></li> 508 499 </ul> 509 500 </li> 510 501 </ul> 511 502 </li> 512 <li class="tocline0">5. <a href="#content.negotiation">Content Negotiation</a><ul class="toc">513 <li class="tocline1">5.1 <a href="#server-driven.negotiation">Server-driven Negotiation</a></li>514 <li class="tocline1">5.2 <a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li>515 <li class="tocline1">5.3 <a href="#transparent.negotiation">Transparent Negotiation</a></li>503 <li>5. <a href="#content.negotiation">Content Negotiation</a><ul> 504 <li>5.1 <a href="#server-driven.negotiation">Server-driven Negotiation</a></li> 505 <li>5.2 <a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li> 506 <li>5.3 <a href="#transparent.negotiation">Transparent Negotiation</a></li> 516 507 </ul> 517 508 </li> 518 <li class="tocline0">6. <a href="#header.fields">Header Field Definitions</a><ul class="toc">519 <li class="tocline1">6.1 <a href="#header.accept">Accept</a></li>520 <li class="tocline1">6.2 <a href="#header.accept-charset">Accept-Charset</a></li>521 <li class="tocline1">6.3 <a href="#header.accept-encoding">Accept-Encoding</a></li>522 <li class="tocline1">6.4 <a href="#header.accept-language">Accept-Language</a></li>523 <li class="tocline1">6.5 <a href="#header.content-encoding">Content-Encoding</a></li>524 <li class="tocline1">6.6 <a href="#header.content-language">Content-Language</a></li>525 <li class="tocline1">6.7 <a href="#header.content-location">Content-Location</a></li>526 <li class="tocline1">6.8 <a href="#header.content-md5">Content-MD5</a></li>527 <li class="tocline1">6.9 <a href="#header.content-type">Content-Type</a></li>509 <li>6. <a href="#header.fields">Header Field Definitions</a><ul> 510 <li>6.1 <a href="#header.accept">Accept</a></li> 511 <li>6.2 <a href="#header.accept-charset">Accept-Charset</a></li> 512 <li>6.3 <a href="#header.accept-encoding">Accept-Encoding</a></li> 513 <li>6.4 <a href="#header.accept-language">Accept-Language</a></li> 514 <li>6.5 <a href="#header.content-encoding">Content-Encoding</a></li> 515 <li>6.6 <a href="#header.content-language">Content-Language</a></li> 516 <li>6.7 <a href="#header.content-location">Content-Location</a></li> 517 <li>6.8 <a href="#header.content-md5">Content-MD5</a></li> 518 <li>6.9 <a href="#header.content-type">Content-Type</a></li> 528 519 </ul> 529 520 </li> 530 <li class="tocline0">7. <a href="#IANA.considerations">IANA Considerations</a></li>531 <li class="tocline0">8. <a href="#security.considerations">Security Considerations</a><ul class="toc">532 <li class="tocline1">8.1 <a href="#privacy.issues.connected.to.accept.headers">Privacy Issues Connected to Accept Headers</a></li>533 <li class="tocline1">8.2 <a href="#content-disposition.issues">Content-Disposition Issues</a></li>521 <li>7. <a href="#IANA.considerations">IANA Considerations</a></li> 522 <li>8. <a href="#security.considerations">Security Considerations</a><ul> 523 <li>8.1 <a href="#privacy.issues.connected.to.accept.headers">Privacy Issues Connected to Accept Headers</a></li> 524 <li>8.2 <a href="#content-disposition.issues">Content-Disposition Issues</a></li> 534 525 </ul> 535 526 </li> 536 <li class="tocline0">9. <a href="#ack">Acknowledgments</a></li>537 <li class="tocline0">10. <a href="#rfc.references">References</a><ul class="toc">538 <li class="tocline1">10.1 <a href="#rfc.references.1">Normative References</a></li>539 <li class="tocline1">10.2 <a href="#rfc.references.2">Informative References</a></li>527 <li>9. <a href="#ack">Acknowledgments</a></li> 528 <li>10. <a href="#rfc.references">References</a><ul> 529 <li>10.1 <a href="#rfc.references.1">Normative References</a></li> 530 <li>10.2 <a href="#rfc.references.2">Informative References</a></li> 540 531 </ul> 541 532 </li> 542 <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>543 <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">544 <li class="tocline1">A.1 <a href="#mime-version">MIME-Version</a></li>545 <li class="tocline1">A.2 <a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li>546 <li class="tocline1">A.3 <a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li>547 <li class="tocline1">A.4 <a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li>548 <li class="tocline1">A.5 <a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li>549 <li class="tocline1">A.6 <a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li>533 <li><a href="#rfc.authors">Authors' Addresses</a></li> 534 <li>A. <a href="#differences.between.http.entities.and.rfc.2045.entities">Differences Between HTTP Entities and RFC 2045 Entities</a><ul> 535 <li>A.1 <a href="#mime-version">MIME-Version</a></li> 536 <li>A.2 <a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li> 537 <li>A.3 <a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li> 538 <li>A.4 <a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li> 539 <li>A.5 <a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li> 540 <li>A.6 <a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li> 550 541 </ul> 551 542 </li> 552 <li class="tocline0">B. <a href="#additional.features">Additional Features</a><ul class="toc">553 <li class="tocline1">B.1 <a href="#content-disposition">Content-Disposition</a></li>543 <li>B. <a href="#additional.features">Additional Features</a><ul> 544 <li>B.1 <a href="#content-disposition">Content-Disposition</a></li> 554 545 </ul> 555 546 </li> 556 <li class="tocline0">C. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc">557 <li class="tocline1">C.1 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>558 <li class="tocline1">C.2 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>547 <li>C. <a href="#compatibility">Compatibility with Previous Versions</a><ul> 548 <li>C.1 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li> 549 <li>C.2 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 559 550 </ul> 560 551 </li> 561 <li class="tocline0">D. <a href="#rfc.section.D">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">562 <li class="tocline1">D.1 <a href="#rfc.section.D.1">Since RFC2616</a></li>563 <li class="tocline1">D.2 <a href="#rfc.section.D.2">Since draft-ietf-httpbis-p3-payload-00</a></li>564 <li class="tocline1">D.3 <a href="#rfc.section.D.3">Since draft-ietf-httpbis-p3-payload-01</a></li>552 <li>D. <a href="#rfc.section.D">Change Log (to be removed by RFC Editor before publication)</a><ul> 553 <li>D.1 <a href="#rfc.section.D.1">Since RFC2616</a></li> 554 <li>D.2 <a href="#rfc.section.D.2">Since draft-ietf-httpbis-p3-payload-00</a></li> 555 <li>D.3 <a href="#rfc.section.D.3">Since draft-ietf-httpbis-p3-payload-01</a></li> 565 556 </ul> 566 557 </li> 567 <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>568 <li class="tocline0"><a href="#rfc.index">Index</a></li>558 <li><a href="#rfc.index">Index</a></li> 559 <li><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li> 569 560 </ul> 570 561 <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> <a id="introduction" href="#introduction">Introduction</a></h1> … … 586 577 </p> 587 578 <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="notation" href="#notation">Notational Conventions and Generic Grammar</a></h1> 588 <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="Augmented BNF">Section 2.1</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> and the core rules defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</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>: <span class="comment" >[abnf.dep: ABNF syntax and basic rules will be adopted from RFC 5234, see <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>.]</span>579 <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="Augmented BNF">Section 2.1</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> and the core rules defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</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>: <span class="comment" id="abnf.dep">[<a href="#abnf.dep" class="smpl">abnf.dep</a>: ABNF syntax and basic rules will be adopted from RFC 5234, see <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>>.]</span> 589 580 </p> 590 581 <div id="rfc.figure.u.1"></div><pre class="inline"> ALPHA = <ALPHA, defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>> … … 615 606 to determine the exact mapping is not permitted. 616 607 </p> 617 < dl class="empty">618 < dd> <b>Note:</b> This use of the term "character set" is more commonly referred to as a "character encoding." However, since HTTP and MIME608 <ul class="empty"> 609 <li> <b>Note:</b> This use of the term "character set" is more commonly referred to as a "character encoding." However, since HTTP and MIME 619 610 share the same registry, it is important that the terminology also be shared. 620 </ dd>621 </ dl>611 </li> 612 </ul> 622 613 <p id="rfc.section.3.1.p.4">HTTP character sets are identified by case-insensitive tokens. The complete set of tokens is defined by the IANA Character 623 614 Set registry (<<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>>). … … 655 646 <p id="rfc.section.3.2.p.5">gzip<span id="rfc.iref.g.3"></span> 656 647 </p> 657 < dl class="empty">658 < 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.659 </ dd>660 </ dl>648 <ul class="empty"> 649 <li>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. 650 </li> 651 </ul> 661 652 <p id="rfc.section.3.2.p.6">compress<span id="rfc.iref.c.1"></span> 662 653 </p> 663 < dl class="empty">664 < dd>The encoding format produced by the common UNIX file compression program "compress". This format is an adaptive Lempel-Ziv-Welch654 <ul class="empty"> 655 <li>The encoding format produced by the common UNIX file compression program "compress". This format is an adaptive Lempel-Ziv-Welch 665 656 coding (LZW). 666 </ dd>667 < dd>Use of program names for the identification of encoding formats is not desirable and is discouraged for future encodings.657 </li> 658 <li>Use of program names for the identification of encoding formats is not desirable and is discouraged for future encodings. 668 659 Their use here is representative of historical practice, not good design. For compatibility with previous implementations 669 660 of HTTP, applications <em class="bcp14">SHOULD</em> consider "x-gzip" and "x-compress" to be equivalent to "gzip" and "compress" respectively. 670 </ dd>671 </ dl>661 </li> 662 </ul> 672 663 <p id="rfc.section.3.2.p.7">deflate<span id="rfc.iref.d.1"></span> 673 664 </p> 674 < dl class="empty">675 < 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>.676 </ dd>677 </ dl>665 <ul class="empty"> 666 <li>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>. 667 </li> 668 </ul> 678 669 <p id="rfc.section.3.2.p.8">identity<span id="rfc.iref.i.1"></span> 679 670 </p> 680 < dl class="empty">681 < dd>The default (identity) encoding; the use of no transformation whatsoever. This content-coding is used only in the Accept-Encoding671 <ul class="empty"> 672 <li>The default (identity) encoding; the use of no transformation whatsoever. This content-coding is used only in the Accept-Encoding 682 673 header, and <em class="bcp14">SHOULD NOT</em> be used in the Content-Encoding header. 683 </ dd>684 </ dl>674 </li> 675 </ul> 685 676 <p id="rfc.section.3.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 686 677 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 … … 733 724 </p> 734 725 <p id="rfc.section.3.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 735 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.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) when it appears in a 206 (Partial Content) response. 726 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.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) when it appears in a 206 (Partial Content) response. In all other cases, 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. The MIME header fields within 727 each body-part of a multipart message-body do not have any significance to HTTP beyond that defined by their MIME semantics. 736 728 </p> 737 729 <p id="rfc.section.3.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 738 730 an unrecognized multipart subtype, the application <em class="bcp14">MUST</em> treat it as being equivalent to "multipart/mixed". 739 731 </p> 740 < dl class="empty">741 < dd> <b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request732 <ul class="empty"> 733 <li> <b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request 742 734 method, as described in <a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>. 743 </ dd>744 </ dl>735 </li> 736 </ul> 745 737 <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a> <a id="quality.values" href="#quality.values">Quality Values</a></h2> 746 738 <p id="rfc.section.3.4.p.1">HTTP content negotiation (<a href="#content.negotiation" title="Content Negotiation">Section 5</a>) uses short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight … … 825 817 best representation for a given response when there are multiple representations available. 826 818 </p> 827 < dl class="empty">828 < dd> <b>Note:</b> This is not called "format negotiation" because the alternate representations may be of the same media type, but use different819 <ul class="empty"> 820 <li> <b>Note:</b> This is not called "format negotiation" because the alternate representations may be of the same media type, but use different 829 821 capabilities of that type, be in different languages, etc. 830 </ dd>831 </ dl>822 </li> 823 </ul> 832 824 <p id="rfc.section.5.p.2">Any response containing an entity-body <em class="bcp14">MAY</em> be subject to negotiation, including error responses. 833 825 </p> … … 926 918 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 3.4</a>). The default value is q=1. 927 919 </p> 928 < dl class="empty">929 < dd> <b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice.920 <ul class="empty"> 921 <li> <b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice. 930 922 Although this prevents any media type parameter named "q" from being used with a media range, such an event is believed to 931 923 be unlikely given the lack of any "q" parameters in the IANA media type registry and the rare usage of any media type parameters 932 924 in Accept. Future media types are discouraged from registering any parameter named "q". 933 </ dd>934 </ dl>925 </li> 926 </ul> 935 927 <p id="rfc.section.6.1.p.5">The example</p> 936 928 <div id="rfc.figure.u.19"></div><pre class="text"> Accept: audio/*; q=0.2, audio/basic … … 1028 1020 client. 1029 1021 </p> 1030 < dl class="empty">1031 < dd> <b>Note:</b> If the request does not include an Accept-Encoding field, and if the "identity" content-coding is unavailable, then content-codings1022 <ul class="empty"> 1023 <li> <b>Note:</b> If the request does not include an Accept-Encoding field, and if the "identity" content-coding is unavailable, then content-codings 1032 1024 commonly understood by HTTP/1.0 clients (i.e., "gzip" and "compress") are preferred; some older clients improperly display 1033 1025 messages sent with other content-codings. The server might also make this decision based on information about the particular 1034 1026 user-agent or client. 1035 </ dd>1036 < dd> <b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues will1027 </li> 1028 <li> <b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues will 1037 1029 not work and are not permitted with x-gzip or x-compress. 1038 </ dd>1039 </ dl>1030 </li> 1031 </ul> 1040 1032 <div id="rfc.iref.a.4"></div> 1041 1033 <div id="rfc.iref.h.4"></div> … … 1056 1048 range present in the Accept-Language field. 1057 1049 </p> 1058 < dl class="empty">1059 < 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 always1050 <ul class="empty"> 1051 <li> <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 1060 1052 true that if a user understands a language with a certain tag, then this user will also understand all languages with tags 1061 1053 for which this tag is a prefix. The prefix rule simply allows the use of prefix tags if this is the case. 1062 </ dd>1063 </ dl>1054 </li> 1055 </ul> 1064 1056 <p id="rfc.section.6.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 1065 1057 in the field that matches the language-tag. If no language-range in the field matches the tag, the language quality factor … … 1073 1065 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. 1074 1066 </p> 1075 < dl class="empty">1076 < dd> <b>Note:</b> When making the choice of linguistic preference available to the user, we remind implementors of the fact that users are not1067 <ul class="empty"> 1068 <li> <b>Note:</b> When making the choice of linguistic preference available to the user, we remind implementors of the fact that users are not 1077 1069 familiar with the details of language matching as described above, and should provide appropriate guidance. As an example, 1078 1070 users might assume that on selecting "en-gb", they will be served any kind of English document if British English is not available. 1079 1071 A user agent might suggest in such a case to add "en" to get the best matching behavior. 1080 </ dd>1081 </ dl>1072 </li> 1073 </ul> 1082 1074 <div id="rfc.iref.c.2"></div> 1083 1075 <div id="rfc.iref.h.5"></div> … … 1176 1168 <p id="rfc.section.6.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. 1177 1169 </p> 1178 < dl class="empty">1179 < 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 several1170 <ul class="empty"> 1171 <li> <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 1180 1172 ways in which the application of Content-MD5 to HTTP entity-bodies differs from its application to MIME entity-bodies. One 1181 1173 is that HTTP, unlike MIME, does not use Content-Transfer-Encoding, and does use Transfer-Encoding and Content-Encoding. Another … … 1183 1175 used to compute the digest is the transmission byte order defined for the type. Lastly, HTTP allows transmission of text types 1184 1176 with any of several line break conventions and not just the canonical form using CRLF. 1185 </ dd>1186 </ dl>1177 </li> 1178 </ul> 1187 1179 <div id="rfc.iref.c.6"></div> 1188 1180 <div id="rfc.iref.h.9"></div> … … 1198 1190 </p> 1199 1191 <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 1200 <p id="rfc.section.7.p.1"> <span class="comment" >[rfc.comment.1: TBD.]</span>1192 <p id="rfc.section.7.p.1"> <span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: TBD.]</span> 1201 1193 </p> 1202 1194 <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> … … 1233 1225 <h2 id="rfc.references.1"><a href="#rfc.section.10.1" id="rfc.section.10.1">10.1</a> Normative References 1234 1226 </h2> 1235 <table summary="Normative References">1227 <table> 1236 1228 <tr> 1237 1229 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> 1238 <td class="top">International Organization for Standardization, “ 1239 Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1 1240 ”, ISO/IEC 8859-1:1998, 1998. 1241 </td> 1230 <td class="top">International Organization for Standardization, “Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1”, ISO/IEC 8859-1:1998, 1998.</td> 1242 1231 </tr> 1243 1232 <tr> 1244 1233 <td class="reference"><b id="Part1">[Part1]</b></td> 1245 <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-02">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-02 (work in progress), February 2008.1234 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-02">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-02 (work in progress), February 2008. 1246 1235 </td> 1247 1236 </tr> 1248 1237 <tr> 1249 1238 <td class="reference"><b id="Part2">[Part2]</b></td> 1250 <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-02">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-02 (work in progress), February 2008.1239 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-02">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-02 (work in progress), February 2008. 1251 1240 </td> 1252 1241 </tr> 1253 1242 <tr> 1254 1243 <td class="reference"><b id="Part4">[Part4]</b></td> 1255 <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-02">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-02 (work in progress), February 2008.1244 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-02">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-02 (work in progress), February 2008. 1256 1245 </td> 1257 1246 </tr> 1258 1247 <tr> 1259 1248 <td class="reference"><b id="Part5">[Part5]</b></td> 1260 <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-02">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-02 (work in progress), February 2008.1249 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-02">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-02 (work in progress), February 2008. 1261 1250 </td> 1262 1251 </tr> 1263 1252 <tr> 1264 1253 <td class="reference"><b id="Part6">[Part6]</b></td> 1265 <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-02">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-02 (work in progress), February 2008.1254 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-02">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-02 (work in progress), February 2008. 1266 1255 </td> 1267 1256 </tr> 1268 1257 <tr> 1269 1258 <td class="reference"><b id="RFC1766">[RFC1766]</b></td> 1270 <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.1259 <td class="top"><a href="mailto:Harald.T.Alvestrand@uninett.no" title="UNINETT">Alvestrand, H.</a>, “<a href="http://tools.ietf.org/html/rfc1766">Tags for the Identification of Languages</a>”, RFC 1766, March 1995. 1271 1260 </td> 1272 1261 </tr> 1273 1262 <tr> 1274 1263 <td class="reference"><b id="RFC1864">[RFC1864]</b></td> 1275 <td class="top"><a title="Carnegie Mellon University">Myers, J.</a> and <atitle="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.1264 <td class="top"><a href="mailto:jgm+@cmu.edu" title="Carnegie Mellon University">Myers, J.</a> and <a href="mailto:mrose@dbc.mtview.ca.us" 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. 1276 1265 </td> 1277 1266 </tr> 1278 1267 <tr> 1279 1268 <td class="reference"><b id="RFC1950">[RFC1950]</b></td> 1280 <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 reference1269 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, L.</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 1281 1270 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. 1282 1271 </td> … … 1284 1273 <tr> 1285 1274 <td class="reference"><b id="RFC1951">[RFC1951]</b></td> 1286 <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 reference1275 <td class="top"><a href="mailto:ghost@aladdin.com" 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 1287 1276 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. 1288 1277 </td> … … 1290 1279 <tr> 1291 1280 <td class="reference"><b id="RFC1952">[RFC1952]</b></td> 1292 <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 reference1281 <td class="top"><a href="mailto:ghost@aladdin.com" title="Aladdin Enterprises">Deutsch, P.</a>, <a href="mailto:gzip@prep.ai.mit.edu">Gailly, J-L.</a>, <a href="mailto:madler@alumni.caltech.edu">Adler, M.</a>, <a href="mailto:ghost@aladdin.com">Deutsch, L.</a>, and <a href="mailto:randeg@alumni.rpi.edu">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 1293 1282 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. 1294 1283 </td> … … 1296 1285 <tr> 1297 1286 <td class="reference"><b id="RFC2045">[RFC2045]</b></td> 1298 <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.1287 <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>”, RFC 2045, November 1996. 1299 1288 </td> 1300 1289 </tr> 1301 1290 <tr> 1302 1291 <td class="reference"><b id="RFC2046">[RFC2046]</b></td> 1303 <td class="top"><a title="Innosoft International, Inc.">Freed, N.</a> and <atitle="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.1292 <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC 2046, November 1996. 1304 1293 </td> 1305 1294 </tr> 1306 1295 <tr> 1307 1296 <td class="reference"><b id="RFC2119">[RFC2119]</b></td> 1308 <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.1297 <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP 14, RFC 2119, March 1997. 1309 1298 </td> 1310 1299 </tr> … … 1312 1301 <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References 1313 1302 </h2> 1314 <table summary="Informative References">1303 <table> 1315 1304 <tr> 1316 1305 <td class="reference"><b id="RFC1806">[RFC1806]</b></td> 1317 <td class="top"><a title="New Century Systems">Troost, R.</a> and <atitle="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.1306 <td class="top"><a href="mailto:rens@century.com" title="New Century Systems">Troost, R.</a> and <a href="mailto:sdorner@qualcomm.com" 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. 1318 1307 </td> 1319 1308 </tr> 1320 1309 <tr> 1321 1310 <td class="reference"><b id="RFC1945">[RFC1945]</b></td> 1322 <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.1311 <td class="top"><a href="mailto:timbl@w3.org" title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, and <a href="mailto:frystyk@w3.org" title="W3 Consortium, MIT Laboratory for Computer Science">H. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC 1945, May 1996. 1323 1312 </td> 1324 1313 </tr> 1325 1314 <tr> 1326 1315 <td class="reference"><b id="RFC2049">[RFC2049]</b></td> 1327 <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.1316 <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2049">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</a>”, RFC 2049, November 1996. 1328 1317 </td> 1329 1318 </tr> 1330 1319 <tr> 1331 1320 <td class="reference"><b id="RFC2068">[RFC2068]</b></td> 1332 <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 <atitle="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.1321 <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="MIT Laboratory for Computer Science">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Digital Equipment Corporation, Western Research Laboratory">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Nielsen, H.</a>, and <a href="mailto:timbl@w3.org" 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. 1333 1322 </td> 1334 1323 </tr> 1335 1324 <tr> 1336 1325 <td class="reference"><b id="RFC2076">[RFC2076]</b></td> 1337 <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.1326 <td class="top"><a href="mailto:jpalme@dsv.su.se" title="Stockholm University/KTH">Palme, J.</a>, “<a href="http://tools.ietf.org/html/rfc2076">Common Internet Message Headers</a>”, RFC 2076, February 1997. 1338 1327 </td> 1339 1328 </tr> 1340 1329 <tr> 1341 1330 <td class="reference"><b id="RFC2183">[RFC2183]</b></td> 1342 <td class="top"><a title="New Century Systems">Troost, R.</a>, <a title="QUALCOMM Incorporated">Dorner, S.</a>, and <atitle="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.1331 <td class="top"><a href="mailto:rens@century.com" title="New Century Systems">Troost, R.</a>, <a href="mailto:sdorner@qualcomm.com" title="QUALCOMM Incorporated">Dorner, S.</a>, and <a href="mailto:moore@cs.utk.edu" 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. 1343 1332 </td> 1344 1333 </tr> 1345 1334 <tr> 1346 1335 <td class="reference"><b id="RFC2277">[RFC2277]</b></td> 1347 <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.1336 <td class="top"><a href="mailto:Harald.T.Alvestrand@uninett.no" title="UNINETT">Alvestrand, H.</a>, “<a href="http://tools.ietf.org/html/rfc2277">IETF Policy on Character Sets and Languages</a>”, BCP 18, RFC 2277, January 1998. 1348 1337 </td> 1349 1338 </tr> 1350 1339 <tr> 1351 1340 <td class="reference"><b id="RFC2388">[RFC2388]</b></td> 1352 <td class="top"><a title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="http://tools.ietf.org/html/rfc2388">Returning Values from Forms:multipart/form-data</a>”, RFC 2388, August 1998.1341 <td class="top"><a href="mailto:masinter@parc.xerox.com" title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="http://tools.ietf.org/html/rfc2388">Returning Values from Forms: multipart/form-data</a>”, RFC 2388, August 1998. 1353 1342 </td> 1354 1343 </tr> 1355 1344 <tr> 1356 1345 <td class="reference"><b id="RFC2557">[RFC2557]</b></td> 1357 <td class="top"><a title="Stockholm University and KTH">Palme, F.</a>, <a title="Microsoft Corporation">Hopmann, A.</a>, <a title="Lotus Development Corporation">Shelness, N.</a>, and <a>E. Stefferud</a>, “<a href="http://tools.ietf.org/html/rfc2557">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</a>”, RFC 2557, March 1999.1346 <td class="top"><a href="mailto:jpalme@dsv.su.se" title="Stockholm University and KTH">Palme, F.</a>, <a href="mailto:alexhop@microsoft.com" title="Microsoft Corporation">Hopmann, A.</a>, <a href="mailto:Shelness@lotus.com" title="Lotus Development Corporation">Shelness, N.</a>, and <a href="mailto:stef@nma.com">E. Stefferud</a>, “<a href="http://tools.ietf.org/html/rfc2557">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</a>”, RFC 2557, March 1999. 1358 1347 </td> 1359 1348 </tr> 1360 1349 <tr> 1361 1350 <td class="reference"><b id="RFC2616">[RFC2616]</b></td> 1362 <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 <atitle="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC 2616, June 1999.1351 <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC 2616, June 1999. 1363 1352 </td> 1364 1353 </tr> … … 1370 1359 <tr> 1371 1360 <td class="reference"><b id="RFC3629">[RFC3629]</b></td> 1372 <td class="top"><a title="Alis Technologies">Yergeau, F.</a>, “<a href="http://tools.ietf.org/html/rfc3629">UTF-8, a transformation format of ISO 10646</a>”, RFC 3629, STD 63, November 2003.1361 <td class="top"><a href="mailto:fyergeau@alis.com" title="Alis Technologies">Yergeau, F.</a>, “<a href="http://tools.ietf.org/html/rfc3629">UTF-8, a transformation format of ISO 10646</a>”, RFC 3629, STD 63, November 2003. 1373 1362 </td> 1374 1363 </tr> 1375 1364 <tr> 1376 1365 <td class="reference"><b id="RFC4288">[RFC4288]</b></td> 1377 <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.1366 <td class="top"><a href="mailto:ned.freed@mrochek.com" title="Sun Microsystems">Freed, N.</a> and <a href="mailto:klensin+ietf@jck.com">J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP 13, RFC 4288, December 2005. 1378 1367 </td> 1379 1368 </tr> 1380 1369 </table> 1381 <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1> 1382 <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span> 1383 (editor) 1384 <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> 1385 <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> 1386 <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> 1387 <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> 1388 <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> 1389 <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> 1390 <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> 1391 <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span> 1392 (editor) 1393 <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> 1394 <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span> 1395 (editor) 1396 <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> 1397 <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> 1370 <div class="avoidbreak"> 1371 <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1> 1372 <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span> 1373 (editor) 1374 <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 href="mailto:fielding@gbiv.com"><span class="email">fielding@gbiv.com</span></a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/" class="url">http://roy.gbiv.com/</a></span></address> 1375 <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 href="mailto:jg@laptop.org"><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> 1376 <address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Hewlett-Packard Company</span><span class="adr"><span class="street-address vcardline">HP Labs, Large Scale Systems Group</span><span class="street-address vcardline">1501 Page Mill Road, MS 1177</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">CA</span> <span class="postal-code">94304</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:JeffMogul@acm.org"><span class="email">JeffMogul@acm.org</span></a></span></address> 1377 <address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span> <span class="postal-code">98052</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:henrikn@microsoft.com"><span class="email">henrikn@microsoft.com</span></a></span></address> 1378 <address class="vcard"><span class="vcardline"><span class="fn">Larry Masinter</span><span class="n hidden"><span class="family-name">Masinter</span><span class="given-name">Larry</span></span></span><span class="org vcardline">Adobe Systems, Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span> <span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:LMM@acm.org"><span class="email">LMM@acm.org</span></a></span><span class="vcardline">URI: <a href="http://larry.masinter.net/" class="url">http://larry.masinter.net/</a></span></address> 1379 <address class="vcard"><span class="vcardline"><span class="fn">Paul J. Leach</span><span class="n hidden"><span class="family-name">Leach</span><span class="given-name">Paul J.</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span> <span class="postal-code">98052</span></span></span><span class="vcardline">EMail: <a href="mailto:paulle@microsoft.com"><span class="email">paulle@microsoft.com</span></a></span></address> 1380 <address class="vcard"><span class="vcardline"><span class="fn">Tim Berners-Lee</span><span class="n hidden"><span class="family-name">Berners-Lee</span><span class="given-name">Tim</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Computer Science and Artificial Intelligence Laboratory</span><span class="street-address vcardline">The Stata Center, Building 32</span><span class="street-address vcardline">32 Vassar Street</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span> <span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:timbl@w3.org"><span class="email">timbl@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.w3.org/People/Berners-Lee/" class="url">http://www.w3.org/People/Berners-Lee/</a></span></address> 1381 <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span> 1382 (editor) 1383 <span class="n hidden"><span class="family-name">Lafon</span><span class="given-name">Yves</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">W3C / ERCIM</span><span class="street-address vcardline">2004, rte des Lucioles</span><span class="vcardline"><span class="locality">Sophia-Antipolis</span>, <span class="region">AM</span> <span class="postal-code">06902</span></span><span class="country-name vcardline">France</span></span><span class="vcardline">EMail: <a href="mailto:ylafon@w3.org"><span class="email">ylafon@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.raubacapeu.net/people/yves/" class="url">http://www.raubacapeu.net/people/yves/</a></span></address> 1384 <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span> 1385 (editor) 1386 <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span> <span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">EMail: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address> 1387 </div> 1388 <h1 id="rfc.section.A" class="np"><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> 1398 1389 <p id="rfc.section.A.p.1">HTTP/1.1 uses many of the constructs defined for Internet Mail (<a href="#RFC2822" id="rfc.xref.RFC2822.1"><cite title="Internet Message Format">[RFC2822]</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 1399 1390 discusses mail, and HTTP has a few features that are different from those described in RFC 2045. These differences were carefully … … 1543 1534 <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li> 1544 1535 </ul> 1536 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1537 <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> 1538 </p> 1539 <div class="print2col"> 1540 <ul class="ind"> 1541 <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul> 1542 <li>Accept header <a href="#rfc.xref.header.accept.1">3.3</a>, <a href="#rfc.xref.header.accept.2">5.1</a>, <a href="#rfc.iref.a.1"><b>6.1</b></a></li> 1543 <li>Accept-Charset header <a href="#rfc.xref.header.accept-charset.1">5.1</a>, <a href="#rfc.iref.a.2"><b>6.2</b></a>, <a href="#rfc.xref.header.accept-charset.2">C.1</a></li> 1544 <li>Accept-Encoding header <a href="#rfc.xref.header.accept-encoding.1">3.2</a>, <a href="#rfc.xref.header.accept-encoding.2">5.1</a>, <a href="#rfc.iref.a.3"><b>6.3</b></a></li> 1545 <li>Accept-Language header <a href="#rfc.xref.header.accept-language.1">5.1</a>, <a href="#rfc.iref.a.4"><b>6.4</b></a></li> 1546 <li>Alternates header <a href="#rfc.iref.a.5"><b>C.1</b></a></li> 1547 </ul> 1548 </li> 1549 <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul> 1550 <li>compress <a href="#rfc.iref.c.1">3.2</a></li> 1551 <li>Content-Base header <a href="#rfc.iref.c.9"><b>C.1</b></a></li> 1552 <li>Content-Disposition header <a href="#rfc.xref.content-disposition.1">8.2</a>, <a href="#rfc.iref.c.7"><b>B.1</b></a></li> 1553 <li>Content-Encoding header <a href="#rfc.xref.header.content-encoding.1">3.2</a>, <a href="#rfc.xref.header.content-encoding.2">4.1</a>, <a href="#rfc.iref.c.2"><b>6.5</b></a>, <a href="#rfc.xref.header.content-encoding.3">6.5</a></li> 1554 <li>Content-Language header <a href="#rfc.xref.header.content-language.1">4.1</a>, <a href="#rfc.iref.c.3"><b>6.6</b></a></li> 1555 <li>Content-Location header <a href="#rfc.xref.header.content-location.1">4.1</a>, <a href="#rfc.iref.c.4"><b>6.7</b></a></li> 1556 <li>Content-MD5 header <a href="#rfc.xref.header.content-md5.1">4.1</a>, <a href="#rfc.iref.c.5"><b>6.8</b></a></li> 1557 <li>Content-Type header <a href="#rfc.xref.header.content-type.1">3.3</a>, <a href="#rfc.xref.header.content-type.2">4.1</a>, <a href="#rfc.iref.c.6"><b>6.9</b></a></li> 1558 <li>Content-Version header <a href="#rfc.iref.c.8"><b>C.1</b></a></li> 1559 </ul> 1560 </li> 1561 <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul> 1562 <li>deflate <a href="#rfc.iref.d.1">3.2</a></li> 1563 <li>Derived-From header <a href="#rfc.iref.d.2"><b>C.1</b></a></li> 1564 </ul> 1565 </li> 1566 <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul> 1567 <li><tt>Grammar</tt> 1568 <ul> 1569 <li><tt>Accept</tt> <a href="#rfc.iref.g.17"><b>6.1</b></a></li> 1570 <li><tt>Accept-Charset</tt> <a href="#rfc.iref.g.21"><b>6.2</b></a></li> 1571 <li><tt>Accept-Encoding</tt> <a href="#rfc.iref.g.22"><b>6.3</b></a></li> 1572 <li><tt>accept-extension</tt> <a href="#rfc.iref.g.20"><b>6.1</b></a></li> 1573 <li><tt>Accept-Language</tt> <a href="#rfc.iref.g.24"><b>6.4</b></a></li> 1574 <li><tt>accept-params</tt> <a href="#rfc.iref.g.19"><b>6.1</b></a></li> 1575 <li><tt>attribute</tt> <a href="#rfc.iref.g.8"><b>3.3</b></a></li> 1576 <li><tt>charset</tt> <a href="#rfc.iref.g.1"><b>3.1</b></a></li> 1577 <li><tt>codings</tt> <a href="#rfc.iref.g.23"><b>6.3</b></a></li> 1578 <li><tt>content-coding</tt> <a href="#rfc.iref.g.2"><b>3.2</b></a></li> 1579 <li><tt>content-disposition</tt> <a href="#rfc.iref.g.33"><b>B.1</b></a></li> 1580 <li><tt>Content-Encoding</tt> <a href="#rfc.iref.g.26"><b>6.5</b></a></li> 1581 <li><tt>Content-Language</tt> <a href="#rfc.iref.g.27"><b>6.6</b></a></li> 1582 <li><tt>Content-Location</tt> <a href="#rfc.iref.g.28"><b>6.7</b></a></li> 1583 <li><tt>Content-MD5</tt> <a href="#rfc.iref.g.29"><b>6.8</b></a></li> 1584 <li><tt>Content-Type</tt> <a href="#rfc.iref.g.31"><b>6.9</b></a></li> 1585 <li><tt>disp-extension-parm</tt> <a href="#rfc.iref.g.38"><b>B.1</b></a></li> 1586 <li><tt>disp-extension-token</tt> <a href="#rfc.iref.g.37"><b>B.1</b></a></li> 1587 <li><tt>disposition-parm</tt> <a href="#rfc.iref.g.35"><b>B.1</b></a></li> 1588 <li><tt>disposition-type</tt> <a href="#rfc.iref.g.34"><b>B.1</b></a></li> 1589 <li><tt>entity-body</tt> <a href="#rfc.iref.g.16"><b>4.2</b></a></li> 1590 <li><tt>entity-header</tt> <a href="#rfc.iref.g.14"><b>4.1</b></a></li> 1591 <li><tt>extension-header</tt> <a href="#rfc.iref.g.15"><b>4.1</b></a></li> 1592 <li><tt>filename-parm</tt> <a href="#rfc.iref.g.36"><b>B.1</b></a></li> 1593 <li><tt>language-range</tt> <a href="#rfc.iref.g.25"><b>6.4</b></a></li> 1594 <li><tt>language-tag</tt> <a href="#rfc.iref.g.11"><b>3.5</b></a></li> 1595 <li><tt>md5-digest</tt> <a href="#rfc.iref.g.30"><b>6.8</b></a></li> 1596 <li><tt>media-range</tt> <a href="#rfc.iref.g.18"><b>6.1</b></a></li> 1597 <li><tt>media-type</tt> <a href="#rfc.iref.g.4"><b>3.3</b></a></li> 1598 <li><tt>MIME-Version</tt> <a href="#rfc.iref.g.32"><b>A.1</b></a></li> 1599 <li><tt>parameter</tt> <a href="#rfc.iref.g.7"><b>3.3</b></a></li> 1600 <li><tt>primary-tag</tt> <a href="#rfc.iref.g.12"><b>3.5</b></a></li> 1601 <li><tt>qvalue</tt> <a href="#rfc.iref.g.10"><b>3.4</b></a></li> 1602 <li><tt>subtag</tt> <a href="#rfc.iref.g.13"><b>3.5</b></a></li> 1603 <li><tt>subtype</tt> <a href="#rfc.iref.g.6"><b>3.3</b></a></li> 1604 <li><tt>type</tt> <a href="#rfc.iref.g.5"><b>3.3</b></a></li> 1605 <li><tt>value</tt> <a href="#rfc.iref.g.9"><b>3.3</b></a></li> 1606 </ul> 1607 </li> 1608 <li>gzip <a href="#rfc.iref.g.3">3.2</a></li> 1609 </ul> 1610 </li> 1611 <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul> 1612 <li>Headers 1613 <ul> 1614 <li>Accept <a href="#rfc.xref.header.accept.1">3.3</a>, <a href="#rfc.xref.header.accept.2">5.1</a>, <a href="#rfc.iref.h.1"><b>6.1</b></a></li> 1615 <li>Accept-Charset <a href="#rfc.xref.header.accept-charset.1">5.1</a>, <a href="#rfc.iref.h.2"><b>6.2</b></a>, <a href="#rfc.xref.header.accept-charset.2">C.1</a></li> 1616 <li>Accept-Encoding <a href="#rfc.xref.header.accept-encoding.1">3.2</a>, <a href="#rfc.xref.header.accept-encoding.2">5.1</a>, <a href="#rfc.iref.h.3"><b>6.3</b></a></li> 1617 <li>Accept-Language <a href="#rfc.xref.header.accept-language.1">5.1</a>, <a href="#rfc.iref.h.4"><b>6.4</b></a></li> 1618 <li>Alternate <a href="#rfc.iref.h.11"><b>C.1</b></a></li> 1619 <li>Content-Base <a href="#rfc.iref.h.17"><b>C.1</b></a></li> 1620 <li>Content-Disposition <a href="#rfc.xref.content-disposition.1">8.2</a>, <a href="#rfc.iref.h.10"><b>B.1</b></a></li> 1621 <li>Content-Encoding <a href="#rfc.xref.header.content-encoding.1">3.2</a>, <a href="#rfc.xref.header.content-encoding.2">4.1</a>, <a href="#rfc.iref.h.5"><b>6.5</b></a>, <a href="#rfc.xref.header.content-encoding.3">6.5</a></li> 1622 <li>Content-Language <a href="#rfc.xref.header.content-language.1">4.1</a>, <a href="#rfc.iref.h.6"><b>6.6</b></a></li> 1623 <li>Content-Location <a href="#rfc.xref.header.content-location.1">4.1</a>, <a href="#rfc.iref.h.7"><b>6.7</b></a></li> 1624 <li>Content-MD5 <a href="#rfc.xref.header.content-md5.1">4.1</a>, <a href="#rfc.iref.h.8"><b>6.8</b></a></li> 1625 <li>Content-Type <a href="#rfc.xref.header.content-type.1">3.3</a>, <a href="#rfc.xref.header.content-type.2">4.1</a>, <a href="#rfc.iref.h.9"><b>6.9</b></a></li> 1626 <li>Content-Version <a href="#rfc.iref.h.12"><b>C.1</b></a></li> 1627 <li>Derived-From <a href="#rfc.iref.h.13"><b>C.1</b></a></li> 1628 <li>Link <a href="#rfc.iref.h.14"><b>C.1</b></a></li> 1629 <li>Public <a href="#rfc.iref.h.16"><b>C.1</b></a></li> 1630 <li>URI <a href="#rfc.iref.h.15"><b>C.1</b></a></li> 1631 </ul> 1632 </li> 1633 </ul> 1634 </li> 1635 <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul> 1636 <li>identity <a href="#rfc.iref.i.1">3.2</a></li> 1637 <li><em>ISO-8859-1</em> <a href="#rfc.xref.ISO-8859-1.1">3.1.1</a>, <a href="#ISO-8859-1"><b>10.1</b></a></li> 1638 </ul> 1639 </li> 1640 <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul> 1641 <li>Link header <a href="#rfc.iref.l.1"><b>C.1</b></a></li> 1642 </ul> 1643 </li> 1644 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 1645 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">2</a>, <a href="#rfc.xref.Part1.2">2</a>, <a href="#rfc.xref.Part1.3">2</a>, <a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.7">2</a>, <a href="#rfc.xref.Part1.8">2</a>, <a href="#rfc.xref.Part1.9">2</a>, <a href="#rfc.xref.Part1.10">2</a>, <a href="#rfc.xref.Part1.11">2</a>, <a href="#rfc.xref.Part1.12">4.1</a>, <a href="#rfc.xref.Part1.13">4.2</a>, <a href="#rfc.xref.Part1.14">4.2.2</a>, <a href="#Part1"><b>10.1</b></a>, <a href="#rfc.xref.Part1.15">A.5</a>, <a href="#rfc.xref.Part1.16">C.1</a><ul> 1646 <li><em>Section 2.1</em> <a href="#rfc.xref.Part1.1">2</a></li> 1647 <li><em>Section 2.2</em> <a href="#rfc.xref.Part1.2">2</a>, <a href="#rfc.xref.Part1.3">2</a>, <a href="#rfc.xref.Part1.4">2</a>, <a href="#rfc.xref.Part1.5">2</a>, <a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.7">2</a></li> 1648 <li><em>Section 3.2.1</em> <a href="#rfc.xref.Part1.8">2</a>, <a href="#rfc.xref.Part1.10">2</a></li> 1649 <li><em>Section 4.2</em> <a href="#rfc.xref.Part1.11">2</a></li> 1650 <li><em>Section 4.3</em> <a href="#rfc.xref.Part1.13">4.2</a></li> 1651 <li><em>Section 4.4</em> <a href="#rfc.xref.Part1.14">4.2.2</a></li> 1652 <li><em>Section 8.2</em> <a href="#rfc.xref.Part1.9">2</a>, <a href="#rfc.xref.Part1.12">4.1</a></li> 1653 <li><em>Section 8.7</em> <a href="#rfc.xref.Part1.15">A.5</a></li> 1654 </ul> 1655 </li> 1656 <li><em>Part2</em> <a href="#rfc.xref.Part2.1">2</a>, <a href="#rfc.xref.Part2.2">4.1</a>, <a href="#rfc.xref.Part2.3">5.1</a>, <a href="#Part2"><b>10.1</b></a><ul> 1657 <li><em>Section 10.1</em> <a href="#rfc.xref.Part2.1">2</a>, <a href="#rfc.xref.Part2.2">4.1</a></li> 1658 <li><em>Section 10.9</em> <a href="#rfc.xref.Part2.3">5.1</a></li> 1659 </ul> 1660 </li> 1661 <li><em>Part4</em> <a href="#rfc.xref.Part4.1">2</a>, <a href="#rfc.xref.Part4.2">4.1</a>, <a href="#Part4"><b>10.1</b></a><ul> 1662 <li><em>Section 7.6</em> <a href="#rfc.xref.Part4.1">2</a>, <a href="#rfc.xref.Part4.2">4.1</a></li> 1663 </ul> 1664 </li> 1665 <li><em>Part5</em> <a href="#rfc.xref.Part5.1">2</a>, <a href="#rfc.xref.Part5.2">3.3.2</a>, <a href="#rfc.xref.Part5.3">4.1</a>, <a href="#Part5"><b>10.1</b></a>, <a href="#rfc.xref.Part5.4">C.1</a><ul> 1666 <li><em>Section 6.2</em> <a href="#rfc.xref.Part5.1">2</a>, <a href="#rfc.xref.Part5.3">4.1</a></li> 1667 <li><em>Appendix A</em> <a href="#rfc.xref.Part5.2">3.3.2</a></li> 1668 </ul> 1669 </li> 1670 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">2</a>, <a href="#rfc.xref.Part6.2">4.1</a>, <a href="#rfc.xref.Part6.3">5.1</a>, <a href="#rfc.xref.Part6.4">6.7</a>, <a href="#Part6"><b>10.1</b></a>, <a href="#rfc.xref.Part6.5">C.1</a><ul> 1671 <li><em>Section 8</em> <a href="#rfc.xref.Part6.4">6.7</a></li> 1672 <li><em>Section 16.3</em> <a href="#rfc.xref.Part6.1">2</a>, <a href="#rfc.xref.Part6.2">4.1</a></li> 1673 <li><em>Section 16.5</em> <a href="#rfc.xref.Part6.3">5.1</a></li> 1674 </ul> 1675 </li> 1676 <li>Public header <a href="#rfc.iref.p.1"><b>C.1</b></a></li> 1677 </ul> 1678 </li> 1679 <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul> 1680 <li><em>RFC1766</em> <a href="#rfc.xref.RFC1766.1">3.5</a>, <a href="#RFC1766"><b>10.1</b></a></li> 1681 <li><em>RFC1806</em> <a href="#rfc.xref.RFC1806.1">8.2</a>, <a href="#rfc.xref.RFC1806.2">8.2</a>, <a href="#RFC1806"><b>10.2</b></a>, <a href="#rfc.xref.RFC1806.3">B.1</a></li> 1682 <li><em>RFC1864</em> <a href="#rfc.xref.RFC1864.1">6.8</a>, <a href="#rfc.xref.RFC1864.2">6.8</a>, <a href="#RFC1864"><b>10.1</b></a></li> 1683 <li><em>RFC1945</em> <a href="#RFC1945"><b>10.2</b></a>, <a href="#rfc.xref.RFC1945.1">B</a></li> 1684 <li><em>RFC1950</em> <a href="#rfc.xref.RFC1950.1">3.2</a>, <a href="#RFC1950"><b>10.1</b></a></li> 1685 <li><em>RFC1951</em> <a href="#rfc.xref.RFC1951.1">3.2</a>, <a href="#RFC1951"><b>10.1</b></a></li> 1686 <li><em>RFC1952</em> <a href="#rfc.xref.RFC1952.1">3.2</a>, <a href="#RFC1952"><b>10.1</b></a></li> 1687 <li><em>RFC2045</em> <a href="#RFC2045"><b>10.1</b></a>, <a href="#rfc.xref.RFC2045.1">A</a>, <a href="#rfc.xref.RFC2045.2">A.1</a>, <a href="#rfc.xref.RFC2045.3">A.2</a></li> 1688 <li><em>RFC2046</em> <a href="#rfc.xref.RFC2046.1">3.3</a>, <a href="#rfc.xref.RFC2046.2">3.3.2</a>, <a href="#RFC2046"><b>10.1</b></a>, <a href="#rfc.xref.RFC2046.3">A.2</a><ul> 1689 <li><em>Section 5.1.1</em> <a href="#rfc.xref.RFC2046.2">3.3.2</a></li> 1690 </ul> 1691 </li> 1692 <li><em>RFC2049</em> <a href="#RFC2049"><b>10.2</b></a>, <a href="#rfc.xref.RFC2049.1">A.2</a><ul> 1693 <li><em>Section 4</em> <a href="#rfc.xref.RFC2049.1">A.2</a></li> 1694 </ul> 1695 </li> 1696 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">10.1</a>, <a href="#rfc.xref.RFC2068.2">10.1</a>, <a href="#rfc.xref.RFC2068.3">10.1</a>, <a href="#RFC2068"><b>10.2</b></a>, <a href="#rfc.xref.RFC2068.4">B</a>, <a href="#rfc.xref.RFC2068.5">C.1</a></li> 1697 <li><em>RFC2076</em> <a href="#RFC2076"><b>10.2</b></a>, <a href="#rfc.xref.RFC2076.1">B</a></li> 1698 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>10.1</b></a></li> 1699 <li><em>RFC2183</em> <a href="#rfc.xref.RFC2183.1">8.2</a>, <a href="#RFC2183"><b>10.2</b></a></li> 1700 <li><em>RFC2277</em> <a href="#rfc.xref.RFC2277.1">3.1</a>, <a href="#RFC2277"><b>10.2</b></a></li> 1701 <li><em>RFC2388</em> <a href="#rfc.xref.RFC2388.1">3.3.2</a>, <a href="#RFC2388"><b>10.2</b></a></li> 1702 <li><em>RFC2557</em> <a href="#RFC2557"><b>10.2</b></a>, <a href="#rfc.xref.RFC2557.1">A.6</a>, <a href="#rfc.xref.RFC2557.2">C.1</a></li> 1703 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">1</a>, <a href="#RFC2616"><b>10.2</b></a>, <a href="#rfc.xref.RFC2616.2">D.1</a></li> 1704 <li><em>RFC2822</em> <a href="#RFC2822"><b>10.2</b></a>, <a href="#rfc.xref.RFC2822.1">A</a></li> 1705 <li><em>RFC3629</em> <a href="#rfc.xref.RFC3629.1">3.1</a>, <a href="#RFC3629"><b>10.2</b></a></li> 1706 <li><em>RFC4288</em> <a href="#rfc.xref.RFC4288.1">3.3</a>, <a href="#RFC4288"><b>10.2</b></a></li> 1707 </ul> 1708 </li> 1709 <li><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul> 1710 <li>URI header <a href="#rfc.iref.u.1"><b>C.1</b></a></li> 1711 </ul> 1712 </li> 1713 </ul> 1714 </div> 1545 1715 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> 1716 <p>Copyright © The IETF Trust (2008).</p> 1546 1717 <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the 1547 1718 authors retain all their rights. … … 1561 1732 <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result 1562 1733 of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users 1563 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>>.1734 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>. 1564 1735 </p> 1565 1736 <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary … … 1567 1738 at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>. 1568 1739 </p> 1569 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>1570 <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>1571 </p>1572 <div class="print2col">1573 <ul class="ind">1574 <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind">1575 <li class="indline1">Accept header <a class="iref" href="#rfc.xref.header.accept.1">3.3</a>, <a class="iref" href="#rfc.xref.header.accept.2">5.1</a>, <a class="iref" href="#rfc.iref.a.1"><b>6.1</b></a></li>1576 <li class="indline1">Accept-Charset header <a class="iref" href="#rfc.xref.header.accept-charset.1">5.1</a>, <a class="iref" href="#rfc.iref.a.2"><b>6.2</b></a>, <a class="iref" href="#rfc.xref.header.accept-charset.2">C.1</a></li>1577 <li class="indline1">Accept-Encoding header <a class="iref" href="#rfc.xref.header.accept-encoding.1">3.2</a>, <a class="iref" href="#rfc.xref.header.accept-encoding.2">5.1</a>, <a class="iref" href="#rfc.iref.a.3"><b>6.3</b></a></li>1578 <li class="indline1">Accept-Language header <a class="iref" href="#rfc.xref.header.accept-language.1">5.1</a>, <a class="iref" href="#rfc.iref.a.4"><b>6.4</b></a></li>1579 <li class="indline1">Alternates header <a class="iref" href="#rfc.iref.a.5"><b>C.1</b></a></li>1580 </ul>1581 </li>1582 <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">1583 <li class="indline1">compress <a class="iref" href="#rfc.iref.c.1">3.2</a></li>1584 <li class="indline1">Content-Base header <a class="iref" href="#rfc.iref.c.9"><b>C.1</b></a></li>1585 <li class="indline1">Content-Disposition header <a class="iref" href="#rfc.xref.content-disposition.1">8.2</a>, <a class="iref" href="#rfc.iref.c.7"><b>B.1</b></a></li>1586 <li class="indline1">Content-Encoding header <a class="iref" href="#rfc.xref.header.content-encoding.1">3.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">4.1</a>, <a class="iref" href="#rfc.iref.c.2"><b>6.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">6.5</a></li>1587 <li class="indline1">Content-Language header <a class="iref" href="#rfc.xref.header.content-language.1">4.1</a>, <a class="iref" href="#rfc.iref.c.3"><b>6.6</b></a></li>1588 <li class="indline1">Content-Location header <a class="iref" href="#rfc.xref.header.content-location.1">4.1</a>, <a class="iref" href="#rfc.iref.c.4"><b>6.7</b></a></li>1589 <li class="indline1">Content-MD5 header <a class="iref" href="#rfc.xref.header.content-md5.1">4.1</a>, <a class="iref" href="#rfc.iref.c.5"><b>6.8</b></a></li>1590 <li class="indline1">Content-Type header <a class="iref" href="#rfc.xref.header.content-type.1">3.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">4.1</a>, <a class="iref" href="#rfc.iref.c.6"><b>6.9</b></a></li>1591 <li class="indline1">Content-Version header <a class="iref" href="#rfc.iref.c.8"><b>C.1</b></a></li>1592 </ul>1593 </li>1594 <li class="indline0"><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul class="ind">1595 <li class="indline1">deflate <a class="iref" href="#rfc.iref.d.1">3.2</a></li>1596 <li class="indline1">Derived-From header <a class="iref" href="#rfc.iref.d.2"><b>C.1</b></a></li>1597 </ul>1598 </li>1599 <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind">1600 <li class="indline1"><tt>Grammar</tt> 1601 <ul class="ind">1602 <li class="indline1"><tt>Accept</tt> <a class="iref" href="#rfc.iref.g.17"><b>6.1</b></a></li>1603 <li class="indline1"><tt>Accept-Charset</tt> <a class="iref" href="#rfc.iref.g.21"><b>6.2</b></a></li>1604 <li class="indline1"><tt>Accept-Encoding</tt> <a class="iref" href="#rfc.iref.g.22"><b>6.3</b></a></li>1605 <li class="indline1"><tt>accept-extension</tt> <a class="iref" href="#rfc.iref.g.20"><b>6.1</b></a></li>1606 <li class="indline1"><tt>Accept-Language</tt> <a class="iref" href="#rfc.iref.g.24"><b>6.4</b></a></li>1607 <li class="indline1"><tt>accept-params</tt> <a class="iref" href="#rfc.iref.g.19"><b>6.1</b></a></li>1608 <li class="indline1"><tt>attribute</tt> <a class="iref" href="#rfc.iref.g.8"><b>3.3</b></a></li>1609 <li class="indline1"><tt>charset</tt> <a class="iref" href="#rfc.iref.g.1"><b>3.1</b></a></li>1610 <li class="indline1"><tt>codings</tt> <a class="iref" href="#rfc.iref.g.23"><b>6.3</b></a></li>1611 <li class="indline1"><tt>content-coding</tt> <a class="iref" href="#rfc.iref.g.2"><b>3.2</b></a></li>1612 <li class="indline1"><tt>content-disposition</tt> <a class="iref" href="#rfc.iref.g.33"><b>B.1</b></a></li>1613 <li class="indline1"><tt>Content-Encoding</tt> <a class="iref" href="#rfc.iref.g.26"><b>6.5</b></a></li>1614 <li class="indline1"><tt>Content-Language</tt> <a class="iref" href="#rfc.iref.g.27"><b>6.6</b></a></li>1615 <li class="indline1"><tt>Content-Location</tt> <a class="iref" href="#rfc.iref.g.28"><b>6.7</b></a></li>1616 <li class="indline1"><tt>Content-MD5</tt> <a class="iref" href="#rfc.iref.g.29"><b>6.8</b></a></li>1617 <li class="indline1"><tt>Content-Type</tt> <a class="iref" href="#rfc.iref.g.31"><b>6.9</b></a></li>1618 <li class="indline1"><tt>disp-extension-parm</tt> <a class="iref" href="#rfc.iref.g.38"><b>B.1</b></a></li>1619 <li class="indline1"><tt>disp-extension-token</tt> <a class="iref" href="#rfc.iref.g.37"><b>B.1</b></a></li>1620 <li class="indline1"><tt>disposition-parm</tt> <a class="iref" href="#rfc.iref.g.35"><b>B.1</b></a></li>1621 <li class="indline1"><tt>disposition-type</tt> <a class="iref" href="#rfc.iref.g.34"><b>B.1</b></a></li>1622 <li class="indline1"><tt>entity-body</tt> <a class="iref" href="#rfc.iref.g.16"><b>4.2</b></a></li>1623 <li class="indline1"><tt>entity-header</tt> <a class="iref" href="#rfc.iref.g.14"><b>4.1</b></a></li>1624 <li class="indline1"><tt>extension-header</tt> <a class="iref" href="#rfc.iref.g.15"><b>4.1</b></a></li>1625 <li class="indline1"><tt>filename-parm</tt> <a class="iref" href="#rfc.iref.g.36"><b>B.1</b></a></li>1626 <li class="indline1"><tt>language-range</tt> <a class="iref" href="#rfc.iref.g.25"><b>6.4</b></a></li>1627 <li class="indline1"><tt>language-tag</tt> <a class="iref" href="#rfc.iref.g.11"><b>3.5</b></a></li>1628 <li class="indline1"><tt>md5-digest</tt> <a class="iref" href="#rfc.iref.g.30"><b>6.8</b></a></li>1629 <li class="indline1"><tt>media-range</tt> <a class="iref" href="#rfc.iref.g.18"><b>6.1</b></a></li>1630 <li class="indline1"><tt>media-type</tt> <a class="iref" href="#rfc.iref.g.4"><b>3.3</b></a></li>1631 <li class="indline1"><tt>MIME-Version</tt> <a class="iref" href="#rfc.iref.g.32"><b>A.1</b></a></li>1632 <li class="indline1"><tt>parameter</tt> <a class="iref" href="#rfc.iref.g.7"><b>3.3</b></a></li>1633 <li class="indline1"><tt>primary-tag</tt> <a class="iref" href="#rfc.iref.g.12"><b>3.5</b></a></li>1634 <li class="indline1"><tt>qvalue</tt> <a class="iref" href="#rfc.iref.g.10"><b>3.4</b></a></li>1635 <li class="indline1"><tt>subtag</tt> <a class="iref" href="#rfc.iref.g.13"><b>3.5</b></a></li>1636 <li class="indline1"><tt>subtype</tt> <a class="iref" href="#rfc.iref.g.6"><b>3.3</b></a></li>1637 <li class="indline1"><tt>type</tt> <a class="iref" href="#rfc.iref.g.5"><b>3.3</b></a></li>1638 <li class="indline1"><tt>value</tt> <a class="iref" href="#rfc.iref.g.9"><b>3.3</b></a></li>1639 </ul>1640 </li>1641 <li class="indline1">gzip <a class="iref" href="#rfc.iref.g.3">3.2</a></li>1642 </ul>1643 </li>1644 <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">1645 <li class="indline1">Headers 1646 <ul class="ind">1647 <li class="indline1">Accept <a class="iref" href="#rfc.xref.header.accept.1">3.3</a>, <a class="iref" href="#rfc.xref.header.accept.2">5.1</a>, <a class="iref" href="#rfc.iref.h.1"><b>6.1</b></a></li>1648 <li class="indline1">Accept-Charset <a class="iref" href="#rfc.xref.header.accept-charset.1">5.1</a>, <a class="iref" href="#rfc.iref.h.2"><b>6.2</b></a>, <a class="iref" href="#rfc.xref.header.accept-charset.2">C.1</a></li>1649 <li class="indline1">Accept-Encoding <a class="iref" href="#rfc.xref.header.accept-encoding.1">3.2</a>, <a class="iref" href="#rfc.xref.header.accept-encoding.2">5.1</a>, <a class="iref" href="#rfc.iref.h.3"><b>6.3</b></a></li>1650 <li class="indline1">Accept-Language <a class="iref" href="#rfc.xref.header.accept-language.1">5.1</a>, <a class="iref" href="#rfc.iref.h.4"><b>6.4</b></a></li>1651 <li class="indline1">Alternate <a class="iref" href="#rfc.iref.h.11"><b>C.1</b></a></li>1652 <li class="indline1">Content-Base <a class="iref" href="#rfc.iref.h.17"><b>C.1</b></a></li>1653 <li class="indline1">Content-Disposition <a class="iref" href="#rfc.xref.content-disposition.1">8.2</a>, <a class="iref" href="#rfc.iref.h.10"><b>B.1</b></a></li>1654 <li class="indline1">Content-Encoding <a class="iref" href="#rfc.xref.header.content-encoding.1">3.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">4.1</a>, <a class="iref" href="#rfc.iref.h.5"><b>6.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">6.5</a></li>1655 <li class="indline1">Content-Language <a class="iref" href="#rfc.xref.header.content-language.1">4.1</a>, <a class="iref" href="#rfc.iref.h.6"><b>6.6</b></a></li>1656 <li class="indline1">Content-Location <a class="iref" href="#rfc.xref.header.content-location.1">4.1</a>, <a class="iref" href="#rfc.iref.h.7"><b>6.7</b></a></li>1657 <li class="indline1">Content-MD5 <a class="iref" href="#rfc.xref.header.content-md5.1">4.1</a>, <a class="iref" href="#rfc.iref.h.8"><b>6.8</b></a></li>1658 <li class="indline1">Content-Type <a class="iref" href="#rfc.xref.header.content-type.1">3.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">4.1</a>, <a class="iref" href="#rfc.iref.h.9"><b>6.9</b></a></li>1659 <li class="indline1">Content-Version <a class="iref" href="#rfc.iref.h.12"><b>C.1</b></a></li>1660 <li class="indline1">Derived-From <a class="iref" href="#rfc.iref.h.13"><b>C.1</b></a></li>1661 <li class="indline1">Link <a class="iref" href="#rfc.iref.h.14"><b>C.1</b></a></li>1662 <li class="indline1">Public <a class="iref" href="#rfc.iref.h.16"><b>C.1</b></a></li>1663 <li class="indline1">URI <a class="iref" href="#rfc.iref.h.15"><b>C.1</b></a></li>1664 </ul>1665 </li>1666 </ul>1667 </li>1668 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">1669 <li class="indline1">identity <a class="iref" href="#rfc.iref.i.1">3.2</a></li>1670 <li class="indline1"><em>ISO-8859-1</em> <a class="iref" href="#rfc.xref.ISO-8859-1.1">3.1.1</a>, <a class="iref" href="#ISO-8859-1"><b>10.1</b></a></li>1671 </ul>1672 </li>1673 <li class="indline0"><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul class="ind">1674 <li class="indline1">Link header <a class="iref" href="#rfc.iref.l.1"><b>C.1</b></a></li>1675 </ul>1676 </li>1677 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">1678 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">2</a>, <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a>, <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a>, <a class="iref" href="#rfc.xref.Part1.11">2</a>, <a class="iref" href="#rfc.xref.Part1.12">4.1</a>, <a class="iref" href="#rfc.xref.Part1.13">4.2</a>, <a class="iref" href="#rfc.xref.Part1.14">4.2.2</a>, <a class="iref" href="#Part1"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part1.15">A.5</a>, <a class="iref" href="#rfc.xref.Part1.16">C.1</a><ul class="ind">1679 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.Part1.1">2</a></li>1680 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a></li>1681 <li class="indline1"><em>Section 3.2.1</em> <a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a></li>1682 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part1.11">2</a></li>1683 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.13">4.2</a></li>1684 <li class="indline1"><em>Section 4.4</em> <a class="iref" href="#rfc.xref.Part1.14">4.2.2</a></li>1685 <li class="indline1"><em>Section 8.2</em> <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.12">4.1</a></li>1686 <li class="indline1"><em>Section 8.7</em> <a class="iref" href="#rfc.xref.Part1.15">A.5</a></li>1687 </ul>1688 </li>1689 <li class="indline1"><em>Part2</em> <a class="iref" href="#rfc.xref.Part2.1">2</a>, <a class="iref" href="#rfc.xref.Part2.2">4.1</a>, <a class="iref" href="#rfc.xref.Part2.3">5.1</a>, <a class="iref" href="#Part2"><b>10.1</b></a><ul class="ind">1690 <li class="indline1"><em>Section 10.1</em> <a class="iref" href="#rfc.xref.Part2.1">2</a>, <a class="iref" href="#rfc.xref.Part2.2">4.1</a></li>1691 <li class="indline1"><em>Section 10.9</em> <a class="iref" href="#rfc.xref.Part2.3">5.1</a></li>1692 </ul>1693 </li>1694 <li class="indline1"><em>Part4</em> <a class="iref" href="#rfc.xref.Part4.1">2</a>, <a class="iref" href="#rfc.xref.Part4.2">4.1</a>, <a class="iref" href="#Part4"><b>10.1</b></a><ul class="ind">1695 <li class="indline1"><em>Section 7.6</em> <a class="iref" href="#rfc.xref.Part4.1">2</a>, <a class="iref" href="#rfc.xref.Part4.2">4.1</a></li>1696 </ul>1697 </li>1698 <li class="indline1"><em>Part5</em> <a class="iref" href="#rfc.xref.Part5.1">2</a>, <a class="iref" href="#rfc.xref.Part5.2">3.3.2</a>, <a class="iref" href="#rfc.xref.Part5.3">4.1</a>, <a class="iref" href="#Part5"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part5.4">C.1</a><ul class="ind">1699 <li class="indline1"><em>Section 6.2</em> <a class="iref" href="#rfc.xref.Part5.1">2</a>, <a class="iref" href="#rfc.xref.Part5.3">4.1</a></li>1700 <li class="indline1"><em>Section A</em> <a class="iref" href="#rfc.xref.Part5.2">3.3.2</a></li>1701 </ul>1702 </li>1703 <li class="indline1"><em>Part6</em> <a class="iref" href="#rfc.xref.Part6.1">2</a>, <a class="iref" href="#rfc.xref.Part6.2">4.1</a>, <a class="iref" href="#rfc.xref.Part6.3">5.1</a>, <a class="iref" href="#rfc.xref.Part6.4">6.7</a>, <a class="iref" href="#Part6"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.Part6.5">C.1</a><ul class="ind">1704 <li class="indline1"><em>Section 8</em> <a class="iref" href="#rfc.xref.Part6.4">6.7</a></li>1705 <li class="indline1"><em>Section 16.3</em> <a class="iref" href="#rfc.xref.Part6.1">2</a>, <a class="iref" href="#rfc.xref.Part6.2">4.1</a></li>1706 <li class="indline1"><em>Section 16.5</em> <a class="iref" href="#rfc.xref.Part6.3">5.1</a></li>1707 </ul>1708 </li>1709 <li class="indline1">Public header <a class="iref" href="#rfc.iref.p.1"><b>C.1</b></a></li>1710 </ul>1711 </li>1712 <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">1713 <li class="indline1"><em>RFC1766</em> <a class="iref" href="#rfc.xref.RFC1766.1">3.5</a>, <a class="iref" href="#RFC1766"><b>10.1</b></a></li>1714 <li class="indline1"><em>RFC1806</em> <a class="iref" href="#rfc.xref.RFC1806.1">8.2</a>, <a class="iref" href="#rfc.xref.RFC1806.2">8.2</a>, <a class="iref" href="#RFC1806"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC1806.3">B.1</a></li>1715 <li class="indline1"><em>RFC1864</em> <a class="iref" href="#rfc.xref.RFC1864.1">6.8</a>, <a class="iref" href="#rfc.xref.RFC1864.2">6.8</a>, <a class="iref" href="#RFC1864"><b>10.1</b></a></li>1716 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#RFC1945"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li>1717 <li class="indline1"><em>RFC1950</em> <a class="iref" href="#rfc.xref.RFC1950.1">3.2</a>, <a class="iref" href="#RFC1950"><b>10.1</b></a></li>1718 <li class="indline1"><em>RFC1951</em> <a class="iref" href="#rfc.xref.RFC1951.1">3.2</a>, <a class="iref" href="#RFC1951"><b>10.1</b></a></li>1719 <li class="indline1"><em>RFC1952</em> <a class="iref" href="#rfc.xref.RFC1952.1">3.2</a>, <a class="iref" href="#RFC1952"><b>10.1</b></a></li>1720 <li class="indline1"><em>RFC2045</em> <a class="iref" href="#RFC2045"><b>10.1</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>1721 <li class="indline1"><em>RFC2046</em> <a class="iref" href="#rfc.xref.RFC2046.1">3.3</a>, <a class="iref" href="#rfc.xref.RFC2046.2">3.3.2</a>, <a class="iref" href="#RFC2046"><b>10.1</b></a>, <a class="iref" href="#rfc.xref.RFC2046.3">A.2</a><ul class="ind">1722 <li class="indline1"><em>Section 5.1.1</em> <a class="iref" href="#rfc.xref.RFC2046.2">3.3.2</a></li>1723 </ul>1724 </li>1725 <li class="indline1"><em>RFC2049</em> <a class="iref" href="#RFC2049"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2049.1">A.2</a><ul class="ind">1726 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.RFC2049.1">A.2</a></li>1727 </ul>1728 </li>1729 <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>10.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>1730 <li class="indline1"><em>RFC2076</em> <a class="iref" href="#RFC2076"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2076.1">B</a></li>1731 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>10.1</b></a></li>1732 <li class="indline1"><em>RFC2183</em> <a class="iref" href="#rfc.xref.RFC2183.1">8.2</a>, <a class="iref" href="#RFC2183"><b>10.2</b></a></li>1733 <li class="indline1"><em>RFC2277</em> <a class="iref" href="#rfc.xref.RFC2277.1">3.1</a>, <a class="iref" href="#RFC2277"><b>10.2</b></a></li>1734 <li class="indline1"><em>RFC2388</em> <a class="iref" href="#rfc.xref.RFC2388.1">3.3.2</a>, <a class="iref" href="#RFC2388"><b>10.2</b></a></li>1735 <li class="indline1"><em>RFC2557</em> <a class="iref" href="#RFC2557"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2557.1">A.6</a>, <a class="iref" href="#rfc.xref.RFC2557.2">C.1</a></li>1736 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">D.1</a></li>1737 <li class="indline1"><em>RFC2822</em> <a class="iref" href="#RFC2822"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2822.1">A</a></li>1738 <li class="indline1"><em>RFC3629</em> <a class="iref" href="#rfc.xref.RFC3629.1">3.1</a>, <a class="iref" href="#RFC3629"><b>10.2</b></a></li>1739 <li class="indline1"><em>RFC4288</em> <a class="iref" href="#rfc.xref.RFC4288.1">3.3</a>, <a class="iref" href="#RFC4288"><b>10.2</b></a></li>1740 </ul>1741 </li>1742 <li class="indline0"><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul class="ind">1743 <li class="indline1">URI header <a class="iref" href="#rfc.iref.u.1"><b>C.1</b></a></li>1744 </ul>1745 </li>1746 </ul>1747 </div>1748 1740 </body> 1749 1741 </html>
Note: See TracChangeset
for help on using the changeset viewer.
