Changeset 1099 for draft-ietf-httpbis/01/p3-payload.html
- Timestamp:
- 01/01/11 17:23:02 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/01/p3-payload.html
r230 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 { … … 348 339 <link rel="Appendix" title="C Compatibility with Previous Versions" href="#rfc.section.C"> 349 340 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 350 <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/"> 351 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 352 <meta name="DC.Creator" content="Fielding, R."> 353 <meta name="DC.Creator" content="Gettys, J."> 354 <meta name="DC.Creator" content="Mogul, J."> 355 <meta name="DC.Creator" content="Frystyk, H."> 356 <meta name="DC.Creator" content="Masinter, L."> 357 <meta name="DC.Creator" content="Leach, P."> 358 <meta name="DC.Creator" content="Berners-Lee, T."> 359 <meta name="DC.Creator" content="Lafon, Y."> 360 <meta name="DC.Creator" content="Reschke, J. F."> 361 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-01"> 362 <meta name="DC.Date.Issued" scheme="ISO8601" content="2008-01"> 363 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 364 <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."> 341 <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/"> 342 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 343 <meta name="dct.creator" content="Fielding, R."> 344 <meta name="dct.creator" content="Gettys, J."> 345 <meta name="dct.creator" content="Mogul, J."> 346 <meta name="dct.creator" content="Frystyk, H."> 347 <meta name="dct.creator" content="Masinter, L."> 348 <meta name="dct.creator" content="Leach, P."> 349 <meta name="dct.creator" content="Berners-Lee, T."> 350 <meta name="dct.creator" content="Lafon, Y."> 351 <meta name="dct.creator" content="Reschke, J. F."> 352 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-01"> 353 <meta name="dct.issued" scheme="ISO8601" content="2008-01-12"> 354 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 355 <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."> 356 <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."> 365 357 </head> 366 358 <body> 367 <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1"> 368 <tr> 369 <td class="header left">Network Working Group</td> 370 <td class="header right">R. Fielding, Editor</td> 371 </tr> 372 <tr> 373 <td class="header left">Internet Draft</td> 374 <td class="header right">Day Software</td> 375 </tr> 376 <tr> 377 <td class="header left"> 378 <draft-ietf-httpbis-p3-payload-01> 379 380 </td> 381 <td class="header right">J. Gettys</td> 382 </tr> 383 <tr> 384 <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 385 </td> 386 <td class="header right">One Laptop per Child</td> 387 </tr> 388 <tr> 389 <td class="header left">Intended status: Standards Track</td> 390 <td class="header right">J. Mogul</td> 391 </tr> 392 <tr> 393 <td class="header left">Expires: July 2008</td> 394 <td class="header right">HP</td> 395 </tr> 396 <tr> 397 <td class="header left"></td> 398 <td class="header right">H. Frystyk</td> 399 </tr> 400 <tr> 401 <td class="header left"></td> 402 <td class="header right">Microsoft</td> 403 </tr> 404 <tr> 405 <td class="header left"></td> 406 <td class="header right">L. Masinter</td> 407 </tr> 408 <tr> 409 <td class="header left"></td> 410 <td class="header right">Adobe Systems</td> 411 </tr> 412 <tr> 413 <td class="header left"></td> 414 <td class="header right">P. Leach</td> 415 </tr> 416 <tr> 417 <td class="header left"></td> 418 <td class="header right">Microsoft</td> 419 </tr> 420 <tr> 421 <td class="header left"></td> 422 <td class="header right">T. Berners-Lee</td> 423 </tr> 424 <tr> 425 <td class="header left"></td> 426 <td class="header right">W3C/MIT</td> 427 </tr> 428 <tr> 429 <td class="header left"></td> 430 <td class="header right">Y. Lafon, Editor</td> 431 </tr> 432 <tr> 433 <td class="header left"></td> 434 <td class="header right">W3C</td> 435 </tr> 436 <tr> 437 <td class="header left"></td> 438 <td class="header right">J. F. Reschke, Editor</td> 439 </tr> 440 <tr> 441 <td class="header left"></td> 442 <td class="header right">greenbytes</td> 443 </tr> 444 <tr> 445 <td class="header left"></td> 446 <td class="header right">January 12, 2008</td> 447 </tr> 359 <table class="header"> 360 <tbody> 361 <tr> 362 <td class="left">Network Working Group</td> 363 <td class="right">R. Fielding, Editor</td> 364 </tr> 365 <tr> 366 <td class="left">Internet-Draft</td> 367 <td class="right">Day Software</td> 368 </tr> 369 <tr> 370 <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 371 </td> 372 <td class="right">J. Gettys</td> 373 </tr> 374 <tr> 375 <td class="left">Intended status: Standards Track</td> 376 <td class="right">One Laptop per Child</td> 377 </tr> 378 <tr> 379 <td class="left">Expires: July 15, 2008</td> 380 <td class="right">J. Mogul</td> 381 </tr> 382 <tr> 383 <td class="left"></td> 384 <td class="right">HP</td> 385 </tr> 386 <tr> 387 <td class="left"></td> 388 <td class="right">H. Frystyk</td> 389 </tr> 390 <tr> 391 <td class="left"></td> 392 <td class="right">Microsoft</td> 393 </tr> 394 <tr> 395 <td class="left"></td> 396 <td class="right">L. Masinter</td> 397 </tr> 398 <tr> 399 <td class="left"></td> 400 <td class="right">Adobe Systems</td> 401 </tr> 402 <tr> 403 <td class="left"></td> 404 <td class="right">P. Leach</td> 405 </tr> 406 <tr> 407 <td class="left"></td> 408 <td class="right">Microsoft</td> 409 </tr> 410 <tr> 411 <td class="left"></td> 412 <td class="right">T. Berners-Lee</td> 413 </tr> 414 <tr> 415 <td class="left"></td> 416 <td class="right">W3C/MIT</td> 417 </tr> 418 <tr> 419 <td class="left"></td> 420 <td class="right">Y. Lafon, Editor</td> 421 </tr> 422 <tr> 423 <td class="left"></td> 424 <td class="right">W3C</td> 425 </tr> 426 <tr> 427 <td class="left"></td> 428 <td class="right">J. Reschke, Editor</td> 429 </tr> 430 <tr> 431 <td class="left"></td> 432 <td class="right">greenbytes</td> 433 </tr> 434 <tr> 435 <td class="left"></td> 436 <td class="right">January 12, 2008</td> 437 </tr> 438 </tbody> 448 439 </table> 449 440 <p class="title">HTTP/1.1, part 3: Message Payload and Content Negotiation<br><span class="filename">draft-ietf-httpbis-p3-payload-01</span></p> … … 460 451 in progress”. 461 452 </p> 462 <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>>.463 </p> 464 <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>>.465 </p> 466 <p>This Internet-Draft will expire in July2008.</p>453 <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>. 454 </p> 455 <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>. 456 </p> 457 <p>This Internet-Draft will expire on July 15, 2008.</p> 467 458 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 468 459 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information … … 480 471 <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1> 481 472 <ul class="toc"> 482 <li class="tocline0">1. <a href="#introduction">Introduction</a><ul class="toc">483 <li class="tocline1">1.1 <a href="#intro.requirements">Requirements</a></li>473 <li>1. <a href="#introduction">Introduction</a><ul> 474 <li>1.1 <a href="#intro.requirements">Requirements</a></li> 484 475 </ul> 485 476 </li> 486 <li class="tocline0">2. <a href="#protocol.parameters">Protocol Parameters</a><ul class="toc">487 <li class="tocline1">2.1 <a href="#character.sets">Character Sets</a><ul class="toc">488 <li class="tocline1">2.1.1 <a href="#missing.charset">Missing Charset</a></li>477 <li>2. <a href="#protocol.parameters">Protocol Parameters</a><ul> 478 <li>2.1 <a href="#character.sets">Character Sets</a><ul> 479 <li>2.1.1 <a href="#missing.charset">Missing Charset</a></li> 489 480 </ul> 490 481 </li> 491 <li class="tocline1">2.2 <a href="#content.codings">Content Codings</a></li>492 <li class="tocline1">2.3 <a href="#media.types">Media Types</a><ul class="toc">493 <li class="tocline1">2.3.1 <a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>494 <li class="tocline1">2.3.2 <a href="#multipart.types">Multipart Types</a></li>482 <li>2.2 <a href="#content.codings">Content Codings</a></li> 483 <li>2.3 <a href="#media.types">Media Types</a><ul> 484 <li>2.3.1 <a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li> 485 <li>2.3.2 <a href="#multipart.types">Multipart Types</a></li> 495 486 </ul> 496 487 </li> 497 <li class="tocline1">2.4 <a href="#quality.values">Quality Values</a></li>498 <li class="tocline1">2.5 <a href="#language.tags">Language Tags</a></li>488 <li>2.4 <a href="#quality.values">Quality Values</a></li> 489 <li>2.5 <a href="#language.tags">Language Tags</a></li> 499 490 </ul> 500 491 </li> 501 <li class="tocline0">3. <a href="#entity">Entity</a><ul class="toc">502 <li class="tocline1">3.1 <a href="#entity.header.fields">Entity Header Fields</a></li>503 <li class="tocline1">3.2 <a href="#entity.body">Entity Body</a><ul class="toc">504 <li class="tocline1">3.2.1 <a href="#type">Type</a></li>505 <li class="tocline1">3.2.2 <a href="#entity.length">Entity Length</a></li>492 <li>3. <a href="#entity">Entity</a><ul> 493 <li>3.1 <a href="#entity.header.fields">Entity Header Fields</a></li> 494 <li>3.2 <a href="#entity.body">Entity Body</a><ul> 495 <li>3.2.1 <a href="#type">Type</a></li> 496 <li>3.2.2 <a href="#entity.length">Entity Length</a></li> 506 497 </ul> 507 498 </li> 508 499 </ul> 509 500 </li> 510 <li class="tocline0">4. <a href="#content.negotiation">Content Negotiation</a><ul class="toc">511 <li class="tocline1">4.1 <a href="#server-driven.negotiation">Server-driven Negotiation</a></li>512 <li class="tocline1">4.2 <a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li>513 <li class="tocline1">4.3 <a href="#transparent.negotiation">Transparent Negotiation</a></li>501 <li>4. <a href="#content.negotiation">Content Negotiation</a><ul> 502 <li>4.1 <a href="#server-driven.negotiation">Server-driven Negotiation</a></li> 503 <li>4.2 <a href="#agent-driven.negotiation">Agent-driven Negotiation</a></li> 504 <li>4.3 <a href="#transparent.negotiation">Transparent Negotiation</a></li> 514 505 </ul> 515 506 </li> 516 <li class="tocline0">5. <a href="#header.fields">Header Field Definitions</a><ul class="toc">517 <li class="tocline1">5.1 <a href="#header.accept">Accept</a></li>518 <li class="tocline1">5.2 <a href="#header.accept-charset">Accept-Charset</a></li>519 <li class="tocline1">5.3 <a href="#header.accept-encoding">Accept-Encoding</a></li>520 <li class="tocline1">5.4 <a href="#header.accept-language">Accept-Language</a></li>521 <li class="tocline1">5.5 <a href="#header.content-encoding">Content-Encoding</a></li>522 <li class="tocline1">5.6 <a href="#header.content-language">Content-Language</a></li>523 <li class="tocline1">5.7 <a href="#header.content-location">Content-Location</a></li>524 <li class="tocline1">5.8 <a href="#header.content-md5">Content-MD5</a></li>525 <li class="tocline1">5.9 <a href="#header.content-type">Content-Type</a></li>507 <li>5. <a href="#header.fields">Header Field Definitions</a><ul> 508 <li>5.1 <a href="#header.accept">Accept</a></li> 509 <li>5.2 <a href="#header.accept-charset">Accept-Charset</a></li> 510 <li>5.3 <a href="#header.accept-encoding">Accept-Encoding</a></li> 511 <li>5.4 <a href="#header.accept-language">Accept-Language</a></li> 512 <li>5.5 <a href="#header.content-encoding">Content-Encoding</a></li> 513 <li>5.6 <a href="#header.content-language">Content-Language</a></li> 514 <li>5.7 <a href="#header.content-location">Content-Location</a></li> 515 <li>5.8 <a href="#header.content-md5">Content-MD5</a></li> 516 <li>5.9 <a href="#header.content-type">Content-Type</a></li> 526 517 </ul> 527 518 </li> 528 <li class="tocline0">6. <a href="#IANA.considerations">IANA Considerations</a></li>529 <li class="tocline0">7. <a href="#security.considerations">Security Considerations</a><ul class="toc">530 <li class="tocline1">7.1 <a href="#privacy.issues.connected.to.accept.headers">Privacy Issues Connected to Accept Headers</a></li>531 <li class="tocline1">7.2 <a href="#content-disposition.issues">Content-Disposition Issues</a></li>519 <li>6. <a href="#IANA.considerations">IANA Considerations</a></li> 520 <li>7. <a href="#security.considerations">Security Considerations</a><ul> 521 <li>7.1 <a href="#privacy.issues.connected.to.accept.headers">Privacy Issues Connected to Accept Headers</a></li> 522 <li>7.2 <a href="#content-disposition.issues">Content-Disposition Issues</a></li> 532 523 </ul> 533 524 </li> 534 <li class="tocline0">8. <a href="#ack">Acknowledgments</a></li>535 <li class="tocline0">9. <a href="#rfc.references">References</a><ul class="toc">536 <li class="tocline1">9.1 <a href="#rfc.references.1">Normative References</a></li>537 <li class="tocline1">9.2 <a href="#rfc.references.2">Informative References</a></li>525 <li>8. <a href="#ack">Acknowledgments</a></li> 526 <li>9. <a href="#rfc.references">References</a><ul> 527 <li>9.1 <a href="#rfc.references.1">Normative References</a></li> 528 <li>9.2 <a href="#rfc.references.2">Informative References</a></li> 538 529 </ul> 539 530 </li> 540 <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>541 <li class="tocline0">A. <a href="#differences.between.http.entities.and.rfc.2045.entities">Differences Between HTTP Entities and RFC 2045 Entities</a><ul class="toc">542 <li class="tocline1">A.1 <a href="#mime-version">MIME-Version</a></li>543 <li class="tocline1">A.2 <a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li>544 <li class="tocline1">A.3 <a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li>545 <li class="tocline1">A.4 <a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li>546 <li class="tocline1">A.5 <a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li>547 <li class="tocline1">A.6 <a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li>531 <li><a href="#rfc.authors">Authors' Addresses</a></li> 532 <li>A. <a href="#differences.between.http.entities.and.rfc.2045.entities">Differences Between HTTP Entities and RFC 2045 Entities</a><ul> 533 <li>A.1 <a href="#mime-version">MIME-Version</a></li> 534 <li>A.2 <a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></li> 535 <li>A.3 <a href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></li> 536 <li>A.4 <a href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></li> 537 <li>A.5 <a href="#introduction.of.transfer-encoding">Introduction of Transfer-Encoding</a></li> 538 <li>A.6 <a href="#mhtml.line.length">MHTML and Line Length Limitations</a></li> 548 539 </ul> 549 540 </li> 550 <li class="tocline0">B. <a href="#additional.features">Additional Features</a><ul class="toc">551 <li class="tocline1">B.1 <a href="#content-disposition">Content-Disposition</a></li>541 <li>B. <a href="#additional.features">Additional Features</a><ul> 542 <li>B.1 <a href="#content-disposition">Content-Disposition</a></li> 552 543 </ul> 553 544 </li> 554 <li class="tocline0">C. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc">555 <li class="tocline1">C.1 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>556 <li class="tocline1">C.2 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>545 <li>C. <a href="#compatibility">Compatibility with Previous Versions</a><ul> 546 <li>C.1 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li> 547 <li>C.2 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 557 548 </ul> 558 549 </li> 559 <li class="tocline0">D. <a href="#rfc.section.D">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">560 <li class="tocline1">D.1 <a href="#rfc.section.D.1">Since RFC2616</a></li>561 <li class="tocline1">D.2 <a href="#rfc.section.D.2">Since draft-ietf-httpbis-p3-payload-00</a></li>550 <li>D. <a href="#rfc.section.D">Change Log (to be removed by RFC Editor before publication)</a><ul> 551 <li>D.1 <a href="#rfc.section.D.1">Since RFC2616</a></li> 552 <li>D.2 <a href="#rfc.section.D.2">Since draft-ietf-httpbis-p3-payload-00</a></li> 562 553 </ul> 563 554 </li> 564 <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>565 <li class="tocline0"><a href="#rfc.index">Index</a></li>555 <li><a href="#rfc.index">Index</a></li> 556 <li><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li> 566 557 </ul> 567 558 <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> <a id="introduction" href="#introduction">Introduction</a></h1> … … 593 584 to determine the exact mapping is not permitted. 594 585 </p> 595 < dl class="empty">596 < dd> <b>Note:</b> This use of the term "character set" is more commonly referred to as a "character encoding." However, since HTTP and MIME586 <ul class="empty"> 587 <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 597 588 share the same registry, it is important that the terminology also be shared. 598 </ dd>599 </ dl>589 </li> 590 </ul> 600 591 <p id="rfc.section.2.1.p.4">HTTP character sets are identified by case-insensitive tokens. The complete set of tokens is defined by the IANA Character 601 592 Set registry (<<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>>). … … 633 624 <p id="rfc.section.2.2.p.5">gzip<span id="rfc.iref.g.3"></span> 634 625 </p> 635 < dl class="empty">636 < 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.637 </ dd>638 </ dl>626 <ul class="empty"> 627 <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. 628 </li> 629 </ul> 639 630 <p id="rfc.section.2.2.p.6">compress<span id="rfc.iref.c.1"></span> 640 631 </p> 641 < dl class="empty">642 < dd>The encoding format produced by the common UNIX file compression program "compress". This format is an adaptive Lempel-Ziv-Welch632 <ul class="empty"> 633 <li>The encoding format produced by the common UNIX file compression program "compress". This format is an adaptive Lempel-Ziv-Welch 643 634 coding (LZW). 644 </ dd>645 < dd>Use of program names for the identification of encoding formats is not desirable and is discouraged for future encodings.635 </li> 636 <li>Use of program names for the identification of encoding formats is not desirable and is discouraged for future encodings. 646 637 Their use here is representative of historical practice, not good design. For compatibility with previous implementations 647 638 of HTTP, applications <em class="bcp14">SHOULD</em> consider "x-gzip" and "x-compress" to be equivalent to "gzip" and "compress" respectively. 648 </ dd>649 </ dl>639 </li> 640 </ul> 650 641 <p id="rfc.section.2.2.p.7">deflate<span id="rfc.iref.d.1"></span> 651 642 </p> 652 < dl class="empty">653 < 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>.654 </ dd>655 </ dl>643 <ul class="empty"> 644 <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>. 645 </li> 646 </ul> 656 647 <p id="rfc.section.2.2.p.8">identity<span id="rfc.iref.i.1"></span> 657 648 </p> 658 < dl class="empty">659 < dd>The default (identity) encoding; the use of no transformation whatsoever. This content-coding is used only in the Accept-Encoding649 <ul class="empty"> 650 <li>The default (identity) encoding; the use of no transformation whatsoever. This content-coding is used only in the Accept-Encoding 660 651 header, and <em class="bcp14">SHOULD NOT</em> be used in the Content-Encoding header. 661 </ dd>662 </ dl>652 </li> 653 </ul> 663 654 <p id="rfc.section.2.2.p.9">New content-coding value tokens <em class="bcp14">SHOULD</em> be registered; to allow interoperability between clients and servers, specifications of the content coding algorithms needed 664 655 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 … … 711 702 </p> 712 703 <p id="rfc.section.2.3.2.p.2">In general, HTTP treats a multipart message-body no differently than any other media type: strictly as payload. The one exception 713 is the "multipart/byteranges" type (<a href="p5-range.html#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a> of <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) when it appears in a 206 (Partial Content) response. 704 is the "multipart/byteranges" type (<a href="p5-range.html#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix A</a> of <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) when it appears in a 206 (Partial Content) response. 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 705 each body-part of a multipart message-body do not have any significance to HTTP beyond that defined by their MIME semantics. 714 706 </p> 715 707 <p id="rfc.section.2.3.2.p.3">In general, an HTTP user agent <em class="bcp14">SHOULD</em> follow the same or similar behavior as a MIME user agent would upon receipt of a multipart type. If an application receives 716 708 an unrecognized multipart subtype, the application <em class="bcp14">MUST</em> treat it as being equivalent to "multipart/mixed". 717 709 </p> 718 < dl class="empty">719 < dd> <b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request710 <ul class="empty"> 711 <li> <b>Note:</b> The "multipart/form-data" type has been specifically defined for carrying form data suitable for processing via the POST request 720 712 method, as described in <a href="#RFC2388" id="rfc.xref.RFC2388.1"><cite title="Returning Values from Forms: multipart/form-data">[RFC2388]</cite></a>. 721 </ dd>722 </ dl>713 </li> 714 </ul> 723 715 <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a> <a id="quality.values" href="#quality.values">Quality Values</a></h2> 724 716 <p id="rfc.section.2.4.p.1">HTTP content negotiation (<a href="#content.negotiation" title="Content Negotiation">Section 4</a>) uses short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight … … 803 795 best representation for a given response when there are multiple representations available. 804 796 </p> 805 < dl class="empty">806 < dd> <b>Note:</b> This is not called "format negotiation" because the alternate representations may be of the same media type, but use different797 <ul class="empty"> 798 <li> <b>Note:</b> This is not called "format negotiation" because the alternate representations may be of the same media type, but use different 807 799 capabilities of that type, be in different languages, etc. 808 </ dd>809 </ dl>800 </li> 801 </ul> 810 802 <p id="rfc.section.4.p.2">Any response containing an entity-body <em class="bcp14">MAY</em> be subject to negotiation, including error responses. 811 803 </p> … … 904 896 agent to indicate the relative degree of preference for that media-range, using the qvalue scale from 0 to 1 (<a href="#quality.values" title="Quality Values">Section 2.4</a>). The default value is q=1. 905 897 </p> 906 < dl class="empty">907 < dd> <b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice.898 <ul class="empty"> 899 <li> <b>Note:</b> Use of the "q" parameter name to separate media type parameters from Accept extension parameters is due to historical practice. 908 900 Although this prevents any media type parameter named "q" from being used with a media range, such an event is believed to 909 901 be unlikely given the lack of any "q" parameters in the IANA media type registry and the rare usage of any media type parameters 910 902 in Accept. Future media types are discouraged from registering any parameter named "q". 911 </ dd>912 </ dl>903 </li> 904 </ul> 913 905 <p id="rfc.section.5.1.p.5">The example</p> 914 906 <div id="rfc.figure.u.12"></div><pre class="text"> Accept: audio/*; q=0.2, audio/basic … … 1006 998 client. 1007 999 </p> 1008 < dl class="empty">1009 < dd> <b>Note:</b> If the request does not include an Accept-Encoding field, and if the "identity" content-coding is unavailable, then content-codings1000 <ul class="empty"> 1001 <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 1010 1002 commonly understood by HTTP/1.0 clients (i.e., "gzip" and "compress") are preferred; some older clients improperly display 1011 1003 messages sent with other content-codings. The server might also make this decision based on information about the particular 1012 1004 user-agent or client. 1013 </ dd>1014 < dd> <b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues will1005 </li> 1006 <li> <b>Note:</b> Most HTTP/1.0 applications do not recognize or obey qvalues associated with content-codings. This means that qvalues will 1015 1007 not work and are not permitted with x-gzip or x-compress. 1016 </ dd>1017 </ dl>1008 </li> 1009 </ul> 1018 1010 <div id="rfc.iref.a.4"></div> 1019 1011 <div id="rfc.iref.h.4"></div> … … 1034 1026 range present in the Accept-Language field. 1035 1027 </p> 1036 < dl class="empty">1037 < 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 always1028 <ul class="empty"> 1029 <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 1038 1030 true that if a user understands a language with a certain tag, then this user will also understand all languages with tags 1039 1031 for which this tag is a prefix. The prefix rule simply allows the use of prefix tags if this is the case. 1040 </ dd>1041 </ dl>1032 </li> 1033 </ul> 1042 1034 <p id="rfc.section.5.4.p.6">The language quality factor assigned to a language-tag by the Accept-Language field is the quality value of the longest language-range 1043 1035 in the field that matches the language-tag. If no language-range in the field matches the tag, the language quality factor … … 1051 1043 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. 1052 1044 </p> 1053 < dl class="empty">1054 < dd> <b>Note:</b> When making the choice of linguistic preference available to the user, we remind implementors of the fact that users are not1045 <ul class="empty"> 1046 <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 1055 1047 familiar with the details of language matching as described above, and should provide appropriate guidance. As an example, 1056 1048 users might assume that on selecting "en-gb", they will be served any kind of English document if British English is not available. 1057 1049 A user agent might suggest in such a case to add "en" to get the best matching behavior. 1058 </ dd>1059 </ dl>1050 </li> 1051 </ul> 1060 1052 <div id="rfc.iref.c.2"></div> 1061 1053 <div id="rfc.iref.h.5"></div> … … 1154 1146 <p id="rfc.section.5.8.p.8">Conversion of all line breaks to CRLF <em class="bcp14">MUST NOT</em> be done before computing or checking the digest: the line break convention used in the text actually transmitted <em class="bcp14">MUST</em> be left unaltered when computing the digest. 1155 1147 </p> 1156 < dl class="empty">1157 < 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 several1148 <ul class="empty"> 1149 <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 1158 1150 ways in which the application of Content-MD5 to HTTP entity-bodies differs from its application to MIME entity-bodies. One 1159 1151 is that HTTP, unlike MIME, does not use Content-Transfer-Encoding, and does use Transfer-Encoding and Content-Encoding. Another … … 1161 1153 used to compute the digest is the transmission byte order defined for the type. Lastly, HTTP allows transmission of text types 1162 1154 with any of several line break conventions and not just the canonical form using CRLF. 1163 </ dd>1164 </ dl>1155 </li> 1156 </ul> 1165 1157 <div id="rfc.iref.c.6"></div> 1166 1158 <div id="rfc.iref.h.9"></div> … … 1210 1202 <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References 1211 1203 </h2> 1212 <table summary="Normative References">1204 <table> 1213 1205 <tr> 1214 1206 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> 1215 <td class="top">International Organization for Standardization, “ 1216 Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1 1217 ”, ISO/IEC 8859-1:1998, 1998. 1218 </td> 1207 <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> 1219 1208 </tr> 1220 1209 <tr> 1221 1210 <td class="reference"><b id="Part1">[Part1]</b></td> 1222 <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-01">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-01 (work in progress), January 2008.1211 <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-01">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft draft-ietf-httpbis-p1-messaging-01 (work in progress), January 2008. 1223 1212 </td> 1224 1213 </tr> 1225 1214 <tr> 1226 1215 <td class="reference"><b id="Part2">[Part2]</b></td> 1227 <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-01">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-01 (work in progress), January 2008.1216 <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-01">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-01 (work in progress), January 2008. 1228 1217 </td> 1229 1218 </tr> 1230 1219 <tr> 1231 1220 <td class="reference"><b id="Part4">[Part4]</b></td> 1232 <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-01">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-01 (work in progress), January 2008.1221 <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-01">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft draft-ietf-httpbis-p4-conditional-01 (work in progress), January 2008. 1233 1222 </td> 1234 1223 </tr> 1235 1224 <tr> 1236 1225 <td class="reference"><b id="Part5">[Part5]</b></td> 1237 <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-01">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-01 (work in progress), January 2008.1226 <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-01">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-01 (work in progress), January 2008. 1238 1227 </td> 1239 1228 </tr> 1240 1229 <tr> 1241 1230 <td class="reference"><b id="Part6">[Part6]</b></td> 1242 <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-01">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-01 (work in progress), January 2008.1231 <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-01">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-01 (work in progress), January 2008. 1243 1232 </td> 1244 1233 </tr> 1245 1234 <tr> 1246 1235 <td class="reference"><b id="RFC1766">[RFC1766]</b></td> 1247 <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.1236 <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. 1248 1237 </td> 1249 1238 </tr> 1250 1239 <tr> 1251 1240 <td class="reference"><b id="RFC1864">[RFC1864]</b></td> 1252 <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.1241 <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. 1253 1242 </td> 1254 1243 </tr> 1255 1244 <tr> 1256 1245 <td class="reference"><b id="RFC1950">[RFC1950]</b></td> 1257 <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 reference1246 <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 1258 1247 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. 1259 1248 </td> … … 1261 1250 <tr> 1262 1251 <td class="reference"><b id="RFC1951">[RFC1951]</b></td> 1263 <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 reference1252 <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 1264 1253 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. 1265 1254 </td> … … 1267 1256 <tr> 1268 1257 <td class="reference"><b id="RFC1952">[RFC1952]</b></td> 1269 <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 reference1258 <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 1270 1259 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. 1271 1260 </td> … … 1273 1262 <tr> 1274 1263 <td class="reference"><b id="RFC2045">[RFC2045]</b></td> 1275 <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.1264 <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. 1276 1265 </td> 1277 1266 </tr> 1278 1267 <tr> 1279 1268 <td class="reference"><b id="RFC2046">[RFC2046]</b></td> 1280 <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.1269 <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. 1281 1270 </td> 1282 1271 </tr> 1283 1272 <tr> 1284 1273 <td class="reference"><b id="RFC2119">[RFC2119]</b></td> 1285 <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.1274 <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. 1286 1275 </td> 1287 1276 </tr> 1288 1277 <tr> 1289 1278 <td class="reference"><b id="RFC4288">[RFC4288]</b></td> 1290 <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.1279 <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. 1291 1280 </td> 1292 1281 </tr> … … 1294 1283 <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References 1295 1284 </h2> 1296 <table summary="Informative References">1285 <table> 1297 1286 <tr> 1298 1287 <td class="reference"><b id="RFC1806">[RFC1806]</b></td> 1299 <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.1288 <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. 1300 1289 </td> 1301 1290 </tr> 1302 1291 <tr> 1303 1292 <td class="reference"><b id="RFC1945">[RFC1945]</b></td> 1304 <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.1293 <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. 1305 1294 </td> 1306 1295 </tr> 1307 1296 <tr> 1308 1297 <td class="reference"><b id="RFC2049">[RFC2049]</b></td> 1309 <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.1298 <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. 1310 1299 </td> 1311 1300 </tr> 1312 1301 <tr> 1313 1302 <td class="reference"><b id="RFC2068">[RFC2068]</b></td> 1314 <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.1303 <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. 1315 1304 </td> 1316 1305 </tr> 1317 1306 <tr> 1318 1307 <td class="reference"><b id="RFC2076">[RFC2076]</b></td> 1319 <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.1308 <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. 1320 1309 </td> 1321 1310 </tr> 1322 1311 <tr> 1323 1312 <td class="reference"><b id="RFC2183">[RFC2183]</b></td> 1324 <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.1313 <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. 1325 1314 </td> 1326 1315 </tr> 1327 1316 <tr> 1328 1317 <td class="reference"><b id="RFC2277">[RFC2277]</b></td> 1329 <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.1318 <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. 1330 1319 </td> 1331 1320 </tr> 1332 1321 <tr> 1333 1322 <td class="reference"><b id="RFC2388">[RFC2388]</b></td> 1334 <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.1323 <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. 1335 1324 </td> 1336 1325 </tr> 1337 1326 <tr> 1338 1327 <td class="reference"><b id="RFC2557">[RFC2557]</b></td> 1339 <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.1328 <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. 1340 1329 </td> 1341 1330 </tr> 1342 1331 <tr> 1343 1332 <td class="reference"><b id="RFC2616">[RFC2616]</b></td> 1344 <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.1333 <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. 1345 1334 </td> 1346 1335 </tr> … … 1352 1341 <tr> 1353 1342 <td class="reference"><b id="RFC3629">[RFC3629]</b></td> 1354 <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.1343 <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. 1355 1344 </td> 1356 1345 </tr> 1357 1346 </table> 1358 <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1> 1359 <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span> 1360 (editor) 1361 <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> 1362 <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> 1363 <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> 1364 <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> 1365 <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> 1366 <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> 1367 <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> 1368 <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span> 1369 (editor) 1370 <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> 1371 <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span> 1372 (editor) 1373 <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> 1374 <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> 1347 <div class="avoidbreak"> 1348 <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1> 1349 <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span> 1350 (editor) 1351 <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> 1352 <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> 1353 <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> 1354 <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> 1355 <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> 1356 <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> 1357 <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> 1358 <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span> 1359 (editor) 1360 <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> 1361 <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span> 1362 (editor) 1363 <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> 1364 </div> 1365 <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> 1375 1366 <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 1376 1367 discusses mail, and HTTP has a few features that are different from those described in RFC 2045. These differences were carefully … … 1511 1502 </li> 1512 1503 </ul> 1504 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1505 <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> 1506 </p> 1507 <div class="print2col"> 1508 <ul class="ind"> 1509 <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul> 1510 <li>Accept header <a href="#rfc.xref.header.accept.1">2.3</a>, <a href="#rfc.xref.header.accept.2">4.1</a>, <a href="#rfc.iref.a.1"><b>5.1</b></a></li> 1511 <li>Accept-Charset header <a href="#rfc.xref.header.accept-charset.1">4.1</a>, <a href="#rfc.iref.a.2"><b>5.2</b></a>, <a href="#rfc.xref.header.accept-charset.2">C.1</a></li> 1512 <li>Accept-Encoding header <a href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a href="#rfc.xref.header.accept-encoding.2">4.1</a>, <a href="#rfc.iref.a.3"><b>5.3</b></a></li> 1513 <li>Accept-Language header <a href="#rfc.xref.header.accept-language.1">4.1</a>, <a href="#rfc.iref.a.4"><b>5.4</b></a></li> 1514 <li>Alternates header <a href="#rfc.iref.a.5"><b>C.1</b></a></li> 1515 </ul> 1516 </li> 1517 <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul> 1518 <li>compress <a href="#rfc.iref.c.1">2.2</a></li> 1519 <li>Content-Base header <a href="#rfc.iref.c.9"><b>C.1</b></a></li> 1520 <li>Content-Disposition header <a href="#rfc.xref.content-disposition.1">7.2</a>, <a href="#rfc.iref.c.7"><b>B.1</b></a></li> 1521 <li>Content-Encoding header <a href="#rfc.xref.header.content-encoding.1">2.2</a>, <a href="#rfc.xref.header.content-encoding.2">3.1</a>, <a href="#rfc.iref.c.2"><b>5.5</b></a>, <a href="#rfc.xref.header.content-encoding.3">5.5</a></li> 1522 <li>Content-Language header <a href="#rfc.xref.header.content-language.1">3.1</a>, <a href="#rfc.iref.c.3"><b>5.6</b></a></li> 1523 <li>Content-Location header <a href="#rfc.xref.header.content-location.1">3.1</a>, <a href="#rfc.iref.c.4"><b>5.7</b></a></li> 1524 <li>Content-MD5 header <a href="#rfc.xref.header.content-md5.1">3.1</a>, <a href="#rfc.iref.c.5"><b>5.8</b></a></li> 1525 <li>Content-Type header <a href="#rfc.xref.header.content-type.1">2.3</a>, <a href="#rfc.xref.header.content-type.2">3.1</a>, <a href="#rfc.iref.c.6"><b>5.9</b></a></li> 1526 <li>Content-Version header <a href="#rfc.iref.c.8"><b>C.1</b></a></li> 1527 </ul> 1528 </li> 1529 <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul> 1530 <li>deflate <a href="#rfc.iref.d.1">2.2</a></li> 1531 <li>Derived-From header <a href="#rfc.iref.d.2"><b>C.1</b></a></li> 1532 </ul> 1533 </li> 1534 <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul> 1535 <li><tt>Grammar</tt> 1536 <ul> 1537 <li><tt>Accept</tt> <a href="#rfc.iref.g.17"><b>5.1</b></a></li> 1538 <li><tt>Accept-Charset</tt> <a href="#rfc.iref.g.21"><b>5.2</b></a></li> 1539 <li><tt>Accept-Encoding</tt> <a href="#rfc.iref.g.22"><b>5.3</b></a></li> 1540 <li><tt>accept-extension</tt> <a href="#rfc.iref.g.20"><b>5.1</b></a></li> 1541 <li><tt>Accept-Language</tt> <a href="#rfc.iref.g.24"><b>5.4</b></a></li> 1542 <li><tt>accept-params</tt> <a href="#rfc.iref.g.19"><b>5.1</b></a></li> 1543 <li><tt>attribute</tt> <a href="#rfc.iref.g.8"><b>2.3</b></a></li> 1544 <li><tt>charset</tt> <a href="#rfc.iref.g.1"><b>2.1</b></a></li> 1545 <li><tt>codings</tt> <a href="#rfc.iref.g.23"><b>5.3</b></a></li> 1546 <li><tt>content-coding</tt> <a href="#rfc.iref.g.2"><b>2.2</b></a></li> 1547 <li><tt>content-disposition</tt> <a href="#rfc.iref.g.33"><b>B.1</b></a></li> 1548 <li><tt>Content-Encoding</tt> <a href="#rfc.iref.g.26"><b>5.5</b></a></li> 1549 <li><tt>Content-Language</tt> <a href="#rfc.iref.g.27"><b>5.6</b></a></li> 1550 <li><tt>Content-Location</tt> <a href="#rfc.iref.g.28"><b>5.7</b></a></li> 1551 <li><tt>Content-MD5</tt> <a href="#rfc.iref.g.29"><b>5.8</b></a></li> 1552 <li><tt>Content-Type</tt> <a href="#rfc.iref.g.31"><b>5.9</b></a></li> 1553 <li><tt>disp-extension-parm</tt> <a href="#rfc.iref.g.38"><b>B.1</b></a></li> 1554 <li><tt>disp-extension-token</tt> <a href="#rfc.iref.g.37"><b>B.1</b></a></li> 1555 <li><tt>disposition-parm</tt> <a href="#rfc.iref.g.35"><b>B.1</b></a></li> 1556 <li><tt>disposition-type</tt> <a href="#rfc.iref.g.34"><b>B.1</b></a></li> 1557 <li><tt>entity-body</tt> <a href="#rfc.iref.g.16"><b>3.2</b></a></li> 1558 <li><tt>entity-header</tt> <a href="#rfc.iref.g.14"><b>3.1</b></a></li> 1559 <li><tt>extension-header</tt> <a href="#rfc.iref.g.15"><b>3.1</b></a></li> 1560 <li><tt>filename-parm</tt> <a href="#rfc.iref.g.36"><b>B.1</b></a></li> 1561 <li><tt>language-range</tt> <a href="#rfc.iref.g.25"><b>5.4</b></a></li> 1562 <li><tt>language-tag</tt> <a href="#rfc.iref.g.11"><b>2.5</b></a></li> 1563 <li><tt>md5-digest</tt> <a href="#rfc.iref.g.30"><b>5.8</b></a></li> 1564 <li><tt>media-range</tt> <a href="#rfc.iref.g.18"><b>5.1</b></a></li> 1565 <li><tt>media-type</tt> <a href="#rfc.iref.g.4"><b>2.3</b></a></li> 1566 <li><tt>MIME-Version</tt> <a href="#rfc.iref.g.32"><b>A.1</b></a></li> 1567 <li><tt>parameter</tt> <a href="#rfc.iref.g.7"><b>2.3</b></a></li> 1568 <li><tt>primary-tag</tt> <a href="#rfc.iref.g.12"><b>2.5</b></a></li> 1569 <li><tt>qvalue</tt> <a href="#rfc.iref.g.10"><b>2.4</b></a></li> 1570 <li><tt>subtag</tt> <a href="#rfc.iref.g.13"><b>2.5</b></a></li> 1571 <li><tt>subtype</tt> <a href="#rfc.iref.g.6"><b>2.3</b></a></li> 1572 <li><tt>type</tt> <a href="#rfc.iref.g.5"><b>2.3</b></a></li> 1573 <li><tt>value</tt> <a href="#rfc.iref.g.9"><b>2.3</b></a></li> 1574 </ul> 1575 </li> 1576 <li>gzip <a href="#rfc.iref.g.3">2.2</a></li> 1577 </ul> 1578 </li> 1579 <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul> 1580 <li>Headers 1581 <ul> 1582 <li>Accept <a href="#rfc.xref.header.accept.1">2.3</a>, <a href="#rfc.xref.header.accept.2">4.1</a>, <a href="#rfc.iref.h.1"><b>5.1</b></a></li> 1583 <li>Accept-Charset <a href="#rfc.xref.header.accept-charset.1">4.1</a>, <a href="#rfc.iref.h.2"><b>5.2</b></a>, <a href="#rfc.xref.header.accept-charset.2">C.1</a></li> 1584 <li>Accept-Encoding <a href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a href="#rfc.xref.header.accept-encoding.2">4.1</a>, <a href="#rfc.iref.h.3"><b>5.3</b></a></li> 1585 <li>Accept-Language <a href="#rfc.xref.header.accept-language.1">4.1</a>, <a href="#rfc.iref.h.4"><b>5.4</b></a></li> 1586 <li>Alternate <a href="#rfc.iref.h.11"><b>C.1</b></a></li> 1587 <li>Content-Base <a href="#rfc.iref.h.17"><b>C.1</b></a></li> 1588 <li>Content-Disposition <a href="#rfc.xref.content-disposition.1">7.2</a>, <a href="#rfc.iref.h.10"><b>B.1</b></a></li> 1589 <li>Content-Encoding <a href="#rfc.xref.header.content-encoding.1">2.2</a>, <a href="#rfc.xref.header.content-encoding.2">3.1</a>, <a href="#rfc.iref.h.5"><b>5.5</b></a>, <a href="#rfc.xref.header.content-encoding.3">5.5</a></li> 1590 <li>Content-Language <a href="#rfc.xref.header.content-language.1">3.1</a>, <a href="#rfc.iref.h.6"><b>5.6</b></a></li> 1591 <li>Content-Location <a href="#rfc.xref.header.content-location.1">3.1</a>, <a href="#rfc.iref.h.7"><b>5.7</b></a></li> 1592 <li>Content-MD5 <a href="#rfc.xref.header.content-md5.1">3.1</a>, <a href="#rfc.iref.h.8"><b>5.8</b></a></li> 1593 <li>Content-Type <a href="#rfc.xref.header.content-type.1">2.3</a>, <a href="#rfc.xref.header.content-type.2">3.1</a>, <a href="#rfc.iref.h.9"><b>5.9</b></a></li> 1594 <li>Content-Version <a href="#rfc.iref.h.12"><b>C.1</b></a></li> 1595 <li>Derived-From <a href="#rfc.iref.h.13"><b>C.1</b></a></li> 1596 <li>Link <a href="#rfc.iref.h.14"><b>C.1</b></a></li> 1597 <li>Public <a href="#rfc.iref.h.16"><b>C.1</b></a></li> 1598 <li>URI <a href="#rfc.iref.h.15"><b>C.1</b></a></li> 1599 </ul> 1600 </li> 1601 </ul> 1602 </li> 1603 <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul> 1604 <li>identity <a href="#rfc.iref.i.1">2.2</a></li> 1605 <li><em>ISO-8859-1</em> <a href="#rfc.xref.ISO-8859-1.1">2.1.1</a>, <a href="#ISO-8859-1"><b>9.1</b></a></li> 1606 </ul> 1607 </li> 1608 <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul> 1609 <li>Link header <a href="#rfc.iref.l.1"><b>C.1</b></a></li> 1610 </ul> 1611 </li> 1612 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 1613 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">3.1</a>, <a href="#rfc.xref.Part1.2">3.2</a>, <a href="#rfc.xref.Part1.3">3.2.2</a>, <a href="#Part1"><b>9.1</b></a>, <a href="#rfc.xref.Part1.4">A.5</a>, <a href="#rfc.xref.Part1.5">C.1</a><ul> 1614 <li><em>Section 4.3</em> <a href="#rfc.xref.Part1.2">3.2</a></li> 1615 <li><em>Section 4.4</em> <a href="#rfc.xref.Part1.3">3.2.2</a></li> 1616 <li><em>Section 8.2</em> <a href="#rfc.xref.Part1.1">3.1</a></li> 1617 <li><em>Section 8.7</em> <a href="#rfc.xref.Part1.4">A.5</a></li> 1618 </ul> 1619 </li> 1620 <li><em>Part2</em> <a href="#rfc.xref.Part2.1">3.1</a>, <a href="#rfc.xref.Part2.2">4.1</a>, <a href="#Part2"><b>9.1</b></a><ul> 1621 <li><em>Section 10.1</em> <a href="#rfc.xref.Part2.1">3.1</a></li> 1622 <li><em>Section 10.9</em> <a href="#rfc.xref.Part2.2">4.1</a></li> 1623 </ul> 1624 </li> 1625 <li><em>Part4</em> <a href="#rfc.xref.Part4.1">3.1</a>, <a href="#Part4"><b>9.1</b></a><ul> 1626 <li><em>Section 6.6</em> <a href="#rfc.xref.Part4.1">3.1</a></li> 1627 </ul> 1628 </li> 1629 <li><em>Part5</em> <a href="#rfc.xref.Part5.1">2.3.2</a>, <a href="#rfc.xref.Part5.2">3.1</a>, <a href="#Part5"><b>9.1</b></a>, <a href="#rfc.xref.Part5.3">C.1</a><ul> 1630 <li><em>Section 5.2</em> <a href="#rfc.xref.Part5.2">3.1</a></li> 1631 <li><em>Appendix A</em> <a href="#rfc.xref.Part5.1">2.3.2</a></li> 1632 </ul> 1633 </li> 1634 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">3.1</a>, <a href="#rfc.xref.Part6.2">4.1</a>, <a href="#rfc.xref.Part6.3">5.7</a>, <a href="#Part6"><b>9.1</b></a>, <a href="#rfc.xref.Part6.4">C.1</a><ul> 1635 <li><em>Section 7</em> <a href="#rfc.xref.Part6.3">5.7</a></li> 1636 <li><em>Section 15.3</em> <a href="#rfc.xref.Part6.1">3.1</a></li> 1637 <li><em>Section 15.5</em> <a href="#rfc.xref.Part6.2">4.1</a></li> 1638 </ul> 1639 </li> 1640 <li>Public header <a href="#rfc.iref.p.1"><b>C.1</b></a></li> 1641 </ul> 1642 </li> 1643 <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul> 1644 <li><em>RFC1766</em> <a href="#rfc.xref.RFC1766.1">2.5</a>, <a href="#RFC1766"><b>9.1</b></a></li> 1645 <li><em>RFC1806</em> <a href="#rfc.xref.RFC1806.1">7.2</a>, <a href="#rfc.xref.RFC1806.2">7.2</a>, <a href="#RFC1806"><b>9.2</b></a>, <a href="#rfc.xref.RFC1806.3">B.1</a></li> 1646 <li><em>RFC1864</em> <a href="#rfc.xref.RFC1864.1">5.8</a>, <a href="#rfc.xref.RFC1864.2">5.8</a>, <a href="#RFC1864"><b>9.1</b></a></li> 1647 <li><em>RFC1945</em> <a href="#RFC1945"><b>9.2</b></a>, <a href="#rfc.xref.RFC1945.1">B</a></li> 1648 <li><em>RFC1950</em> <a href="#rfc.xref.RFC1950.1">2.2</a>, <a href="#RFC1950"><b>9.1</b></a></li> 1649 <li><em>RFC1951</em> <a href="#rfc.xref.RFC1951.1">2.2</a>, <a href="#RFC1951"><b>9.1</b></a></li> 1650 <li><em>RFC1952</em> <a href="#rfc.xref.RFC1952.1">2.2</a>, <a href="#RFC1952"><b>9.1</b></a></li> 1651 <li><em>RFC2045</em> <a href="#RFC2045"><b>9.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> 1652 <li><em>RFC2046</em> <a href="#rfc.xref.RFC2046.1">2.3</a>, <a href="#rfc.xref.RFC2046.2">2.3.2</a>, <a href="#RFC2046"><b>9.1</b></a>, <a href="#rfc.xref.RFC2046.3">A.2</a><ul> 1653 <li><em>Section 5.1.1</em> <a href="#rfc.xref.RFC2046.2">2.3.2</a></li> 1654 </ul> 1655 </li> 1656 <li><em>RFC2049</em> <a href="#RFC2049"><b>9.2</b></a>, <a href="#rfc.xref.RFC2049.1">A.2</a><ul> 1657 <li><em>Section 4</em> <a href="#rfc.xref.RFC2049.1">A.2</a></li> 1658 </ul> 1659 </li> 1660 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">9.1</a>, <a href="#rfc.xref.RFC2068.2">9.1</a>, <a href="#rfc.xref.RFC2068.3">9.1</a>, <a href="#RFC2068"><b>9.2</b></a>, <a href="#rfc.xref.RFC2068.4">B</a>, <a href="#rfc.xref.RFC2068.5">C.1</a></li> 1661 <li><em>RFC2076</em> <a href="#RFC2076"><b>9.2</b></a>, <a href="#rfc.xref.RFC2076.1">B</a></li> 1662 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>9.1</b></a></li> 1663 <li><em>RFC2183</em> <a href="#rfc.xref.RFC2183.1">7.2</a>, <a href="#RFC2183"><b>9.2</b></a></li> 1664 <li><em>RFC2277</em> <a href="#rfc.xref.RFC2277.1">2.1</a>, <a href="#RFC2277"><b>9.2</b></a></li> 1665 <li><em>RFC2388</em> <a href="#rfc.xref.RFC2388.1">2.3.2</a>, <a href="#RFC2388"><b>9.2</b></a></li> 1666 <li><em>RFC2557</em> <a href="#RFC2557"><b>9.2</b></a>, <a href="#rfc.xref.RFC2557.1">A.6</a>, <a href="#rfc.xref.RFC2557.2">C.1</a></li> 1667 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">1</a>, <a href="#RFC2616"><b>9.2</b></a>, <a href="#rfc.xref.RFC2616.2">D.1</a></li> 1668 <li><em>RFC2822</em> <a href="#RFC2822"><b>9.2</b></a>, <a href="#rfc.xref.RFC2822.1">A</a></li> 1669 <li><em>RFC3629</em> <a href="#rfc.xref.RFC3629.1">2.1</a>, <a href="#RFC3629"><b>9.2</b></a></li> 1670 <li><em>RFC4288</em> <a href="#rfc.xref.RFC4288.1">2.3</a>, <a href="#RFC4288"><b>9.1</b></a></li> 1671 </ul> 1672 </li> 1673 <li><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul> 1674 <li>URI header <a href="#rfc.iref.u.1"><b>C.1</b></a></li> 1675 </ul> 1676 </li> 1677 </ul> 1678 </div> 1513 1679 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> 1680 <p>Copyright © The IETF Trust (2008).</p> 1514 1681 <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the 1515 1682 authors retain all their rights. … … 1529 1696 <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result 1530 1697 of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users 1531 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>>.1698 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>. 1532 1699 </p> 1533 1700 <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary … … 1535 1702 at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>. 1536 1703 </p> 1537 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>1538 <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>1539 </p>1540 <div class="print2col">1541 <ul class="ind">1542 <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind">1543 <li class="indline1">Accept header <a class="iref" href="#rfc.xref.header.accept.1">2.3</a>, <a class="iref" href="#rfc.xref.header.accept.2">4.1</a>, <a class="iref" href="#rfc.iref.a.1"><b>5.1</b></a></li>1544 <li class="indline1">Accept-Charset header <a class="iref" href="#rfc.xref.header.accept-charset.1">4.1</a>, <a class="iref" href="#rfc.iref.a.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.accept-charset.2">C.1</a></li>1545 <li class="indline1">Accept-Encoding header <a class="iref" href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.accept-encoding.2">4.1</a>, <a class="iref" href="#rfc.iref.a.3"><b>5.3</b></a></li>1546 <li class="indline1">Accept-Language header <a class="iref" href="#rfc.xref.header.accept-language.1">4.1</a>, <a class="iref" href="#rfc.iref.a.4"><b>5.4</b></a></li>1547 <li class="indline1">Alternates header <a class="iref" href="#rfc.iref.a.5"><b>C.1</b></a></li>1548 </ul>1549 </li>1550 <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">1551 <li class="indline1">compress <a class="iref" href="#rfc.iref.c.1">2.2</a></li>1552 <li class="indline1">Content-Base header <a class="iref" href="#rfc.iref.c.9"><b>C.1</b></a></li>1553 <li class="indline1">Content-Disposition header <a class="iref" href="#rfc.xref.content-disposition.1">7.2</a>, <a class="iref" href="#rfc.iref.c.7"><b>B.1</b></a></li>1554 <li class="indline1">Content-Encoding header <a class="iref" href="#rfc.xref.header.content-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">3.1</a>, <a class="iref" href="#rfc.iref.c.2"><b>5.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">5.5</a></li>1555 <li class="indline1">Content-Language header <a class="iref" href="#rfc.xref.header.content-language.1">3.1</a>, <a class="iref" href="#rfc.iref.c.3"><b>5.6</b></a></li>1556 <li class="indline1">Content-Location header <a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.c.4"><b>5.7</b></a></li>1557 <li class="indline1">Content-MD5 header <a class="iref" href="#rfc.xref.header.content-md5.1">3.1</a>, <a class="iref" href="#rfc.iref.c.5"><b>5.8</b></a></li>1558 <li class="indline1">Content-Type header <a class="iref" href="#rfc.xref.header.content-type.1">2.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">3.1</a>, <a class="iref" href="#rfc.iref.c.6"><b>5.9</b></a></li>1559 <li class="indline1">Content-Version header <a class="iref" href="#rfc.iref.c.8"><b>C.1</b></a></li>1560 </ul>1561 </li>1562 <li class="indline0"><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul class="ind">1563 <li class="indline1">deflate <a class="iref" href="#rfc.iref.d.1">2.2</a></li>1564 <li class="indline1">Derived-From header <a class="iref" href="#rfc.iref.d.2"><b>C.1</b></a></li>1565 </ul>1566 </li>1567 <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind">1568 <li class="indline1"><tt>Grammar</tt> 1569 <ul class="ind">1570 <li class="indline1"><tt>Accept</tt> <a class="iref" href="#rfc.iref.g.17"><b>5.1</b></a></li>1571 <li class="indline1"><tt>Accept-Charset</tt> <a class="iref" href="#rfc.iref.g.21"><b>5.2</b></a></li>1572 <li class="indline1"><tt>Accept-Encoding</tt> <a class="iref" href="#rfc.iref.g.22"><b>5.3</b></a></li>1573 <li class="indline1"><tt>accept-extension</tt> <a class="iref" href="#rfc.iref.g.20"><b>5.1</b></a></li>1574 <li class="indline1"><tt>Accept-Language</tt> <a class="iref" href="#rfc.iref.g.24"><b>5.4</b></a></li>1575 <li class="indline1"><tt>accept-params</tt> <a class="iref" href="#rfc.iref.g.19"><b>5.1</b></a></li>1576 <li class="indline1"><tt>attribute</tt> <a class="iref" href="#rfc.iref.g.8"><b>2.3</b></a></li>1577 <li class="indline1"><tt>charset</tt> <a class="iref" href="#rfc.iref.g.1"><b>2.1</b></a></li>1578 <li class="indline1"><tt>codings</tt> <a class="iref" href="#rfc.iref.g.23"><b>5.3</b></a></li>1579 <li class="indline1"><tt>content-coding</tt> <a class="iref" href="#rfc.iref.g.2"><b>2.2</b></a></li>1580 <li class="indline1"><tt>content-disposition</tt> <a class="iref" href="#rfc.iref.g.33"><b>B.1</b></a></li>1581 <li class="indline1"><tt>Content-Encoding</tt> <a class="iref" href="#rfc.iref.g.26"><b>5.5</b></a></li>1582 <li class="indline1"><tt>Content-Language</tt> <a class="iref" href="#rfc.iref.g.27"><b>5.6</b></a></li>1583 <li class="indline1"><tt>Content-Location</tt> <a class="iref" href="#rfc.iref.g.28"><b>5.7</b></a></li>1584 <li class="indline1"><tt>Content-MD5</tt> <a class="iref" href="#rfc.iref.g.29"><b>5.8</b></a></li>1585 <li class="indline1"><tt>Content-Type</tt> <a class="iref" href="#rfc.iref.g.31"><b>5.9</b></a></li>1586 <li class="indline1"><tt>disp-extension-parm</tt> <a class="iref" href="#rfc.iref.g.38"><b>B.1</b></a></li>1587 <li class="indline1"><tt>disp-extension-token</tt> <a class="iref" href="#rfc.iref.g.37"><b>B.1</b></a></li>1588 <li class="indline1"><tt>disposition-parm</tt> <a class="iref" href="#rfc.iref.g.35"><b>B.1</b></a></li>1589 <li class="indline1"><tt>disposition-type</tt> <a class="iref" href="#rfc.iref.g.34"><b>B.1</b></a></li>1590 <li class="indline1"><tt>entity-body</tt> <a class="iref" href="#rfc.iref.g.16"><b>3.2</b></a></li>1591 <li class="indline1"><tt>entity-header</tt> <a class="iref" href="#rfc.iref.g.14"><b>3.1</b></a></li>1592 <li class="indline1"><tt>extension-header</tt> <a class="iref" href="#rfc.iref.g.15"><b>3.1</b></a></li>1593 <li class="indline1"><tt>filename-parm</tt> <a class="iref" href="#rfc.iref.g.36"><b>B.1</b></a></li>1594 <li class="indline1"><tt>language-range</tt> <a class="iref" href="#rfc.iref.g.25"><b>5.4</b></a></li>1595 <li class="indline1"><tt>language-tag</tt> <a class="iref" href="#rfc.iref.g.11"><b>2.5</b></a></li>1596 <li class="indline1"><tt>md5-digest</tt> <a class="iref" href="#rfc.iref.g.30"><b>5.8</b></a></li>1597 <li class="indline1"><tt>media-range</tt> <a class="iref" href="#rfc.iref.g.18"><b>5.1</b></a></li>1598 <li class="indline1"><tt>media-type</tt> <a class="iref" href="#rfc.iref.g.4"><b>2.3</b></a></li>1599 <li class="indline1"><tt>MIME-Version</tt> <a class="iref" href="#rfc.iref.g.32"><b>A.1</b></a></li>1600 <li class="indline1"><tt>parameter</tt> <a class="iref" href="#rfc.iref.g.7"><b>2.3</b></a></li>1601 <li class="indline1"><tt>primary-tag</tt> <a class="iref" href="#rfc.iref.g.12"><b>2.5</b></a></li>1602 <li class="indline1"><tt>qvalue</tt> <a class="iref" href="#rfc.iref.g.10"><b>2.4</b></a></li>1603 <li class="indline1"><tt>subtag</tt> <a class="iref" href="#rfc.iref.g.13"><b>2.5</b></a></li>1604 <li class="indline1"><tt>subtype</tt> <a class="iref" href="#rfc.iref.g.6"><b>2.3</b></a></li>1605 <li class="indline1"><tt>type</tt> <a class="iref" href="#rfc.iref.g.5"><b>2.3</b></a></li>1606 <li class="indline1"><tt>value</tt> <a class="iref" href="#rfc.iref.g.9"><b>2.3</b></a></li>1607 </ul>1608 </li>1609 <li class="indline1">gzip <a class="iref" href="#rfc.iref.g.3">2.2</a></li>1610 </ul>1611 </li>1612 <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">1613 <li class="indline1">Headers 1614 <ul class="ind">1615 <li class="indline1">Accept <a class="iref" href="#rfc.xref.header.accept.1">2.3</a>, <a class="iref" href="#rfc.xref.header.accept.2">4.1</a>, <a class="iref" href="#rfc.iref.h.1"><b>5.1</b></a></li>1616 <li class="indline1">Accept-Charset <a class="iref" href="#rfc.xref.header.accept-charset.1">4.1</a>, <a class="iref" href="#rfc.iref.h.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.accept-charset.2">C.1</a></li>1617 <li class="indline1">Accept-Encoding <a class="iref" href="#rfc.xref.header.accept-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.accept-encoding.2">4.1</a>, <a class="iref" href="#rfc.iref.h.3"><b>5.3</b></a></li>1618 <li class="indline1">Accept-Language <a class="iref" href="#rfc.xref.header.accept-language.1">4.1</a>, <a class="iref" href="#rfc.iref.h.4"><b>5.4</b></a></li>1619 <li class="indline1">Alternate <a class="iref" href="#rfc.iref.h.11"><b>C.1</b></a></li>1620 <li class="indline1">Content-Base <a class="iref" href="#rfc.iref.h.17"><b>C.1</b></a></li>1621 <li class="indline1">Content-Disposition <a class="iref" href="#rfc.xref.content-disposition.1">7.2</a>, <a class="iref" href="#rfc.iref.h.10"><b>B.1</b></a></li>1622 <li class="indline1">Content-Encoding <a class="iref" href="#rfc.xref.header.content-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">3.1</a>, <a class="iref" href="#rfc.iref.h.5"><b>5.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">5.5</a></li>1623 <li class="indline1">Content-Language <a class="iref" href="#rfc.xref.header.content-language.1">3.1</a>, <a class="iref" href="#rfc.iref.h.6"><b>5.6</b></a></li>1624 <li class="indline1">Content-Location <a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.h.7"><b>5.7</b></a></li>1625 <li class="indline1">Content-MD5 <a class="iref" href="#rfc.xref.header.content-md5.1">3.1</a>, <a class="iref" href="#rfc.iref.h.8"><b>5.8</b></a></li>1626 <li class="indline1">Content-Type <a class="iref" href="#rfc.xref.header.content-type.1">2.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">3.1</a>, <a class="iref" href="#rfc.iref.h.9"><b>5.9</b></a></li>1627 <li class="indline1">Content-Version <a class="iref" href="#rfc.iref.h.12"><b>C.1</b></a></li>1628 <li class="indline1">Derived-From <a class="iref" href="#rfc.iref.h.13"><b>C.1</b></a></li>1629 <li class="indline1">Link <a class="iref" href="#rfc.iref.h.14"><b>C.1</b></a></li>1630 <li class="indline1">Public <a class="iref" href="#rfc.iref.h.16"><b>C.1</b></a></li>1631 <li class="indline1">URI <a class="iref" href="#rfc.iref.h.15"><b>C.1</b></a></li>1632 </ul>1633 </li>1634 </ul>1635 </li>1636 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">1637 <li class="indline1">identity <a class="iref" href="#rfc.iref.i.1">2.2</a></li>1638 <li class="indline1"><em>ISO-8859-1</em> <a class="iref" href="#rfc.xref.ISO-8859-1.1">2.1.1</a>, <a class="iref" href="#ISO-8859-1"><b>9.1</b></a></li>1639 </ul>1640 </li>1641 <li class="indline0"><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul class="ind">1642 <li class="indline1">Link header <a class="iref" href="#rfc.iref.l.1"><b>C.1</b></a></li>1643 </ul>1644 </li>1645 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">1646 <li class="indline1"><em>Part1</em> <a class="iref" href="#rfc.xref.Part1.1">3.1</a>, <a class="iref" href="#rfc.xref.Part1.2">3.2</a>, <a class="iref" href="#rfc.xref.Part1.3">3.2.2</a>, <a class="iref" href="#Part1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part1.4">A.5</a>, <a class="iref" href="#rfc.xref.Part1.5">C.1</a><ul class="ind">1647 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.2">3.2</a></li>1648 <li class="indline1"><em>Section 4.4</em> <a class="iref" href="#rfc.xref.Part1.3">3.2.2</a></li>1649 <li class="indline1"><em>Section 8.2</em> <a class="iref" href="#rfc.xref.Part1.1">3.1</a></li>1650 <li class="indline1"><em>Section 8.7</em> <a class="iref" href="#rfc.xref.Part1.4">A.5</a></li>1651 </ul>1652 </li>1653 <li class="indline1"><em>Part2</em> <a class="iref" href="#rfc.xref.Part2.1">3.1</a>, <a class="iref" href="#rfc.xref.Part2.2">4.1</a>, <a class="iref" href="#Part2"><b>9.1</b></a><ul class="ind">1654 <li class="indline1"><em>Section 10.1</em> <a class="iref" href="#rfc.xref.Part2.1">3.1</a></li>1655 <li class="indline1"><em>Section 10.9</em> <a class="iref" href="#rfc.xref.Part2.2">4.1</a></li>1656 </ul>1657 </li>1658 <li class="indline1"><em>Part4</em> <a class="iref" href="#rfc.xref.Part4.1">3.1</a>, <a class="iref" href="#Part4"><b>9.1</b></a><ul class="ind">1659 <li class="indline1"><em>Section 6.6</em> <a class="iref" href="#rfc.xref.Part4.1">3.1</a></li>1660 </ul>1661 </li>1662 <li class="indline1"><em>Part5</em> <a class="iref" href="#rfc.xref.Part5.1">2.3.2</a>, <a class="iref" href="#rfc.xref.Part5.2">3.1</a>, <a class="iref" href="#Part5"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part5.3">C.1</a><ul class="ind">1663 <li class="indline1"><em>Section 5.2</em> <a class="iref" href="#rfc.xref.Part5.2">3.1</a></li>1664 <li class="indline1"><em>Section A</em> <a class="iref" href="#rfc.xref.Part5.1">2.3.2</a></li>1665 </ul>1666 </li>1667 <li class="indline1"><em>Part6</em> <a class="iref" href="#rfc.xref.Part6.1">3.1</a>, <a class="iref" href="#rfc.xref.Part6.2">4.1</a>, <a class="iref" href="#rfc.xref.Part6.3">5.7</a>, <a class="iref" href="#Part6"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part6.4">C.1</a><ul class="ind">1668 <li class="indline1"><em>Section 7</em> <a class="iref" href="#rfc.xref.Part6.3">5.7</a></li>1669 <li class="indline1"><em>Section 15.3</em> <a class="iref" href="#rfc.xref.Part6.1">3.1</a></li>1670 <li class="indline1"><em>Section 15.5</em> <a class="iref" href="#rfc.xref.Part6.2">4.1</a></li>1671 </ul>1672 </li>1673 <li class="indline1">Public header <a class="iref" href="#rfc.iref.p.1"><b>C.1</b></a></li>1674 </ul>1675 </li>1676 <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">1677 <li class="indline1"><em>RFC1766</em> <a class="iref" href="#rfc.xref.RFC1766.1">2.5</a>, <a class="iref" href="#RFC1766"><b>9.1</b></a></li>1678 <li class="indline1"><em>RFC1806</em> <a class="iref" href="#rfc.xref.RFC1806.1">7.2</a>, <a class="iref" href="#rfc.xref.RFC1806.2">7.2</a>, <a class="iref" href="#RFC1806"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC1806.3">B.1</a></li>1679 <li class="indline1"><em>RFC1864</em> <a class="iref" href="#rfc.xref.RFC1864.1">5.8</a>, <a class="iref" href="#rfc.xref.RFC1864.2">5.8</a>, <a class="iref" href="#RFC1864"><b>9.1</b></a></li>1680 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#RFC1945"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC1945.1">B</a></li>1681 <li class="indline1"><em>RFC1950</em> <a class="iref" href="#rfc.xref.RFC1950.1">2.2</a>, <a class="iref" href="#RFC1950"><b>9.1</b></a></li>1682 <li class="indline1"><em>RFC1951</em> <a class="iref" href="#rfc.xref.RFC1951.1">2.2</a>, <a class="iref" href="#RFC1951"><b>9.1</b></a></li>1683 <li class="indline1"><em>RFC1952</em> <a class="iref" href="#rfc.xref.RFC1952.1">2.2</a>, <a class="iref" href="#RFC1952"><b>9.1</b></a></li>1684 <li class="indline1"><em>RFC2045</em> <a class="iref" href="#RFC2045"><b>9.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>1685 <li class="indline1"><em>RFC2046</em> <a class="iref" href="#rfc.xref.RFC2046.1">2.3</a>, <a class="iref" href="#rfc.xref.RFC2046.2">2.3.2</a>, <a class="iref" href="#RFC2046"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC2046.3">A.2</a><ul class="ind">1686 <li class="indline1"><em>Section 5.1.1</em> <a class="iref" href="#rfc.xref.RFC2046.2">2.3.2</a></li>1687 </ul>1688 </li>1689 <li class="indline1"><em>RFC2049</em> <a class="iref" href="#RFC2049"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2049.1">A.2</a><ul class="ind">1690 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.RFC2049.1">A.2</a></li>1691 </ul>1692 </li>1693 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">§</a>, <a class="iref" href="#rfc.xref.RFC2068.2">§</a>, <a class="iref" href="#rfc.xref.RFC2068.3">§</a>, <a class="iref" href="#RFC2068"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.4">B</a>, <a class="iref" href="#rfc.xref.RFC2068.5">C.1</a></li>1694 <li class="indline1"><em>RFC2076</em> <a class="iref" href="#RFC2076"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2076.1">B</a></li>1695 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>9.1</b></a></li>1696 <li class="indline1"><em>RFC2183</em> <a class="iref" href="#rfc.xref.RFC2183.1">7.2</a>, <a class="iref" href="#RFC2183"><b>9.2</b></a></li>1697 <li class="indline1"><em>RFC2277</em> <a class="iref" href="#rfc.xref.RFC2277.1">2.1</a>, <a class="iref" href="#RFC2277"><b>9.2</b></a></li>1698 <li class="indline1"><em>RFC2388</em> <a class="iref" href="#rfc.xref.RFC2388.1">2.3.2</a>, <a class="iref" href="#RFC2388"><b>9.2</b></a></li>1699 <li class="indline1"><em>RFC2557</em> <a class="iref" href="#RFC2557"><b>9.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>1700 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">D.1</a></li>1701 <li class="indline1"><em>RFC2822</em> <a class="iref" href="#RFC2822"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2822.1">A</a></li>1702 <li class="indline1"><em>RFC3629</em> <a class="iref" href="#rfc.xref.RFC3629.1">2.1</a>, <a class="iref" href="#RFC3629"><b>9.2</b></a></li>1703 <li class="indline1"><em>RFC4288</em> <a class="iref" href="#rfc.xref.RFC4288.1">2.3</a>, <a class="iref" href="#RFC4288"><b>9.1</b></a></li>1704 </ul>1705 </li>1706 <li class="indline0"><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul class="ind">1707 <li class="indline1">URI header <a class="iref" href="#rfc.iref.u.1"><b>C.1</b></a></li>1708 </ul>1709 </li>1710 </ul>1711 </div>1712 1704 </body> 1713 1705 </html>
Note: See TracChangeset
for help on using the changeset viewer.