![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 1099 for draft-ietf-httpbis/04/p1-messaging.html
- Timestamp:
- 01/01/11 17:23:02 (11 years ago)
- File:
-
- 1 edited
-
draft-ietf-httpbis/04/p1-messaging.html (modified) (39 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/04/p1-messaging.html
r314 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 1: URIs, Connections, and Message Parsing</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 } … … 163 149 border-width: 1px; 164 150 } 151 table.left { 152 margin-right: auto; 153 } 154 table.right { 155 margin-left: auto; 156 } 157 table.center { 158 margin-left: auto; 159 margin-right: auto; 160 } 161 caption { 162 caption-side: bottom; 163 font-weight: bold; 164 font-size: 9pt; 165 margin-top: .5em; 166 } 167 165 168 table.header { 169 border-spacing: 1px; 166 170 width: 95%; 167 171 font-size: 10pt; … … 175 179 white-space: nowrap; 176 180 } 177 t d.header{181 table.header td { 178 182 background-color: gray; 179 183 width: 50%; 180 184 } 181 t d.header a {185 table.header a { 182 186 color: white; 183 187 } … … 190 194 display:table-header-group; 191 195 } 192 ul.toc {196 ul.toc, ul.toc ul { 193 197 list-style: none; 194 198 margin-left: 1.5em; … … 196 200 padding-left: 0em; 197 201 } 198 li.tocline0{202 ul.toc li { 199 203 line-height: 150%; 200 204 font-weight: bold; … … 203 207 margin-right: 0em; 204 208 } 205 li.tocline1{209 ul.toc li li { 206 210 line-height: normal; 207 211 font-weight: normal; … … 210 214 margin-right: 0em; 211 215 } 212 li. tocline2{216 li.excluded { 213 217 font-size: 0pt; 214 218 } … … 216 220 margin-left: 0em; 217 221 } 218 ul.ind {222 ul.ind, ul.ind ul { 219 223 list-style: none; 220 224 margin-left: 1.5em; 221 225 margin-right: 0em; 222 226 padding-left: 0em; 223 } 224 li.indline0 { 227 page-break-before: avoid; 228 } 229 ul.ind li { 225 230 font-weight: bold; 226 231 line-height: 200%; … … 228 233 margin-right: 0em; 229 234 } 230 li.indline1{235 ul.ind li li { 231 236 font-weight: normal; 232 237 line-height: 150%; 233 238 margin-left: 0em; 234 239 margin-right: 0em; 240 } 241 .avoidbreak { 242 page-break-inside: avoid; 235 243 } 236 244 .bcp14 { … … 317 325 } 318 326 319 a.iref{327 ul.ind li li a { 320 328 content: target-counter(attr(href), page); 321 329 } … … 330 338 @page { 331 339 @top-left { 332 content: "I NTERNET DRAFT";340 content: "Internet-Draft"; 333 341 } 334 342 @top-right { … … 380 388 <link rel="Appendix" title="C Compatibility with Previous Versions" href="#rfc.section.C"> 381 389 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 382 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.387, 2008-08-08 13:06:55, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 383 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 384 <meta name="DC.Creator" content="Fielding, R."> 385 <meta name="DC.Creator" content="Gettys, J."> 386 <meta name="DC.Creator" content="Mogul, J."> 387 <meta name="DC.Creator" content="Frystyk, H."> 388 <meta name="DC.Creator" content="Masinter, L."> 389 <meta name="DC.Creator" content="Leach, P."> 390 <meta name="DC.Creator" content="Berners-Lee, T."> 391 <meta name="DC.Creator" content="Lafon, Y."> 392 <meta name="DC.Creator" content="Reschke, J. F."> 393 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-04"> 394 <meta name="DC.Date.Issued" scheme="ISO8601" content="2008-08"> 395 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 396 <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 1 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."> 390 <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/"> 391 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 392 <meta name="dct.creator" content="Fielding, R."> 393 <meta name="dct.creator" content="Gettys, J."> 394 <meta name="dct.creator" content="Mogul, J."> 395 <meta name="dct.creator" content="Frystyk, H."> 396 <meta name="dct.creator" content="Masinter, L."> 397 <meta name="dct.creator" content="Leach, P."> 398 <meta name="dct.creator" content="Berners-Lee, T."> 399 <meta name="dct.creator" content="Lafon, Y."> 400 <meta name="dct.creator" content="Reschke, J. F."> 401 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-04"> 402 <meta name="dct.issued" scheme="ISO8601" content="2008-08-29"> 403 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 404 <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 1 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."> 405 <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 1 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."> 397 406 </head> 398 407 <body> 399 <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1"> 400 <tr> 401 <td class="header left">Network Working Group</td> 402 <td class="header right">R. Fielding, Editor</td> 403 </tr> 404 <tr> 405 <td class="header left">Internet Draft</td> 406 <td class="header right">Day Software</td> 407 </tr> 408 <tr> 409 <td class="header left"> 410 <draft-ietf-httpbis-p1-messaging-04> 411 412 </td> 413 <td class="header right">J. Gettys</td> 414 </tr> 415 <tr> 416 <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 417 </td> 418 <td class="header right">One Laptop per Child</td> 419 </tr> 420 <tr> 421 <td class="header left">Intended status: Standards Track</td> 422 <td class="header right">J. Mogul</td> 423 </tr> 424 <tr> 425 <td class="header left">Expires: February 2009</td> 426 <td class="header right">HP</td> 427 </tr> 428 <tr> 429 <td class="header left"></td> 430 <td class="header right">H. Frystyk</td> 431 </tr> 432 <tr> 433 <td class="header left"></td> 434 <td class="header right">Microsoft</td> 435 </tr> 436 <tr> 437 <td class="header left"></td> 438 <td class="header right">L. Masinter</td> 439 </tr> 440 <tr> 441 <td class="header left"></td> 442 <td class="header right">Adobe Systems</td> 443 </tr> 444 <tr> 445 <td class="header left"></td> 446 <td class="header right">P. Leach</td> 447 </tr> 448 <tr> 449 <td class="header left"></td> 450 <td class="header right">Microsoft</td> 451 </tr> 452 <tr> 453 <td class="header left"></td> 454 <td class="header right">T. Berners-Lee</td> 455 </tr> 456 <tr> 457 <td class="header left"></td> 458 <td class="header right">W3C/MIT</td> 459 </tr> 460 <tr> 461 <td class="header left"></td> 462 <td class="header right">Y. Lafon, Editor</td> 463 </tr> 464 <tr> 465 <td class="header left"></td> 466 <td class="header right">W3C</td> 467 </tr> 468 <tr> 469 <td class="header left"></td> 470 <td class="header right">J. F. Reschke, Editor</td> 471 </tr> 472 <tr> 473 <td class="header left"></td> 474 <td class="header right">greenbytes</td> 475 </tr> 476 <tr> 477 <td class="header left"></td> 478 <td class="header right">August 29, 2008</td> 479 </tr> 408 <table class="header"> 409 <tbody> 410 <tr> 411 <td class="left">Network Working Group</td> 412 <td class="right">R. Fielding, Editor</td> 413 </tr> 414 <tr> 415 <td class="left">Internet-Draft</td> 416 <td class="right">Day Software</td> 417 </tr> 418 <tr> 419 <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 420 </td> 421 <td class="right">J. Gettys</td> 422 </tr> 423 <tr> 424 <td class="left">Intended status: Standards Track</td> 425 <td class="right">One Laptop per Child</td> 426 </tr> 427 <tr> 428 <td class="left">Expires: March 2, 2009</td> 429 <td class="right">J. Mogul</td> 430 </tr> 431 <tr> 432 <td class="left"></td> 433 <td class="right">HP</td> 434 </tr> 435 <tr> 436 <td class="left"></td> 437 <td class="right">H. Frystyk</td> 438 </tr> 439 <tr> 440 <td class="left"></td> 441 <td class="right">Microsoft</td> 442 </tr> 443 <tr> 444 <td class="left"></td> 445 <td class="right">L. Masinter</td> 446 </tr> 447 <tr> 448 <td class="left"></td> 449 <td class="right">Adobe Systems</td> 450 </tr> 451 <tr> 452 <td class="left"></td> 453 <td class="right">P. Leach</td> 454 </tr> 455 <tr> 456 <td class="left"></td> 457 <td class="right">Microsoft</td> 458 </tr> 459 <tr> 460 <td class="left"></td> 461 <td class="right">T. Berners-Lee</td> 462 </tr> 463 <tr> 464 <td class="left"></td> 465 <td class="right">W3C/MIT</td> 466 </tr> 467 <tr> 468 <td class="left"></td> 469 <td class="right">Y. Lafon, Editor</td> 470 </tr> 471 <tr> 472 <td class="left"></td> 473 <td class="right">W3C</td> 474 </tr> 475 <tr> 476 <td class="left"></td> 477 <td class="right">J. Reschke, Editor</td> 478 </tr> 479 <tr> 480 <td class="left"></td> 481 <td class="right">greenbytes</td> 482 </tr> 483 <tr> 484 <td class="left"></td> 485 <td class="right">August 29, 2008</td> 486 </tr> 487 </tbody> 480 488 </table> 481 489 <p class="title">HTTP/1.1, part 1: URIs, Connections, and Message Parsing<br><span class="filename">draft-ietf-httpbis-p1-messaging-04</span></p> … … 492 500 in progress”. 493 501 </p> 494 <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>>.495 </p> 496 <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>>.497 </p> 498 <p>This Internet-Draft will expire in February2009.</p>502 <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>. 503 </p> 504 <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>. 505 </p> 506 <p>This Internet-Draft will expire on March 2, 2009.</p> 499 507 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 500 508 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information … … 514 522 <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1> 515 523 <ul class="toc"> 516 <li class="tocline0">1. <a href="#introduction">Introduction</a><ul class="toc">517 <li class="tocline1">1.1 <a href="#intro.purpose">Purpose</a></li>518 <li class="tocline1">1.2 <a href="#intro.requirements">Requirements</a></li>519 <li class="tocline1">1.3 <a href="#intro.terminology">Terminology</a></li>520 <li class="tocline1">1.4 <a href="#intro.overall.operation">Overall Operation</a></li>524 <li>1. <a href="#introduction">Introduction</a><ul> 525 <li>1.1 <a href="#intro.purpose">Purpose</a></li> 526 <li>1.2 <a href="#intro.requirements">Requirements</a></li> 527 <li>1.3 <a href="#intro.terminology">Terminology</a></li> 528 <li>1.4 <a href="#intro.overall.operation">Overall Operation</a></li> 521 529 </ul> 522 530 </li> 523 <li class="tocline0">2. <a href="#notation">Notational Conventions and Generic Grammar</a><ul class="toc">524 <li class="tocline1">2.1 <a href="#notation.abnf">Augmented BNF</a></li>525 <li class="tocline1">2.2 <a href="#basic.rules">Basic Rules</a></li>526 <li class="tocline1">2.3 <a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>531 <li>2. <a href="#notation">Notational Conventions and Generic Grammar</a><ul> 532 <li>2.1 <a href="#notation.abnf">Augmented BNF</a></li> 533 <li>2.2 <a href="#basic.rules">Basic Rules</a></li> 534 <li>2.3 <a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li> 527 535 </ul> 528 536 </li> 529 <li class="tocline0">3. <a href="#protocol.parameters">Protocol Parameters</a><ul class="toc">530 <li class="tocline1">3.1 <a href="#http.version">HTTP Version</a></li>531 <li class="tocline1">3.2 <a href="#uri">Uniform Resource Identifiers</a><ul class="toc">532 <li class="tocline1">3.2.1 <a href="#general.syntax">General Syntax</a></li>533 <li class="tocline1">3.2.2 <a href="#http.url">http URL</a></li>534 <li class="tocline1">3.2.3 <a href="#uri.comparison">URI Comparison</a></li>537 <li>3. <a href="#protocol.parameters">Protocol Parameters</a><ul> 538 <li>3.1 <a href="#http.version">HTTP Version</a></li> 539 <li>3.2 <a href="#uri">Uniform Resource Identifiers</a><ul> 540 <li>3.2.1 <a href="#general.syntax">General Syntax</a></li> 541 <li>3.2.2 <a href="#http.url">http URL</a></li> 542 <li>3.2.3 <a href="#uri.comparison">URI Comparison</a></li> 535 543 </ul> 536 544 </li> 537 <li class="tocline1">3.3 <a href="#date.time.formats">Date/Time Formats</a><ul class="toc">538 <li class="tocline1">3.3.1 <a href="#full.date">Full Date</a></li>545 <li>3.3 <a href="#date.time.formats">Date/Time Formats</a><ul> 546 <li>3.3.1 <a href="#full.date">Full Date</a></li> 539 547 </ul> 540 548 </li> 541 <li class="tocline1">3.4 <a href="#transfer.codings">Transfer Codings</a><ul class="toc">542 <li class="tocline1">3.4.1 <a href="#chunked.transfer.encoding">Chunked Transfer Coding</a></li>549 <li>3.4 <a href="#transfer.codings">Transfer Codings</a><ul> 550 <li>3.4.1 <a href="#chunked.transfer.encoding">Chunked Transfer Coding</a></li> 543 551 </ul> 544 552 </li> 545 <li class="tocline1">3.5 <a href="#product.tokens">Product Tokens</a></li>553 <li>3.5 <a href="#product.tokens">Product Tokens</a></li> 546 554 </ul> 547 555 </li> 548 <li class="tocline0">4. <a href="#http.message">HTTP Message</a><ul class="toc">549 <li class="tocline1">4.1 <a href="#message.types">Message Types</a></li>550 <li class="tocline1">4.2 <a href="#message.headers">Message Headers</a></li>551 <li class="tocline1">4.3 <a href="#message.body">Message Body</a></li>552 <li class="tocline1">4.4 <a href="#message.length">Message Length</a></li>553 <li class="tocline1">4.5 <a href="#general.header.fields">General Header Fields</a></li>556 <li>4. <a href="#http.message">HTTP Message</a><ul> 557 <li>4.1 <a href="#message.types">Message Types</a></li> 558 <li>4.2 <a href="#message.headers">Message Headers</a></li> 559 <li>4.3 <a href="#message.body">Message Body</a></li> 560 <li>4.4 <a href="#message.length">Message Length</a></li> 561 <li>4.5 <a href="#general.header.fields">General Header Fields</a></li> 554 562 </ul> 555 563 </li> 556 <li class="tocline0">5. <a href="#request">Request</a><ul class="toc">557 <li class="tocline1">5.1 <a href="#request-line">Request-Line</a><ul class="toc">558 <li class="tocline1">5.1.1 <a href="#method">Method</a></li>559 <li class="tocline1">5.1.2 <a href="#request-uri">Request-URI</a></li>564 <li>5. <a href="#request">Request</a><ul> 565 <li>5.1 <a href="#request-line">Request-Line</a><ul> 566 <li>5.1.1 <a href="#method">Method</a></li> 567 <li>5.1.2 <a href="#request-uri">Request-URI</a></li> 560 568 </ul> 561 569 </li> 562 <li class="tocline1">5.2 <a href="#the.resource.identified.by.a.request">The Resource Identified by a Request</a></li>570 <li>5.2 <a href="#the.resource.identified.by.a.request">The Resource Identified by a Request</a></li> 563 571 </ul> 564 572 </li> 565 <li class="tocline0">6. <a href="#response">Response</a><ul class="toc">566 <li class="tocline1">6.1 <a href="#status-line">Status-Line</a><ul class="toc">567 <li class="tocline1">6.1.1 <a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></li>573 <li>6. <a href="#response">Response</a><ul> 574 <li>6.1 <a href="#status-line">Status-Line</a><ul> 575 <li>6.1.1 <a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></li> 568 576 </ul> 569 577 </li> 570 578 </ul> 571 579 </li> 572 <li class="tocline0">7. <a href="#connections">Connections</a><ul class="toc">573 <li class="tocline1">7.1 <a href="#persistent.connections">Persistent Connections</a><ul class="toc">574 <li class="tocline1">7.1.1 <a href="#persistent.purpose">Purpose</a></li>575 <li class="tocline1">7.1.2 <a href="#persistent.overall">Overall Operation</a><ul class="toc">576 <li class="tocline1">7.1.2.1 <a href="#persistent.negotiation">Negotiation</a></li>577 <li class="tocline1">7.1.2.2 <a href="#pipelining">Pipelining</a></li>580 <li>7. <a href="#connections">Connections</a><ul> 581 <li>7.1 <a href="#persistent.connections">Persistent Connections</a><ul> 582 <li>7.1.1 <a href="#persistent.purpose">Purpose</a></li> 583 <li>7.1.2 <a href="#persistent.overall">Overall Operation</a><ul> 584 <li>7.1.2.1 <a href="#persistent.negotiation">Negotiation</a></li> 585 <li>7.1.2.2 <a href="#pipelining">Pipelining</a></li> 578 586 </ul> 579 587 </li> 580 <li class="tocline1">7.1.3 <a href="#persistent.proxy">Proxy Servers</a></li>581 <li class="tocline1">7.1.4 <a href="#persistent.practical">Practical Considerations</a></li>588 <li>7.1.3 <a href="#persistent.proxy">Proxy Servers</a></li> 589 <li>7.1.4 <a href="#persistent.practical">Practical Considerations</a></li> 582 590 </ul> 583 591 </li> 584 <li class="tocline1">7.2 <a href="#message.transmission.requirements">Message Transmission Requirements</a><ul class="toc">585 <li class="tocline1">7.2.1 <a href="#persistent.flow">Persistent Connections and Flow Control</a></li>586 <li class="tocline1">7.2.2 <a href="#persistent.monitor">Monitoring Connections for Error Status Messages</a></li>587 <li class="tocline1">7.2.3 <a href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></li>588 <li class="tocline1">7.2.4 <a href="#connection.premature">Client Behavior if Server Prematurely Closes Connection</a></li>592 <li>7.2 <a href="#message.transmission.requirements">Message Transmission Requirements</a><ul> 593 <li>7.2.1 <a href="#persistent.flow">Persistent Connections and Flow Control</a></li> 594 <li>7.2.2 <a href="#persistent.monitor">Monitoring Connections for Error Status Messages</a></li> 595 <li>7.2.3 <a href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></li> 596 <li>7.2.4 <a href="#connection.premature">Client Behavior if Server Prematurely Closes Connection</a></li> 589 597 </ul> 590 598 </li> 591 599 </ul> 592 600 </li> 593 <li class="tocline0">8. <a href="#header.fields">Header Field Definitions</a><ul class="toc">594 <li class="tocline1">8.1 <a href="#header.connection">Connection</a></li>595 <li class="tocline1">8.2 <a href="#header.content-length">Content-Length</a></li>596 <li class="tocline1">8.3 <a href="#header.date">Date</a><ul class="toc">597 <li class="tocline1">8.3.1 <a href="#clockless.origin.server.operation">Clockless Origin Server Operation</a></li>601 <li>8. <a href="#header.fields">Header Field Definitions</a><ul> 602 <li>8.1 <a href="#header.connection">Connection</a></li> 603 <li>8.2 <a href="#header.content-length">Content-Length</a></li> 604 <li>8.3 <a href="#header.date">Date</a><ul> 605 <li>8.3.1 <a href="#clockless.origin.server.operation">Clockless Origin Server Operation</a></li> 598 606 </ul> 599 607 </li> 600 <li class="tocline1">8.4 <a href="#header.host">Host</a></li>601 <li class="tocline1">8.5 <a href="#header.te">TE</a></li>602 <li class="tocline1">8.6 <a href="#header.trailer">Trailer</a></li>603 <li class="tocline1">8.7 <a href="#header.transfer-encoding">Transfer-Encoding</a></li>604 <li class="tocline1">8.8 <a href="#header.upgrade">Upgrade</a></li>605 <li class="tocline1">8.9 <a href="#header.via">Via</a></li>608 <li>8.4 <a href="#header.host">Host</a></li> 609 <li>8.5 <a href="#header.te">TE</a></li> 610 <li>8.6 <a href="#header.trailer">Trailer</a></li> 611 <li>8.7 <a href="#header.transfer-encoding">Transfer-Encoding</a></li> 612 <li>8.8 <a href="#header.upgrade">Upgrade</a></li> 613 <li>8.9 <a href="#header.via">Via</a></li> 606 614 </ul> 607 615 </li> 608 <li class="tocline0">9. <a href="#IANA.considerations">IANA Considerations</a><ul class="toc">609 <li class="tocline1">9.1 <a href="#message.header.registration">Message Header Registration</a></li>610 <li class="tocline1">9.2 <a href="#uri.scheme.registration">URI Scheme Registration</a></li>611 <li class="tocline1">9.3 <a href="#internet.media.type.http">Internet Media Type Registrations</a><ul class="toc">612 <li class="tocline1">9.3.1 <a href="#internet.media.type.message.http">Internet Media Type message/http</a></li>613 <li class="tocline1">9.3.2 <a href="#internet.media.type.application.http">Internet Media Type application/http</a></li>616 <li>9. <a href="#IANA.considerations">IANA Considerations</a><ul> 617 <li>9.1 <a href="#message.header.registration">Message Header Registration</a></li> 618 <li>9.2 <a href="#uri.scheme.registration">URI Scheme Registration</a></li> 619 <li>9.3 <a href="#internet.media.type.http">Internet Media Type Registrations</a><ul> 620 <li>9.3.1 <a href="#internet.media.type.message.http">Internet Media Type message/http</a></li> 621 <li>9.3.2 <a href="#internet.media.type.application.http">Internet Media Type application/http</a></li> 614 622 </ul> 615 623 </li> 616 624 </ul> 617 625 </li> 618 <li class="tocline0">10. <a href="#security.considerations">Security Considerations</a><ul class="toc">619 <li class="tocline1">10.1 <a href="#personal.information">Personal Information</a></li>620 <li class="tocline1">10.2 <a href="#abuse.of.server.log.information">Abuse of Server Log Information</a></li>621 <li class="tocline1">10.3 <a href="#attack.pathname">Attacks Based On File and Path Names</a></li>622 <li class="tocline1">10.4 <a href="#dns.spoofing">DNS Spoofing</a></li>623 <li class="tocline1">10.5 <a href="#attack.proxies">Proxies and Caching</a></li>624 <li class="tocline1">10.6 <a href="#attack.DoS">Denial of Service Attacks on Proxies</a></li>626 <li>10. <a href="#security.considerations">Security Considerations</a><ul> 627 <li>10.1 <a href="#personal.information">Personal Information</a></li> 628 <li>10.2 <a href="#abuse.of.server.log.information">Abuse of Server Log Information</a></li> 629 <li>10.3 <a href="#attack.pathname">Attacks Based On File and Path Names</a></li> 630 <li>10.4 <a href="#dns.spoofing">DNS Spoofing</a></li> 631 <li>10.5 <a href="#attack.proxies">Proxies and Caching</a></li> 632 <li>10.6 <a href="#attack.DoS">Denial of Service Attacks on Proxies</a></li> 625 633 </ul> 626 634 </li> 627 <li class="tocline0">11. <a href="#ack">Acknowledgments</a></li>628 <li class="tocline0">12. <a href="#rfc.references">References</a><ul class="toc">629 <li class="tocline1">12.1 <a href="#rfc.references.1">Normative References</a></li>630 <li class="tocline1">12.2 <a href="#rfc.references.2">Informative References</a></li>635 <li>11. <a href="#ack">Acknowledgments</a></li> 636 <li>12. <a href="#rfc.references">References</a><ul> 637 <li>12.1 <a href="#rfc.references.1">Normative References</a></li> 638 <li>12.2 <a href="#rfc.references.2">Informative References</a></li> 631 639 </ul> 632 640 </li> 633 <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>634 <li class="tocline0">A. <a href="#tolerant.applications">Tolerant Applications</a></li>635 <li class="tocline0">B. <a href="#conversion.of.date.formats">Conversion of Date Formats</a></li>636 <li class="tocline0">C. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc">637 <li class="tocline1">C.1 <a href="#changes.from.1.0">Changes from HTTP/1.0</a><ul class="toc">638 <li class="tocline1">C.1.1 <a href="#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses">Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses</a></li>641 <li><a href="#rfc.authors">Authors' Addresses</a></li> 642 <li>A. <a href="#tolerant.applications">Tolerant Applications</a></li> 643 <li>B. <a href="#conversion.of.date.formats">Conversion of Date Formats</a></li> 644 <li>C. <a href="#compatibility">Compatibility with Previous Versions</a><ul> 645 <li>C.1 <a href="#changes.from.1.0">Changes from HTTP/1.0</a><ul> 646 <li>C.1.1 <a href="#changes.to.simplify.multi-homed.web.servers.and.conserve.ip.addresses">Changes to Simplify Multi-homed Web Servers and Conserve IP Addresses</a></li> 639 647 </ul> 640 648 </li> 641 <li class="tocline1">C.2 <a href="#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></li>642 <li class="tocline1">C.3 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>643 <li class="tocline1">C.4 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>649 <li>C.2 <a href="#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></li> 650 <li>C.3 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li> 651 <li>C.4 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 644 652 </ul> 645 653 </li> 646 <li class="tocline0">D. <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">647 <li class="tocline1">D.1 <a href="#rfc.section.D.1">Since RFC2616</a></li>648 <li class="tocline1">D.2 <a href="#rfc.section.D.2">Since draft-ietf-httpbis-p1-messaging-00</a></li>649 <li class="tocline1">D.3 <a href="#rfc.section.D.3">Since draft-ietf-httpbis-p1-messaging-01</a></li>650 <li class="tocline1">D.4 <a href="#changes.since.02">Since draft-ietf-httpbis-p1-messaging-02</a></li>651 <li class="tocline1">D.5 <a href="#changes.since.03">Since draft-ietf-httpbis-p1-messaging-03</a></li>654 <li>D. <a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul> 655 <li>D.1 <a href="#rfc.section.D.1">Since RFC2616</a></li> 656 <li>D.2 <a href="#rfc.section.D.2">Since draft-ietf-httpbis-p1-messaging-00</a></li> 657 <li>D.3 <a href="#rfc.section.D.3">Since draft-ietf-httpbis-p1-messaging-01</a></li> 658 <li>D.4 <a href="#changes.since.02">Since draft-ietf-httpbis-p1-messaging-02</a></li> 659 <li>D.5 <a href="#changes.since.03">Since draft-ietf-httpbis-p1-messaging-03</a></li> 652 660 </ul> 653 661 </li> 654 <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>655 <li class="tocline0"><a href="#rfc.index">Index</a></li>662 <li><a href="#rfc.index">Index</a></li> 663 <li><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li> 656 664 </ul> 657 665 <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> <a id="introduction" href="#introduction">Introduction</a></h1> … … 694 702 <p id="rfc.section.1.3.p.2"> <span id="rfc.iref.c.1"></span> <dfn>connection</dfn> 695 703 </p> 696 < dl class="empty">697 < dd>A transport layer virtual circuit established between two programs for the purpose of communication.</dd>698 </ dl>704 <ul class="empty"> 705 <li>A transport layer virtual circuit established between two programs for the purpose of communication.</li> 706 </ul> 699 707 <p id="rfc.section.1.3.p.3"> <span id="rfc.iref.m.1"></span> <dfn>message</dfn> 700 708 </p> 701 < dl class="empty">702 < dd>The basic unit of HTTP communication, consisting of a structured sequence of octets matching the syntax defined in <a href="#http.message" title="HTTP Message">Section 4</a> and transmitted via the connection.703 </ dd>704 </ dl>709 <ul class="empty"> 710 <li>The basic unit of HTTP communication, consisting of a structured sequence of octets matching the syntax defined in <a href="#http.message" title="HTTP Message">Section 4</a> and transmitted via the connection. 711 </li> 712 </ul> 705 713 <p id="rfc.section.1.3.p.4"> <span id="rfc.iref.r.1"></span> <dfn>request</dfn> 706 714 </p> 707 < dl class="empty">708 < dd>An HTTP request message, as defined in <a href="#request" title="Request">Section 5</a>.709 </ dd>710 </ dl>715 <ul class="empty"> 716 <li>An HTTP request message, as defined in <a href="#request" title="Request">Section 5</a>. 717 </li> 718 </ul> 711 719 <p id="rfc.section.1.3.p.5"> <span id="rfc.iref.r.2"></span> <dfn>response</dfn> 712 720 </p> 713 < dl class="empty">714 < dd>An HTTP response message, as defined in <a href="#response" title="Response">Section 6</a>.715 </ dd>716 </ dl>721 <ul class="empty"> 722 <li>An HTTP response message, as defined in <a href="#response" title="Response">Section 6</a>. 723 </li> 724 </ul> 717 725 <p id="rfc.section.1.3.p.6"> <span id="rfc.iref.r.3"></span> <dfn>resource</dfn> 718 726 </p> 719 < dl class="empty">720 < dd>A network data object or service that can be identified by a URI, as defined in <a href="#uri" title="Uniform Resource Identifiers">Section 3.2</a>. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, and resolutions) or727 <ul class="empty"> 728 <li>A network data object or service that can be identified by a URI, as defined in <a href="#uri" title="Uniform Resource Identifiers">Section 3.2</a>. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, and resolutions) or 721 729 vary in other ways. 722 </ dd>723 </ dl>730 </li> 731 </ul> 724 732 <p id="rfc.section.1.3.p.7"> <span id="rfc.iref.e.1"></span> <dfn>entity</dfn> 725 733 </p> 726 < dl class="empty">727 < dd>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of734 <ul class="empty"> 735 <li>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of 728 736 entity-header fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="Entity">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. 729 </ dd>730 </ dl>737 </li> 738 </ul> 731 739 <p id="rfc.section.1.3.p.8"> <span id="rfc.iref.r.4"></span> <dfn>representation</dfn> 732 740 </p> 733 < dl class="empty">734 < dd>An entity included with a response that is subject to content negotiation, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. There may exist multiple representations associated with a particular response status.735 </ dd>736 </ dl>741 <ul class="empty"> 742 <li>An entity included with a response that is subject to content negotiation, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. There may exist multiple representations associated with a particular response status. 743 </li> 744 </ul> 737 745 <p id="rfc.section.1.3.p.9"> <span id="rfc.iref.c.2"></span> <dfn>content negotiation</dfn> 738 746 </p> 739 < dl class="empty">740 < dd>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. The representation of entities in any response can be negotiated (including error responses).741 </ dd>742 </ dl>747 <ul class="empty"> 748 <li>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. The representation of entities in any response can be negotiated (including error responses). 749 </li> 750 </ul> 743 751 <p id="rfc.section.1.3.p.10"> <span id="rfc.iref.v.1"></span> <dfn>variant</dfn> 744 752 </p> 745 < dl class="empty">746 < dd>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations753 <ul class="empty"> 754 <li>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations 747 755 is termed a `variant'. Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation. 748 </ dd>749 </ dl>756 </li> 757 </ul> 750 758 <p id="rfc.section.1.3.p.11"> <span id="rfc.iref.c.3"></span> <dfn>client</dfn> 751 759 </p> 752 < dl class="empty">753 < dd>A program that establishes connections for the purpose of sending requests.</dd>754 </ dl>760 <ul class="empty"> 761 <li>A program that establishes connections for the purpose of sending requests.</li> 762 </ul> 755 763 <p id="rfc.section.1.3.p.12"> <span id="rfc.iref.u.1"></span> <dfn>user agent</dfn> 756 764 </p> 757 < dl class="empty">758 < dd>The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user765 <ul class="empty"> 766 <li>The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user 759 767 tools. 760 </ dd>761 </ dl>768 </li> 769 </ul> 762 770 <p id="rfc.section.1.3.p.13"> <span id="rfc.iref.s.1"></span> <dfn>server</dfn> 763 771 </p> 764 < dl class="empty">765 < dd>An application program that accepts connections in order to service requests by sending back responses. Any given program772 <ul class="empty"> 773 <li>An application program that accepts connections in order to service requests by sending back responses. Any given program 766 774 may be capable of being both a client and a server; our use of these terms refers only to the role being performed by the 767 775 program for a particular connection, rather than to the program's capabilities in general. Likewise, any server may act as 768 776 an origin server, proxy, gateway, or tunnel, switching behavior based on the nature of each request. 769 </ dd>770 </ dl>777 </li> 778 </ul> 771 779 <p id="rfc.section.1.3.p.14"> <span id="rfc.iref.o.1"></span> <dfn>origin server</dfn> 772 780 </p> 773 < dl class="empty">774 < dd>The server on which a given resource resides or is to be created.</dd>775 </ dl>781 <ul class="empty"> 782 <li>The server on which a given resource resides or is to be created.</li> 783 </ul> 776 784 <p id="rfc.section.1.3.p.15"> <span id="rfc.iref.p.1"></span> <dfn>proxy</dfn> 777 785 </p> 778 < dl class="empty">779 < dd>An intermediary program which acts as both a server and a client for the purpose of making requests on behalf of other clients.786 <ul class="empty"> 787 <li>An intermediary program which acts as both a server and a client for the purpose of making requests on behalf of other clients. 780 788 Requests are serviced internally or by passing them on, with possible translation, to other servers. A proxy <em class="bcp14">MUST</em> implement both the client and server requirements of this specification. A "transparent proxy" is a proxy that does not modify 781 789 the request or response beyond what is required for proxy authentication and identification. A "non-transparent proxy" is … … 783 791 services, media type transformation, protocol reduction, or anonymity filtering. Except where either transparent or non-transparent 784 792 behavior is explicitly stated, the HTTP proxy requirements apply to both types of proxies. 785 </ dd>786 </ dl>793 </li> 794 </ul> 787 795 <p id="rfc.section.1.3.p.16"> <span id="rfc.iref.g.1"></span> <dfn>gateway</dfn> 788 796 </p> 789 < dl class="empty">790 < dd>A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the797 <ul class="empty"> 798 <li>A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the 791 799 origin server for the requested resource; the requesting client may not be aware that it is communicating with a gateway. 792 </ dd>793 </ dl>800 </li> 801 </ul> 794 802 <p id="rfc.section.1.3.p.17"> <span id="rfc.iref.t.1"></span> <dfn>tunnel</dfn> 795 803 </p> 796 < dl class="empty">797 < dd>An intermediary program which is acting as a blind relay between two connections. Once active, a tunnel is not considered804 <ul class="empty"> 805 <li>An intermediary program which is acting as a blind relay between two connections. Once active, a tunnel is not considered 798 806 a party to the HTTP communication, though the tunnel may have been initiated by an HTTP request. The tunnel ceases to exist 799 807 when both ends of the relayed connections are closed. 800 </ dd>801 </ dl>808 </li> 809 </ul> 802 810 <p id="rfc.section.1.3.p.18"> <span id="rfc.iref.c.4"></span> <dfn>cache</dfn> 803 811 </p> 804 < dl class="empty">805 < dd>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion.812 <ul class="empty"> 813 <li>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion. 806 814 A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent 807 815 requests. Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel. 808 </ dd>809 </ dl>816 </li> 817 </ul> 810 818 <p id="rfc.section.1.3.p.19"> <span id="rfc.iref.c.5"></span> <dfn>cacheable</dfn> 811 819 </p> 812 < dl class="empty">813 < dd>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.820 <ul class="empty"> 821 <li>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests. 814 822 The rules for determining the cacheability of HTTP responses are defined in <a href="p6-cache.html#caching" title="Introduction">Section 1</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. Even if a resource is cacheable, there may be additional constraints on whether a cache can use the cached copy for a particular 815 823 request. 816 </ dd>817 </ dl>824 </li> 825 </ul> 818 826 <p id="rfc.section.1.3.p.20"> <span id="rfc.iref.u.2"></span> <span id="rfc.iref.d.1"></span> <dfn>upstream</dfn>/<dfn>downstream</dfn> 819 827 </p> 820 < dl class="empty">821 < dd>Upstream and downstream describe the flow of a message: all messages flow from upstream to downstream.</dd>822 </ dl>828 <ul class="empty"> 829 <li>Upstream and downstream describe the flow of a message: all messages flow from upstream to downstream.</li> 830 </ul> 823 831 <p id="rfc.section.1.3.p.21"> <span id="rfc.iref.i.1"></span> <span id="rfc.iref.o.2"></span> <dfn>inbound</dfn>/<dfn>outbound</dfn> 824 832 </p> 825 < dl class="empty">826 < dd>Inbound and outbound refer to the request and response paths for messages: "inbound" means "traveling toward the origin server",833 <ul class="empty"> 834 <li>Inbound and outbound refer to the request and response paths for messages: "inbound" means "traveling toward the origin server", 827 835 and "outbound" means "traveling toward the user agent" 828 </ dd>829 </ dl>836 </li> 837 </ul> 830 838 <h2 id="rfc.section.1.4"><a href="#rfc.section.1.4">1.4</a> <a id="intro.overall.operation" href="#intro.overall.operation">Overall Operation</a></h2> 831 839 <p id="rfc.section.1.4.p.1">HTTP is a request/response protocol. A client sends a request to the server in the form of a request method, URI, and protocol … … 894 902 </p> 895 903 <p id="rfc.section.2.1.p.2">name = definition </p> 896 < dl class="empty">897 < dd>The name of a rule is simply the name itself (without any enclosing "<" and ">") and is separated from its definition by the904 <ul class="empty"> 905 <li>The name of a rule is simply the name itself (without any enclosing "<" and ">") and is separated from its definition by the 898 906 equal "=" character. White space is only significant in that indentation of continuation lines is used to indicate a rule 899 907 definition that spans more than one line. Certain basic rules are in uppercase, such as SP, LWS, HTAB, CRLF, DIGIT, ALPHA, 900 908 etc. Angle brackets are used within definitions whenever their presence will facilitate discerning the use of rule names. 901 </ dd>902 </ dl>909 </li> 910 </ul> 903 911 <p id="rfc.section.2.1.p.3">"literal" </p> 904 < dl class="empty">905 < dd>Quotation marks surround literal text. Unless stated otherwise, the text is case-insensitive.</dd>906 </ dl>912 <ul class="empty"> 913 <li>Quotation marks surround literal text. Unless stated otherwise, the text is case-insensitive.</li> 914 </ul> 907 915 <p id="rfc.section.2.1.p.4">rule1 | rule2 </p> 908 < dl class="empty">909 < dd>Elements separated by a bar ("|") are alternatives, e.g., "yes | no" will accept yes or no.</dd>910 </ dl>916 <ul class="empty"> 917 <li>Elements separated by a bar ("|") are alternatives, e.g., "yes | no" will accept yes or no.</li> 918 </ul> 911 919 <p id="rfc.section.2.1.p.5">(rule1 rule2) </p> 912 < dl class="empty">913 < dd>Elements enclosed in parentheses are treated as a single element. Thus, "(elem (foo | bar) elem)" allows the token sequences920 <ul class="empty"> 921 <li>Elements enclosed in parentheses are treated as a single element. Thus, "(elem (foo | bar) elem)" allows the token sequences 914 922 "elem foo elem" and "elem bar elem". 915 </ dd>916 </ dl>923 </li> 924 </ul> 917 925 <p id="rfc.section.2.1.p.6">*rule </p> 918 < dl class="empty">919 < dd>The character "*" preceding an element indicates repetition. The full form is "<n>*<m>element" indicating at least <n> and926 <ul class="empty"> 927 <li>The character "*" preceding an element indicates repetition. The full form is "<n>*<m>element" indicating at least <n> and 920 928 at most <m> occurrences of element. Default values are 0 and infinity so that "*(element)" allows any number, including zero; 921 929 "1*element" requires at least one; and "1*2element" allows one or two. 922 </ dd>923 </ dl>930 </li> 931 </ul> 924 932 <p id="rfc.section.2.1.p.7">[rule] </p> 925 < dl class="empty">926 < dd>Square brackets enclose optional elements; "[foo bar]" is equivalent to "*1(foo bar)".</dd>927 </ dl>933 <ul class="empty"> 934 <li>Square brackets enclose optional elements; "[foo bar]" is equivalent to "*1(foo bar)".</li> 935 </ul> 928 936 <p id="rfc.section.2.1.p.8">N rule </p> 929 < dl class="empty">930 < dd>Specific repetition: "<n>(element)" is equivalent to "<n>*<n>(element)"; that is, exactly <n> occurrences of (element). Thus937 <ul class="empty"> 938 <li>Specific repetition: "<n>(element)" is equivalent to "<n>*<n>(element)"; that is, exactly <n> occurrences of (element). Thus 931 939 2DIGIT is a 2-digit number, and 3ALPHA is a string of three alphabetic characters. 932 </ dd>933 </ dl>940 </li> 941 </ul> 934 942 <p id="rfc.section.2.1.p.9">#rule </p> 935 < dl class="empty">936 < dd>A construct "#" is defined, similar to "*", for defining lists of elements. The full form is "<n>#<m>element" indicating at943 <ul class="empty"> 944 <li>A construct "#" is defined, similar to "*", for defining lists of elements. The full form is "<n>#<m>element" indicating at 937 945 least <n> and at most <m> elements, each separated by one or more commas (",") and <em class="bcp14">OPTIONAL</em> linear white space (LWS). This makes the usual form of lists very easy; a rule such as 938 <div id="rfc.figure.u.4"></div><pre class="text"> ( *<a href="#rule.LWS" class="smpl">LWS</a> element *( *<a href="#rule.LWS" class="smpl">LWS</a> "," *<a href="#rule.LWS" class="smpl">LWS</a> element ))</pre> </ dd>939 < dd>can be shown as940 <div id="rfc.figure.u.5"></div><pre class="text"> 1#element</pre> </ dd>941 < dd>Wherever this construct is used, null elements are allowed, but do not contribute to the count of elements present. That is,946 <div id="rfc.figure.u.4"></div><pre class="text"> ( *<a href="#rule.LWS" class="smpl">LWS</a> element *( *<a href="#rule.LWS" class="smpl">LWS</a> "," *<a href="#rule.LWS" class="smpl">LWS</a> element ))</pre> </li> 947 <li>can be shown as 948 <div id="rfc.figure.u.5"></div><pre class="text"> 1#element</pre> </li> 949 <li>Wherever this construct is used, null elements are allowed, but do not contribute to the count of elements present. That is, 942 950 "(element), , (element) " is permitted, but counts as only two elements. Therefore, where at least one element is required, 943 951 at least one non-null element <em class="bcp14">MUST</em> be present. Default values are 0 and infinity so that "#element" allows any number, including zero; "1#element" requires at 944 952 least one; and "1#2element" allows one or two. 945 </ dd>946 </ dl>953 </li> 954 </ul> 947 955 <p id="rfc.section.2.1.p.10">; comment </p> 948 < dl class="empty">949 < dd>A semi-colon, set off some distance to the right of rule text, starts a comment that continues to the end of line. This is956 <ul class="empty"> 957 <li>A semi-colon, set off some distance to the right of rule text, starts a comment that continues to the end of line. This is 950 958 a simple way of including useful notes in parallel with the specifications. 951 </ dd>952 </ dl>959 </li> 960 </ul> 953 961 <div id="implied.LWS"> 954 962 <p id="rfc.section.2.1.p.11"> <span id="rfc.iref.i.2"></span> implied *LWS 955 963 </p> 956 < dl class="empty">957 < dd>The grammar described by this specification is word-based. Except where noted otherwise, linear white space (LWS) can be included964 <ul class="empty"> 965 <li>The grammar described by this specification is word-based. Except where noted otherwise, linear white space (LWS) can be included 958 966 between any two adjacent words (token or quoted-string), and between adjacent words and separators, without changing the interpretation 959 967 of a field. At least one delimiter (LWS and/or separators) <em class="bcp14">MUST</em> exist between any two tokens (for the definition of "token" below), since they would otherwise be interpreted as a single 960 968 token. 961 </ dd>962 </ dl>969 </li> 970 </ul> 963 971 </div> 964 972 <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a> <a id="basic.rules" href="#basic.rules">Basic Rules</a></h2> … … 1089 1097 </p> 1090 1098 <p id="rfc.section.3.1.p.9"> </p> 1091 < dl class="empty">1092 < dd> <b>Note:</b> Converting between versions of HTTP may involve modification of header fields required or forbidden by the versions involved.1093 </ dd>1094 </ dl>1099 <ul class="empty"> 1100 <li> <b>Note:</b> Converting between versions of HTTP may involve modification of header fields required or forbidden by the versions involved. 1101 </li> 1102 </ul> 1095 1103 <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="uri" href="#uri">Uniform Resource Identifiers</a></h2> 1096 1104 <p id="rfc.section.3.2.p.1">URIs have been known by many names: WWW addresses, Universal Document Identifiers, Universal Resource Identifiers <a href="#RFC1630" id="rfc.xref.RFC1630.2"><cite title="Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web">[RFC1630]</cite></a>, and finally the combination of Uniform Resource Locators (URL) <a href="#RFC1738" id="rfc.xref.RFC1738.2"><cite title="Uniform Resource Locators (URL)">[RFC1738]</cite></a> and Names (URN) <a href="#RFC1737" id="rfc.xref.RFC1737.2"><cite title="Functional Requirements for Uniform Resource Names">[RFC1737]</cite></a>. As far as HTTP is concerned, Uniform Resource Identifiers are simply formatted strings which identify--via name, location, … … 1114 1122 </p> 1115 1123 <p id="rfc.section.3.2.1.p.4"> </p> 1116 < dl class="empty">1117 < dd> <b>Note:</b> Servers ought to be cautious about depending on URI lengths above 255 bytes, because some older client or proxy implementations1124 <ul class="empty"> 1125 <li> <b>Note:</b> Servers ought to be cautious about depending on URI lengths above 255 bytes, because some older client or proxy implementations 1118 1126 might not properly support these lengths. 1119 </ dd>1120 </ dl>1127 </li> 1128 </ul> 1121 1129 <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a> <a id="http.url" href="#http.url">http URL</a></h3> 1122 1130 <div id="rfc.iref.h.1"></div> … … 1130 1138 listening for TCP connections on that port of that host, and the Request-URI for the resource is path-absolute (<a href="#request-uri" title="Request-URI">Section 5.1.2</a>). The use of IP addresses in URLs <em class="bcp14">SHOULD</em> be avoided whenever possible (see <a href="#RFC1900" id="rfc.xref.RFC1900.1"><cite title="Renumbering Needs Work">[RFC1900]</cite></a>). If the path-absolute is not present in the URL, it <em class="bcp14">MUST</em> be given as "/" when used as a Request-URI for a resource (<a href="#request-uri" title="Request-URI">Section 5.1.2</a>). If a proxy receives a host name which is not a fully qualified domain name, it <em class="bcp14">MAY</em> add its domain to the host name it received. If a proxy receives a fully qualified domain name, the proxy <em class="bcp14">MUST NOT</em> change the host name. 1131 1139 </p> 1132 < dl class="empty">1133 < dd> <span id="rfc.iref.h.2"></span> <span id="rfc.iref.u.4"></span> <b>Note:</b> the "https" scheme is defined in <a href="#RFC2818" id="rfc.xref.RFC2818.1"><cite title="HTTP Over TLS">[RFC2818]</cite></a>.1134 </ dd>1135 </ dl>1140 <ul class="empty"> 1141 <li> <span id="rfc.iref.h.2"></span> <span id="rfc.iref.u.4"></span> <b>Note:</b> the "https" scheme is defined in <a href="#RFC2818" id="rfc.xref.RFC2818.1"><cite title="HTTP Over TLS">[RFC2818]</cite></a>. 1142 </li> 1143 </ul> 1136 1144 <h3 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a> <a id="uri.comparison" href="#uri.comparison">URI Comparison</a></h3> 1137 1145 <p id="rfc.section.3.2.3.p.1">When comparing two URIs to decide if they match or not, a client <em class="bcp14">SHOULD</em> use a case-sensitive octet-by-octet comparison of the entire URIs, with these exceptions: … … 1160 1168 that parse the date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields. See <a href="#tolerant.applications" title="Tolerant Applications">Appendix A</a> for further information. 1161 1169 </p> 1162 < dl class="empty">1163 < dd> <b>Note:</b> Recipients of date values are encouraged to be robust in accepting date values that may have been sent by non-HTTP applications,1170 <ul class="empty"> 1171 <li> <b>Note:</b> Recipients of date values are encouraged to be robust in accepting date values that may have been sent by non-HTTP applications, 1164 1172 as is sometimes the case when retrieving or posting messages via proxies/gateways to SMTP or NNTP. 1165 </ dd>1166 </ dl>1173 </li> 1174 </ul> 1167 1175 <p id="rfc.section.3.3.1.p.5">All HTTP date/time stamps <em class="bcp14">MUST</em> be represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is exactly equal to UTC (Coordinated 1168 1176 Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as the three-letter abbreviation for … … 1371 1379 </p> 1372 1380 <p id="rfc.section.4.2.p.6"> </p> 1373 < dl class="empty">1374 < dd> <b>Note:</b> the "Set-Cookie" header as implemented in practice (as opposed to how it is specified in <a href="#RFC2109" id="rfc.xref.RFC2109.1"><cite title="HTTP State Management Mechanism">[RFC2109]</cite></a>) can occur multiple times, but does not use the list syntax, and thus cannot be combined into a single line. (See Appendix1381 <ul class="empty"> 1382 <li> <b>Note:</b> the "Set-Cookie" header as implemented in practice (as opposed to how it is specified in <a href="#RFC2109" id="rfc.xref.RFC2109.1"><cite title="HTTP State Management Mechanism">[RFC2109]</cite></a>) can occur multiple times, but does not use the list syntax, and thus cannot be combined into a single line. (See Appendix 1375 1383 A.2.3 of <a href="#Kri2001" id="rfc.xref.Kri2001.1"><cite title="HTTP Cookies: Standards, Privacy, and Politics">[Kri2001]</cite></a> for details.) Also note that the Set-Cookie2 header specified in <a href="#RFC2965" id="rfc.xref.RFC2965.1"><cite title="HTTP State Management Mechanism">[RFC2965]</cite></a> does not share this problem. 1376 </ dd>1377 </ dl>1384 </li> 1385 </ul> 1378 1386 <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a> <a id="message.body" href="#message.body">Message Body</a></h2> 1379 1387 <p id="rfc.section.4.3.p.1">The message-body (if any) of an HTTP message is used to carry the entity-body associated with the request or response. The … … 1424 1432 byte-range specifiers from a 1.1 client implies that the client can parse multipart/byteranges responses. 1425 1433 </p> 1426 < dl class="empty">1427 < dd>A range header might be forwarded by a 1.0 proxy that does not understand multipart/byteranges; in this case the server <em class="bcp14">MUST</em> delimit the message using methods defined in items 1, 3 or 5 of this section.1428 </ dd>1429 </ dl>1434 <ul class="empty"> 1435 <li>A range header might be forwarded by a 1.0 proxy that does not understand multipart/byteranges; in this case the server <em class="bcp14">MUST</em> delimit the message using methods defined in items 1, 3 or 5 of this section. 1436 </li> 1437 </ul> 1430 1438 </li> 1431 1439 <li> … … 1517 1525 </p> 1518 1526 <p id="rfc.section.5.1.2.p.14"> </p> 1519 < dl class="empty">1520 < dd> <b>Note:</b> The "no rewrite" rule prevents the proxy from changing the meaning of the request when the origin server is improperly using1527 <ul class="empty"> 1528 <li> <b>Note:</b> The "no rewrite" rule prevents the proxy from changing the meaning of the request when the origin server is improperly using 1521 1529 a non-reserved URI character for a reserved purpose. Implementors should be aware that some pre-HTTP/1.1 proxies have been 1522 1530 known to rewrite the Request-URI. 1523 </ dd>1524 </ dl>1531 </li> 1532 </ul> 1525 1533 <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a> <a id="the.resource.identified.by.a.request" href="#the.resource.identified.by.a.request">The Resource Identified by a Request</a></h2> 1526 1534 <p id="rfc.section.5.2.p.1">The exact resource identified by an Internet request is determined by examining both the Request-URI and the Host header field.</p> … … 2013 2021 <div id="rfc.table.1"> 2014 2022 <div id="iana.header.registration.table"></div> 2015 <table summary="" class="tt full" cellpadding="3" cellspacing="0">2023 <table class="tt full left" cellpadding="3" cellspacing="0"> 2016 2024 <thead> 2017 2025 <tr> … … 2024 2032 <tbody> 2025 2033 <tr> 2026 <td >Connection</td>2027 <td >http</td>2028 <td >standard</td>2029 <td > <a href="#header.connection" id="rfc.xref.header.connection.6" title="Connection">Section 8.1</a>2034 <td class="left">Connection</td> 2035 <td class="left">http</td> 2036 <td class="left">standard</td> 2037 <td class="left"> <a href="#header.connection" id="rfc.xref.header.connection.6" title="Connection">Section 8.1</a> 2030 2038 </td> 2031 2039 </tr> 2032 2040 <tr> 2033 <td >Content-Length</td>2034 <td >http</td>2035 <td >standard</td>2036 <td > <a href="#header.content-length" id="rfc.xref.header.content-length.2" title="Content-Length">Section 8.2</a>2041 <td class="left">Content-Length</td> 2042 <td class="left">http</td> 2043 <td class="left">standard</td> 2044 <td class="left"> <a href="#header.content-length" id="rfc.xref.header.content-length.2" title="Content-Length">Section 8.2</a> 2037 2045 </td> 2038 2046 </tr> 2039 2047 <tr> 2040 <td >Date</td>2041 <td >http</td>2042 <td >standard</td>2043 <td > <a href="#header.date" id="rfc.xref.header.date.2" title="Date">Section 8.3</a>2048 <td class="left">Date</td> 2049 <td class="left">http</td> 2050 <td class="left">standard</td> 2051 <td class="left"> <a href="#header.date" id="rfc.xref.header.date.2" title="Date">Section 8.3</a> 2044 2052 </td> 2045 2053 </tr> 2046 2054 <tr> 2047 <td >Host</td>2048 <td >http</td>2049 <td >standard</td>2050 <td > <a href="#header.host" id="rfc.xref.header.host.1" title="Host">Section 8.4</a>2055 <td class="left">Host</td> 2056 <td class="left">http</td> 2057 <td class="left">standard</td> 2058 <td class="left"> <a href="#header.host" id="rfc.xref.header.host.1" title="Host">Section 8.4</a> 2051 2059 </td> 2052 2060 </tr> 2053 2061 <tr> 2054 <td >TE</td>2055 <td >http</td>2056 <td >standard</td>2057 <td > <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section 8.5</a>2062 <td class="left">TE</td> 2063 <td class="left">http</td> 2064 <td class="left">standard</td> 2065 <td class="left"> <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section 8.5</a> 2058 2066 </td> 2059 2067 </tr> 2060 2068 <tr> 2061 <td >Trailer</td>2062 <td >http</td>2063 <td >standard</td>2064 <td > <a href="#header.trailer" id="rfc.xref.header.trailer.3" title="Trailer">Section 8.6</a>2069 <td class="left">Trailer</td> 2070 <td class="left">http</td> 2071 <td class="left">standard</td> 2072 <td class="left"> <a href="#header.trailer" id="rfc.xref.header.trailer.3" title="Trailer">Section 8.6</a> 2065 2073 </td> 2066 2074 </tr> 2067 2075 <tr> 2068 <td >Transfer-Encoding</td>2069 <td >http</td>2070 <td >standard</td>2071 <td > <a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.5" title="Transfer-Encoding">Section 8.7</a>2076 <td class="left">Transfer-Encoding</td> 2077 <td class="left">http</td> 2078 <td class="left">standard</td> 2079 <td class="left"> <a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.5" title="Transfer-Encoding">Section 8.7</a> 2072 2080 </td> 2073 2081 </tr> 2074 2082 <tr> 2075 <td >Upgrade</td>2076 <td >http</td>2077 <td >standard</td>2078 <td > <a href="#header.upgrade" id="rfc.xref.header.upgrade.2" title="Upgrade">Section 8.8</a>2083 <td class="left">Upgrade</td> 2084 <td class="left">http</td> 2085 <td class="left">standard</td> 2086 <td class="left"> <a href="#header.upgrade" id="rfc.xref.header.upgrade.2" title="Upgrade">Section 8.8</a> 2079 2087 </td> 2080 2088 </tr> 2081 2089 <tr> 2082 <td >Via</td>2083 <td >http</td>2084 <td >standard</td>2085 <td > <a href="#header.via" id="rfc.xref.header.via.2" title="Via">Section 8.9</a>2090 <td class="left">Via</td> 2091 <td class="left">http</td> 2092 <td class="left">standard</td> 2093 <td class="left"> <a href="#header.via" id="rfc.xref.header.via.2" title="Via">Section 8.9</a> 2086 2094 </td> 2087 2095 </tr> … … 2307 2315 <h2 id="rfc.references.1"><a href="#rfc.section.12.1" id="rfc.section.12.1">12.1</a> Normative References 2308 2316 </h2> 2309 <table summary="Normative References">2317 <table> 2310 2318 <tr> 2311 2319 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> 2312 <td class="top">International Organization for Standardization, “ 2313 Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1 2314 ”, ISO/IEC 8859-1:1998, 1998. 2315 </td> 2320 <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> 2316 2321 </tr> 2317 2322 <tr> 2318 2323 <td class="reference"><b id="Part2">[Part2]</b></td> 2319 <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-04">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-04 (work in progress), August 2008.2324 <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-04">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-04 (work in progress), August 2008. 2320 2325 </td> 2321 2326 </tr> 2322 2327 <tr> 2323 2328 <td class="reference"><b id="Part3">[Part3]</b></td> 2324 <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-p3-payload-04">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-04 (work in progress), August 2008.2329 <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-p3-payload-04">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-04 (work in progress), August 2008. 2325 2330 </td> 2326 2331 </tr> 2327 2332 <tr> 2328 2333 <td class="reference"><b id="Part5">[Part5]</b></td> 2329 <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-04">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-04 (work in progress), August 2008.2334 <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-04">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-04 (work in progress), August 2008. 2330 2335 </td> 2331 2336 </tr> 2332 2337 <tr> 2333 2338 <td class="reference"><b id="Part6">[Part6]</b></td> 2334 <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-04">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-04 (work in progress), August 2008.2339 <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-04">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-04 (work in progress), August 2008. 2335 2340 </td> 2336 2341 </tr> 2337 2342 <tr> 2338 2343 <td class="reference"><b id="RFC2045">[RFC2045]</b></td> 2339 <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.2344 <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. 2340 2345 </td> 2341 2346 </tr> 2342 2347 <tr> 2343 2348 <td class="reference"><b id="RFC2047">[RFC2047]</b></td> 2344 <td class="top"><a title="University of Tennessee">Moore, K.</a>, “<a href="http://tools.ietf.org/html/rfc2047">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</a>”, RFC 2047, November 1996.2349 <td class="top"><a href="mailto:moore@cs.utk.edu" title="University of Tennessee">Moore, K.</a>, “<a href="http://tools.ietf.org/html/rfc2047">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</a>”, RFC 2047, November 1996. 2345 2350 </td> 2346 2351 </tr> 2347 2352 <tr> 2348 2353 <td class="reference"><b id="RFC2119">[RFC2119]</b></td> 2349 <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.2354 <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. 2350 2355 </td> 2351 2356 </tr> 2352 2357 <tr> 2353 2358 <td class="reference"><b id="RFC2396">[RFC2396]</b></td> 2354 <td class="top"><a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="Department of Information and Computer Science">Fielding, R.T.</a>, and <atitle="Xerox PARC">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc2396">Uniform Resource Identifiers (URI): Generic Syntax</a>”, RFC 2396, August 1998.2359 <td class="top"><a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:fielding@ics.uci.edu" title="Department of Information and Computer Science">Fielding, R.</a>, and <a href="mailto:masinter@parc.xerox.com" title="Xerox PARC">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc2396">Uniform Resource Identifiers (URI): Generic Syntax</a>”, RFC 2396, August 1998. 2355 2360 </td> 2356 2361 </tr> 2357 2362 <tr> 2358 2363 <td class="reference"><b id="RFC822ABNF">[RFC822ABNF]</b></td> 2359 <td class="top"><a title="University of Delaware, Dept. of Electrical Engineering">Crocker, D.H.</a>, “<a href="http://tools.ietf.org/html/rfc822">Standard for the format of ARPA Internet text messages</a>”, STD 11, RFC 822, August 1982.2364 <td class="top"><a href="mailto:DCrocker@UDel-Relay" title="University of Delaware, Dept. of Electrical Engineering">Crocker, D.</a>, “<a href="http://tools.ietf.org/html/rfc822">Standard for the format of ARPA Internet text messages</a>”, STD 11, RFC 822, August 1982. 2360 2365 </td> 2361 2366 </tr> … … 2367 2372 <h2 id="rfc.references.2"><a href="#rfc.section.12.2" id="rfc.section.12.2">12.2</a> Informative References 2368 2373 </h2> 2369 <table summary="Informative References">2374 <table> 2370 2375 <tr> 2371 2376 <td class="reference"><b id="Kri2001">[Kri2001]</b></td> … … 2375 2380 <tr> 2376 2381 <td class="reference"><b id="Nie1997">[Nie1997]</b></td> 2377 <td class="top">Nielsen, H. F.., Gettys, J., Prud'hommeaux, E., Lie, H., and C. Lilley, “<a href="http://doi.acm.org/10.1145/263105.263157">Network Performance Effects of HTTP/1.1, CSS1, and PNG</a>”, ACM Proceedings of the ACM SIGCOMM '97 conference on Applications, technologies, architectures, and protocols for computer communication2382 <td class="top">Nielsen, H., Gettys, J., Prud'hommeaux, E., Lie, H., and C. Lilley, “<a href="http://doi.acm.org/10.1145/263105.263157">Network Performance Effects of HTTP/1.1, CSS1, and PNG</a>”, ACM Proceedings of the ACM SIGCOMM '97 conference on Applications, technologies, architectures, and protocols for computer communication 2378 2383 SIGCOMM '97, September 1997, <<a href="http://doi.acm.org/10.1145/263105.263157">http://doi.acm.org/10.1145/263105.263157</a>>. 2379 2384 </td> … … 2381 2386 <tr> 2382 2387 <td class="reference"><b id="Pad1995">[Pad1995]</b></td> 2383 <td class="top">Padmanabhan, V. N. and J.C. Mogul, “<a href="http://portal.acm.org/citation.cfm?id=219094">Improving HTTP Latency</a>”, Computer Networks and ISDN Systems v. 28, pp. 25-35, December 1995, <<a href="http://portal.acm.org/citation.cfm?id=219094">http://portal.acm.org/citation.cfm?id=219094</a>>.2388 <td class="top">Padmanabhan, V. and J. Mogul, “<a href="http://portal.acm.org/citation.cfm?id=219094">Improving HTTP Latency</a>”, Computer Networks and ISDN Systems v. 28, pp. 25-35, December 1995, <<a href="http://portal.acm.org/citation.cfm?id=219094">http://portal.acm.org/citation.cfm?id=219094</a>>. 2384 2389 </td> 2385 2390 </tr> 2386 2391 <tr> 2387 2392 <td class="reference"><b id="RFC1123">[RFC1123]</b></td> 2388 <td class="top"><a title="University of Southern California (USC), Information Sciences Institute">Braden, R.</a>, “<a href="http://tools.ietf.org/html/rfc1123">Requirements for Internet Hosts - Application and Support</a>”, STD 3, RFC 1123, October 1989.2393 <td class="top"><a href="mailto:Braden@ISI.EDU" title="University of Southern California (USC), Information Sciences Institute">Braden, R.</a>, “<a href="http://tools.ietf.org/html/rfc1123">Requirements for Internet Hosts - Application and Support</a>”, STD 3, RFC 1123, October 1989. 2389 2394 </td> 2390 2395 </tr> 2391 2396 <tr> 2392 2397 <td class="reference"><b id="RFC1305">[RFC1305]</b></td> 2393 <td class="top"><a title="University of Delaware, Electrical Engineering Department">Mills, D.</a>, “<a href="http://tools.ietf.org/html/rfc1305">Network Time Protocol (Version 3) Specification, Implementation</a>”, RFC 1305, March 1992.2398 <td class="top"><a href="mailto:mills@udel.edu" title="University of Delaware, Electrical Engineering Department">Mills, D.</a>, “<a href="http://tools.ietf.org/html/rfc1305">Network Time Protocol (Version 3) Specification, Implementation</a>”, RFC 1305, March 1992. 2394 2399 </td> 2395 2400 </tr> 2396 2401 <tr> 2397 2402 <td class="reference"><b id="RFC1436">[RFC1436]</b></td> 2398 <td class="top"><a title="University of Minnesota, Computer and Information Services">Anklesaria, F.</a>, <a title="University of Minnesota, Computer and Information Services">McCahill, M.</a>, <a title="University of Minnesota, Computer and Information Services">Lindner, P.</a>, <a title="University of Minnesota, Computer and Information Services">Johnson, D.</a>, <a title="University of Minnesota, Computer and Information Services">Torrey, D.</a>, and <atitle="University of Minnesota, Computer and Information Services">B. Alberti</a>, “<a href="http://tools.ietf.org/html/rfc1436">The Internet Gopher Protocol (a distributed document search and retrieval protocol)</a>”, RFC 1436, March 1993.2403 <td class="top"><a href="mailto:fxa@boombox.micro.umn.edu" title="University of Minnesota, Computer and Information Services">Anklesaria, F.</a>, <a href="mailto:mpm@boombox.micro.umn.edu" title="University of Minnesota, Computer and Information Services">McCahill, M.</a>, <a href="mailto:lindner@boombox.micro.umn.edu" title="University of Minnesota, Computer and Information Services">Lindner, P.</a>, <a href="mailto:dmj@boombox.micro.umn.edu" title="University of Minnesota, Computer and Information Services">Johnson, D.</a>, <a href="mailto:daniel@boombox.micro.umn.edu" title="University of Minnesota, Computer and Information Services">Torrey, D.</a>, and <a href="mailto:alberti@boombox.micro.umn.edu" title="University of Minnesota, Computer and Information Services">B. Alberti</a>, “<a href="http://tools.ietf.org/html/rfc1436">The Internet Gopher Protocol (a distributed document search and retrieval protocol)</a>”, RFC 1436, March 1993. 2399 2404 </td> 2400 2405 </tr> 2401 2406 <tr> 2402 2407 <td class="reference"><b id="RFC1630">[RFC1630]</b></td> 2403 <td class="top"><a title="CERN, World-Wide Web project">Berners-Lee, T.</a>, “<a href="http://tools.ietf.org/html/rfc1630">Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network2408 <td class="top"><a href="mailto:timbl@info.cern.ch" title="CERN, World-Wide Web project">Berners-Lee, T.</a>, “<a href="http://tools.ietf.org/html/rfc1630">Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network 2404 2409 as used in the World-Wide Web</a>”, RFC 1630, June 1994. 2405 2410 </td> … … 2407 2412 <tr> 2408 2413 <td class="reference"><b id="RFC1737">[RFC1737]</b></td> 2409 <td class="top"><a title="Xerox Palo Alto Research Center">Masinter, L.</a> and <atitle="MIT Laboratory for Computer Science">K. Sollins</a>, “<a href="http://tools.ietf.org/html/rfc1737">Functional Requirements for Uniform Resource Names</a>”, RFC 1737, December 1994.2414 <td class="top"><a href="mailto:masinter@parc.xerox.com" title="Xerox Palo Alto Research Center">Masinter, L.</a> and <a href="mailto:sollins@lcs.mit.edu" title="MIT Laboratory for Computer Science">K. Sollins</a>, “<a href="http://tools.ietf.org/html/rfc1737">Functional Requirements for Uniform Resource Names</a>”, RFC 1737, December 1994. 2410 2415 </td> 2411 2416 </tr> 2412 2417 <tr> 2413 2418 <td class="reference"><b id="RFC1738">[RFC1738]</b></td> 2414 <td class="top"><a title="CERN, World-Wide Web project">Berners-Lee, T.</a>, <a title="Xerox PARC">Masinter, L.</a>, and <atitle="University of Minnesota, Computer and Information Services">M. McCahill</a>, “<a href="http://tools.ietf.org/html/rfc1738">Uniform Resource Locators (URL)</a>”, RFC 1738, December 1994.2419 <td class="top"><a href="mailto:timbl@info.cern.ch" title="CERN, World-Wide Web project">Berners-Lee, T.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox PARC">Masinter, L.</a>, and <a href="mailto:mpm@boombox.micro.umn.edu" title="University of Minnesota, Computer and Information Services">M. McCahill</a>, “<a href="http://tools.ietf.org/html/rfc1738">Uniform Resource Locators (URL)</a>”, RFC 1738, December 1994. 2415 2420 </td> 2416 2421 </tr> 2417 2422 <tr> 2418 2423 <td class="reference"><b id="RFC1808">[RFC1808]</b></td> 2419 <td class="top"><a title="University of California Irvine, Department of Information and Computer Science">Fielding, R.</a>, “<a href="http://tools.ietf.org/html/rfc1808">Relative Uniform Resource Locators</a>”, RFC 1808, June 1995.2424 <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="http://tools.ietf.org/html/rfc1808">Relative Uniform Resource Locators</a>”, RFC 1808, June 1995. 2420 2425 </td> 2421 2426 </tr> 2422 2427 <tr> 2423 2428 <td class="reference"><b id="RFC1900">[RFC1900]</b></td> 2424 <td class="top"><a title="CERN, Computing and Networks Division">Carpenter, B.</a> and <atitle="cisco Systems">Y. Rekhter</a>, “<a href="http://tools.ietf.org/html/rfc1900">Renumbering Needs Work</a>”, RFC 1900, February 1996.2429 <td class="top"><a href="mailto:brian@dxcoms.cern.ch" title="CERN, Computing and Networks Division">Carpenter, B.</a> and <a href="mailto:yakov@cisco.com" title="cisco Systems">Y. Rekhter</a>, “<a href="http://tools.ietf.org/html/rfc1900">Renumbering Needs Work</a>”, RFC 1900, February 1996. 2425 2430 </td> 2426 2431 </tr> 2427 2432 <tr> 2428 2433 <td class="reference"><b id="RFC1945">[RFC1945]</b></td> 2429 <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.2434 <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. 2430 2435 </td> 2431 2436 </tr> 2432 2437 <tr> 2433 2438 <td class="reference"><b id="RFC2068">[RFC2068]</b></td> 2434 <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.2439 <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. 2435 2440 </td> 2436 2441 </tr> 2437 2442 <tr> 2438 2443 <td class="reference"><b id="RFC2109">[RFC2109]</b></td> 2439 <td class="top"><a title="Bell Laboratories, Lucent Technologies">Kristol, D.M.</a> and <atitle="Netscape Communications Corp.">L. Montulli</a>, “<a href="http://tools.ietf.org/html/rfc2109">HTTP State Management Mechanism</a>”, RFC 2109, February 1997.2444 <td class="top"><a href="mailto:dmk@bell-labs.com" title="Bell Laboratories, Lucent Technologies">Kristol, D.</a> and <a href="mailto:montulli@netscape.com" title="Netscape Communications Corp.">L. Montulli</a>, “<a href="http://tools.ietf.org/html/rfc2109">HTTP State Management Mechanism</a>”, RFC 2109, February 1997. 2440 2445 </td> 2441 2446 </tr> 2442 2447 <tr> 2443 2448 <td class="reference"><b id="RFC2145">[RFC2145]</b></td> 2444 <td class="top"><a title="Western Research Laboratory">Mogul, J.C.</a>, <a title="Department of Information and Computer Science">Fielding, R.T.</a>, <a title="MIT Laboratory for Computer Science">Gettys, J.</a>, and <a title="W3 Consortium">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc2145">Use and Interpretation of HTTP Version Numbers</a>”, RFC 2145, May 1997.2449 <td class="top"><a href="mailto:mogul@wrl.dec.com" title="Western Research Laboratory">Mogul, J.</a>, <a href="mailto:fielding@ics.uci.edu" title="Department of Information and Computer Science">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="MIT Laboratory for Computer Science">Gettys, J.</a>, and <a href="mailto:frystyk@w3.org" title="W3 Consortium">H. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc2145">Use and Interpretation of HTTP Version Numbers</a>”, RFC 2145, May 1997. 2445 2450 </td> 2446 2451 </tr> 2447 2452 <tr> 2448 2453 <td class="reference"><b id="RFC2324">[RFC2324]</b></td> 2449 <td class="top"><a title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="http://tools.ietf.org/html/rfc2324">Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)</a>”, RFC 2324, April 1998.2454 <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/rfc2324">Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)</a>”, RFC 2324, April 1998. 2450 2455 </td> 2451 2456 </tr> 2452 2457 <tr> 2453 2458 <td class="reference"><b id="RFC2616">[RFC2616]</b></td> 2454 <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.2459 <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. 2455 2460 </td> 2456 2461 </tr> 2457 2462 <tr> 2458 2463 <td class="reference"><b id="RFC2818">[RFC2818]</b></td> 2459 <td class="top"><a title="RTFM, Inc.">Rescorla, E.</a>, “<a href="http://tools.ietf.org/html/rfc2818">HTTP Over TLS</a>”, RFC 2818, May 2000.2464 <td class="top"><a href="mailto:ekr@rtfm.com" title="RTFM, Inc.">Rescorla, E.</a>, “<a href="http://tools.ietf.org/html/rfc2818">HTTP Over TLS</a>”, RFC 2818, May 2000. 2460 2465 </td> 2461 2466 </tr> 2462 2467 <tr> 2463 2468 <td class="reference"><b id="RFC2821">[RFC2821]</b></td> 2464 <td class="top"><a title="AT&T Laboratories">Klensin, J.</a>, “<a href="http://tools.ietf.org/html/rfc2821">Simple Mail Transfer Protocol</a>”, RFC 2821, April 2001.2469 <td class="top"><a href="mailto:klensin@research.att.com" title="AT&T Laboratories">Klensin, J.</a>, “<a href="http://tools.ietf.org/html/rfc2821">Simple Mail Transfer Protocol</a>”, RFC 2821, April 2001. 2465 2470 </td> 2466 2471 </tr> … … 2472 2477 <tr> 2473 2478 <td class="reference"><b id="RFC2965">[RFC2965]</b></td> 2474 <td class="top"><a title="Bell Laboratories, Lucent Technologies">Kristol, D. M.</a> and <atitle="Epinions.com, Inc.">L. Montulli</a>, “<a href="http://tools.ietf.org/html/rfc2965">HTTP State Management Mechanism</a>”, RFC 2965, October 2000.2479 <td class="top"><a href="mailto:dmk@bell-labs.com" title="Bell Laboratories, Lucent Technologies">Kristol, D.</a> and <a href="mailto:lou@montulli.org" title="Epinions.com, Inc.">L. Montulli</a>, “<a href="http://tools.ietf.org/html/rfc2965">HTTP State Management Mechanism</a>”, RFC 2965, October 2000. 2475 2480 </td> 2476 2481 </tr> 2477 2482 <tr> 2478 2483 <td class="reference"><b id="RFC3864">[RFC3864]</b></td> 2479 <td class="top"><a title="Nine by Nine">Klyne, G.</a>, <a title="BEA Systems">Nottingham, M.</a>, and <atitle="HP Labs">J. Mogul</a>, “<a href="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP 90, RFC 3864, September 2004.2484 <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP 90, RFC 3864, September 2004. 2480 2485 </td> 2481 2486 </tr> 2482 2487 <tr> 2483 2488 <td class="reference"><b id="RFC3977">[RFC3977]</b></td> 2484 <td class="top"><a title="THUS plc">Feather, C.</a>, “<a href="http://tools.ietf.org/html/rfc3977">Network News Transfer Protocol (NNTP)</a>”, RFC 3977, October 2006.2489 <td class="top"><a href="mailto:clive@demon.net" title="THUS plc">Feather, C.</a>, “<a href="http://tools.ietf.org/html/rfc3977">Network News Transfer Protocol (NNTP)</a>”, RFC 3977, October 2006. 2485 2490 </td> 2486 2491 </tr> 2487 2492 <tr> 2488 2493 <td class="reference"><b id="RFC4288">[RFC4288]</b></td> 2489 <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.2494 <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. 2490 2495 </td> 2491 2496 </tr> 2492 2497 <tr> 2493 2498 <td class="reference"><b id="RFC4395">[RFC4395]</b></td> 2494 <td class="top"><a title="AT&T Laboratories">Hansen, T.</a>, <a title="Qualcomm, Inc.">Hardie, T.</a>, and <atitle="Adobe Systems">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc4395">Guidelines and Registration Procedures for New URI Schemes</a>”, BCP 115, RFC 4395, February 2006.2499 <td class="top"><a href="mailto:tony+urireg@maillennium.att.com" title="AT&T Laboratories">Hansen, T.</a>, <a href="mailto:hardie@qualcomm.com" title="Qualcomm, Inc.">Hardie, T.</a>, and <a href="mailto:LMM@acm.org" title="Adobe Systems">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc4395">Guidelines and Registration Procedures for New URI Schemes</a>”, BCP 115, RFC 4395, February 2006. 2495 2500 </td> 2496 2501 </tr> 2497 2502 <tr> 2498 2503 <td class="reference"><b id="RFC822">[RFC822]</b></td> 2499 <td class="top"><a title="University of Delaware, Dept. of Electrical Engineering">Crocker, D.H.</a>, “<a href="http://tools.ietf.org/html/rfc822">Standard for the format of ARPA Internet text messages</a>”, STD 11, RFC 822, August 1982.2504 <td class="top"><a href="mailto:DCrocker@UDel-Relay" title="University of Delaware, Dept. of Electrical Engineering">Crocker, D.</a>, “<a href="http://tools.ietf.org/html/rfc822">Standard for the format of ARPA Internet text messages</a>”, STD 11, RFC 822, August 1982. 2500 2505 </td> 2501 2506 </tr> … … 2512 2517 <tr> 2513 2518 <td class="reference"><b id="Tou1998">[Tou1998]</b></td> 2514 <td class="top"><a title="USC/Information Sciences Institute">Touch, J.</a>, <a title="USC/Information Sciences Institute">Heidemann, J.</a>, and <atitle="USC/Information Sciences Institute">K. Obraczka</a>, “<a href="http://www.isi.edu/touch/pubs/http-perf96/">Analysis of HTTP Performance</a>”, ISI Research Report ISI/RR-98-463, Aug 1998, <<a href="http://www.isi.edu/touch/pubs/http-perf96/">http://www.isi.edu/touch/pubs/http-perf96/</a>>.<br>(original report dated Aug. 1996)2519 <td class="top"><a href="mailto:touch@isi.edu" title="USC/Information Sciences Institute">Touch, J.</a>, <a href="mailto:johnh@isi.edu" title="USC/Information Sciences Institute">Heidemann, J.</a>, and <a href="mailto:katia@isi.edu" title="USC/Information Sciences Institute">K. Obraczka</a>, “<a href="http://www.isi.edu/touch/pubs/http-perf96/">Analysis of HTTP Performance</a>”, ISI Research Report ISI/RR-98-463, Aug 1998, <<a href="http://www.isi.edu/touch/pubs/http-perf96/">http://www.isi.edu/touch/pubs/http-perf96/</a>>.<br>(original report dated Aug. 1996) 2515 2520 </td> 2516 2521 </tr> … … 2520 2525 </tr> 2521 2526 </table> 2522 <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1> 2523 <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span> 2524 (editor) 2525 <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> 2526 <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> 2527 <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> 2528 <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> 2529 <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> 2530 <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> 2531 <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> 2532 <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span> 2533 (editor) 2534 <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> 2535 <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span> 2536 (editor) 2537 <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> 2538 <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a> <a id="tolerant.applications" href="#tolerant.applications">Tolerant Applications</a></h1> 2527 <div class="avoidbreak"> 2528 <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1> 2529 <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span> 2530 (editor) 2531 <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> 2532 <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> 2533 <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> 2534 <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> 2535 <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> 2536 <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> 2537 <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> 2538 <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span> 2539 (editor) 2540 <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> 2541 <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span> 2542 (editor) 2543 <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> 2544 </div> 2545 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="tolerant.applications" href="#tolerant.applications">Tolerant Applications</a></h1> 2539 2546 <p id="rfc.section.A.p.1">Although this document specifies the requirements for the generation of HTTP/1.1 messages, not all applications will be correct 2540 2547 in their implementation. We therefore recommend that operational applications be tolerant of deviations whenever those deviations … … 2777 2784 <li>Replace HEX by HEXDIG for future consistence with RFC 5234's core rules.</li> 2778 2785 </ul> 2786 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 2787 <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.E">E</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.K">K</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a> <a href="#rfc.index.W">W</a> 2788 </p> 2789 <div class="print2col"> 2790 <ul class="ind"> 2791 <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul> 2792 <li>application/http Media Type <a href="#rfc.iref.a.1"><b>9.3.2</b></a></li> 2793 </ul> 2794 </li> 2795 <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul> 2796 <li>cache <a href="#rfc.iref.c.4">1.3</a></li> 2797 <li>cacheable <a href="#rfc.iref.c.5">1.3</a></li> 2798 <li>client <a href="#rfc.iref.c.3">1.3</a></li> 2799 <li>connection <a href="#rfc.iref.c.1">1.3</a></li> 2800 <li>Connection header <a href="#rfc.xref.header.connection.1">4.5</a>, <a href="#rfc.xref.header.connection.2">7.1.2</a>, <a href="#rfc.xref.header.connection.3">7.1.3</a>, <a href="#rfc.iref.c.6"><b>8.1</b></a>, <a href="#rfc.xref.header.connection.4">8.5</a>, <a href="#rfc.xref.header.connection.5">8.8</a>, <a href="#rfc.xref.header.connection.6">9.1</a>, <a href="#rfc.xref.header.connection.7">C.2</a>, <a href="#rfc.xref.header.connection.8">C.4</a></li> 2801 <li>content negotiation <a href="#rfc.iref.c.2">1.3</a></li> 2802 <li>Content-Length header <a href="#rfc.xref.header.content-length.1">4.4</a>, <a href="#rfc.iref.c.7"><b>8.2</b></a>, <a href="#rfc.xref.header.content-length.2">9.1</a>, <a href="#rfc.xref.header.content-length.3">C.3</a></li> 2803 </ul> 2804 </li> 2805 <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul> 2806 <li>Date header <a href="#rfc.xref.header.date.1">4.5</a>, <a href="#rfc.iref.d.2"><b>8.3</b></a>, <a href="#rfc.xref.header.date.2">9.1</a></li> 2807 <li>downstream <a href="#rfc.iref.d.1">1.3</a></li> 2808 </ul> 2809 </li> 2810 <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul> 2811 <li>entity <a href="#rfc.iref.e.1">1.3</a></li> 2812 </ul> 2813 </li> 2814 <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul> 2815 <li>gateway <a href="#rfc.iref.g.1">1.3</a></li> 2816 <li><tt>Grammar</tt> 2817 <ul> 2818 <li><tt>absoluteURI</tt> <a href="#rfc.iref.g.27"><b>3.2.1</b></a></li> 2819 <li><tt>ALPHA</tt> <a href="#rfc.iref.g.4"><b>2.2</b></a></li> 2820 <li><tt>asctime-date</tt> <a href="#rfc.iref.g.39"><b>3.3.1</b></a></li> 2821 <li><tt>attribute</tt> <a href="#rfc.iref.g.50"><b>3.4</b></a></li> 2822 <li><tt>authority</tt> <a href="#rfc.iref.g.28"><b>3.2.1</b></a></li> 2823 <li><tt>CHAR</tt> <a href="#rfc.iref.g.3"><b>2.2</b></a></li> 2824 <li><tt>chunk</tt> <a href="#rfc.iref.g.53"><b>3.4.1</b></a></li> 2825 <li><tt>chunk-data</tt> <a href="#rfc.iref.g.59"><b>3.4.1</b></a></li> 2826 <li><tt>chunk-ext-name</tt> <a href="#rfc.iref.g.57"><b>3.4.1</b></a></li> 2827 <li><tt>chunk-ext-val</tt> <a href="#rfc.iref.g.58"><b>3.4.1</b></a></li> 2828 <li><tt>chunk-extension</tt> <a href="#rfc.iref.g.56"><b>3.4.1</b></a></li> 2829 <li><tt>chunk-size</tt> <a href="#rfc.iref.g.54"><b>3.4.1</b></a></li> 2830 <li><tt>Chunked-Body</tt> <a href="#rfc.iref.g.52"><b>3.4.1</b></a></li> 2831 <li><tt>comment</tt> <a href="#rfc.iref.g.19"><b>2.2</b></a></li> 2832 <li><tt>Connection</tt> <a href="#rfc.iref.g.82"><b>8.1</b></a></li> 2833 <li><tt>connection-token</tt> <a href="#rfc.iref.g.83"><b>8.1</b></a></li> 2834 <li><tt>Content-Length</tt> <a href="#rfc.iref.g.84"><b>8.2</b></a></li> 2835 <li><tt>CR</tt> <a href="#rfc.iref.g.7"><b>2.2</b></a></li> 2836 <li><tt>CRLF</tt> <a href="#rfc.iref.g.12"><b>2.2</b></a></li> 2837 <li><tt>ctext</tt> <a href="#rfc.iref.g.20"><b>2.2</b></a></li> 2838 <li><tt>CTL</tt> <a href="#rfc.iref.g.6"><b>2.2</b></a></li> 2839 <li><tt>Date</tt> <a href="#rfc.iref.g.85"><b>8.3</b></a></li> 2840 <li><tt>date1</tt> <a href="#rfc.iref.g.40"><b>3.3.1</b></a></li> 2841 <li><tt>date2</tt> <a href="#rfc.iref.g.41"><b>3.3.1</b></a></li> 2842 <li><tt>date3</tt> <a href="#rfc.iref.g.42"><b>3.3.1</b></a></li> 2843 <li><tt>DIGIT</tt> <a href="#rfc.iref.g.5"><b>2.2</b></a></li> 2844 <li><tt>DQUOTE</tt> <a href="#rfc.iref.g.11"><b>2.2</b></a></li> 2845 <li><tt>extension-code</tt> <a href="#rfc.iref.g.80"><b>6.1.1</b></a></li> 2846 <li><tt>extension-method</tt> <a href="#rfc.iref.g.75"><b>5.1.1</b></a></li> 2847 <li><tt>field-content</tt> <a href="#rfc.iref.g.69"><b>4.2</b></a></li> 2848 <li><tt>field-name</tt> <a href="#rfc.iref.g.67"><b>4.2</b></a></li> 2849 <li><tt>field-value</tt> <a href="#rfc.iref.g.68"><b>4.2</b></a></li> 2850 <li><tt>general-header</tt> <a href="#rfc.iref.g.71"><b>4.5</b></a></li> 2851 <li><tt>generic-message</tt> <a href="#rfc.iref.g.64"><b>4.1</b></a></li> 2852 <li><tt>HEXDIG</tt> <a href="#rfc.iref.g.15"><b>2.2</b></a></li> 2853 <li><tt>Host</tt> <a href="#rfc.iref.g.86"><b>8.4</b></a></li> 2854 <li><tt>HTAB</tt> <a href="#rfc.iref.g.10"><b>2.2</b></a></li> 2855 <li><tt>HTTP-date</tt> <a href="#rfc.iref.g.35"><b>3.3.1</b></a></li> 2856 <li><tt>HTTP-message</tt> <a href="#rfc.iref.g.63"><b>4.1</b></a></li> 2857 <li><tt>HTTP-Prot-Name</tt> <a href="#rfc.iref.g.26"><b>3.1</b></a></li> 2858 <li><tt>http-URL</tt> <a href="#rfc.iref.g.34"><b>3.2.2</b></a></li> 2859 <li><tt>HTTP-Version</tt> <a href="#rfc.iref.g.25"><b>3.1</b></a></li> 2860 <li><tt>last-chunk</tt> <a href="#rfc.iref.g.55"><b>3.4.1</b></a></li> 2861 <li><tt>LF</tt> <a href="#rfc.iref.g.8"><b>2.2</b></a></li> 2862 <li><tt>LWS</tt> <a href="#rfc.iref.g.13"><b>2.2</b></a></li> 2863 <li><tt>message-body</tt> <a href="#rfc.iref.g.70"><b>4.3</b></a></li> 2864 <li><tt>message-header</tt> <a href="#rfc.iref.g.66"><b>4.2</b></a></li> 2865 <li><tt>Method</tt> <a href="#rfc.iref.g.74"><b>5.1.1</b></a></li> 2866 <li><tt>month</tt> <a href="#rfc.iref.g.46"><b>3.3.1</b></a></li> 2867 <li><tt>obsolete-date</tt> <a href="#rfc.iref.g.37"><b>3.3.1</b></a></li> 2868 <li><tt>OCTET</tt> <a href="#rfc.iref.g.2"><b>2.2</b></a></li> 2869 <li><tt>parameter</tt> <a href="#rfc.iref.g.49"><b>3.4</b></a></li> 2870 <li><tt>path-absolute</tt> <a href="#rfc.iref.g.29"><b>3.2.1</b></a></li> 2871 <li><tt>port</tt> <a href="#rfc.iref.g.30"><b>3.2.1</b></a></li> 2872 <li><tt>product</tt> <a href="#rfc.iref.g.61"><b>3.5</b></a></li> 2873 <li><tt>product-version</tt> <a href="#rfc.iref.g.62"><b>3.5</b></a></li> 2874 <li><tt>protocol-name</tt> <a href="#rfc.iref.g.94"><b>8.9</b></a></li> 2875 <li><tt>protocol-version</tt> <a href="#rfc.iref.g.95"><b>8.9</b></a></li> 2876 <li><tt>pseudonym</tt> <a href="#rfc.iref.g.97"><b>8.9</b></a></li> 2877 <li><tt>qdtext</tt> <a href="#rfc.iref.g.22"><b>2.2</b></a></li> 2878 <li><tt>query</tt> <a href="#rfc.iref.g.31"><b>3.2.1</b></a></li> 2879 <li><tt>quoted-pair</tt> <a href="#rfc.iref.g.24"><b>2.2</b></a></li> 2880 <li><tt>quoted-string</tt> <a href="#rfc.iref.g.21"><b>2.2</b></a></li> 2881 <li><tt>quoted-text</tt> <a href="#rfc.iref.g.23"><b>2.2</b></a></li> 2882 <li><tt>Reason-Phrase</tt> <a href="#rfc.iref.g.81"><b>6.1.1</b></a></li> 2883 <li><tt>received-by</tt> <a href="#rfc.iref.g.96"><b>8.9</b></a></li> 2884 <li><tt>received-protocol</tt> <a href="#rfc.iref.g.93"><b>8.9</b></a></li> 2885 <li><tt>relativeURI</tt> <a href="#rfc.iref.g.32"><b>3.2.1</b></a></li> 2886 <li><tt>Request</tt> <a href="#rfc.iref.g.72"><b>5</b></a></li> 2887 <li><tt>Request-Line</tt> <a href="#rfc.iref.g.73"><b>5.1</b></a></li> 2888 <li><tt>Request-URI</tt> <a href="#rfc.iref.g.76"><b>5.1.2</b></a></li> 2889 <li><tt>Response</tt> <a href="#rfc.iref.g.77"><b>6</b></a></li> 2890 <li><tt>rfc1123-date</tt> <a href="#rfc.iref.g.36"><b>3.3.1</b></a></li> 2891 <li><tt>rfc850-date</tt> <a href="#rfc.iref.g.38"><b>3.3.1</b></a></li> 2892 <li><tt>separators</tt> <a href="#rfc.iref.g.18"><b>2.2</b></a></li> 2893 <li><tt>SP</tt> <a href="#rfc.iref.g.9"><b>2.2</b></a></li> 2894 <li><tt>start-line</tt> <a href="#rfc.iref.g.65"><b>4.1</b></a></li> 2895 <li><tt>Status-Code</tt> <a href="#rfc.iref.g.79"><b>6.1.1</b></a></li> 2896 <li><tt>Status-Line</tt> <a href="#rfc.iref.g.78"><b>6.1</b></a></li> 2897 <li><tt>t-codings</tt> <a href="#rfc.iref.g.88"><b>8.5</b></a></li> 2898 <li><tt>tchar</tt> <a href="#rfc.iref.g.17"><b>2.2</b></a></li> 2899 <li><tt>TE</tt> <a href="#rfc.iref.g.87"><b>8.5</b></a></li> 2900 <li><tt>TEXT</tt> <a href="#rfc.iref.g.14"><b>2.2</b></a></li> 2901 <li><tt>time</tt> <a href="#rfc.iref.g.43"><b>3.3.1</b></a></li> 2902 <li><tt>token</tt> <a href="#rfc.iref.g.16"><b>2.2</b></a></li> 2903 <li><tt>Trailer</tt> <a href="#rfc.iref.g.89"><b>8.6</b></a></li> 2904 <li><tt>trailer-part</tt> <a href="#rfc.iref.g.60"><b>3.4.1</b></a></li> 2905 <li><tt>transfer-coding</tt> <a href="#rfc.iref.g.47"><b>3.4</b></a></li> 2906 <li><tt>Transfer-Encoding</tt> <a href="#rfc.iref.g.90"><b>8.7</b></a></li> 2907 <li><tt>transfer-extension</tt> <a href="#rfc.iref.g.48"><b>3.4</b></a></li> 2908 <li><tt>Upgrade</tt> <a href="#rfc.iref.g.91"><b>8.8</b></a></li> 2909 <li><tt>uri-host</tt> <a href="#rfc.iref.g.33"><b>3.2.1</b></a></li> 2910 <li><tt>value</tt> <a href="#rfc.iref.g.51"><b>3.4</b></a></li> 2911 <li><tt>Via</tt> <a href="#rfc.iref.g.92"><b>8.9</b></a></li> 2912 <li><tt>weekday</tt> <a href="#rfc.iref.g.45"><b>3.3.1</b></a></li> 2913 <li><tt>wkday</tt> <a href="#rfc.iref.g.44"><b>3.3.1</b></a></li> 2914 </ul> 2915 </li> 2916 </ul> 2917 </li> 2918 <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul> 2919 <li>Headers 2920 <ul> 2921 <li>Connection <a href="#rfc.xref.header.connection.1">4.5</a>, <a href="#rfc.xref.header.connection.2">7.1.2</a>, <a href="#rfc.xref.header.connection.3">7.1.3</a>, <a href="#rfc.iref.h.3"><b>8.1</b></a>, <a href="#rfc.xref.header.connection.4">8.5</a>, <a href="#rfc.xref.header.connection.5">8.8</a>, <a href="#rfc.xref.header.connection.6">9.1</a>, <a href="#rfc.xref.header.connection.7">C.2</a>, <a href="#rfc.xref.header.connection.8">C.4</a></li> 2922 <li>Content-Length <a href="#rfc.xref.header.content-length.1">4.4</a>, <a href="#rfc.iref.h.4"><b>8.2</b></a>, <a href="#rfc.xref.header.content-length.2">9.1</a>, <a href="#rfc.xref.header.content-length.3">C.3</a></li> 2923 <li>Date <a href="#rfc.xref.header.date.1">4.5</a>, <a href="#rfc.iref.h.5"><b>8.3</b></a>, <a href="#rfc.xref.header.date.2">9.1</a></li> 2924 <li>Host <a href="#rfc.iref.h.7"><b>8.4</b></a>, <a href="#rfc.xref.header.host.1">9.1</a>, <a href="#rfc.xref.header.host.2">C.1.1</a></li> 2925 <li>TE <a href="#rfc.xref.header.te.1">3.4</a>, <a href="#rfc.xref.header.te.2">3.4.1</a>, <a href="#rfc.iref.h.8"><b>8.5</b></a>, <a href="#rfc.xref.header.te.3">9.1</a>, <a href="#rfc.xref.header.te.4">C.3</a></li> 2926 <li>Trailer <a href="#rfc.xref.header.trailer.1">3.4.1</a>, <a href="#rfc.xref.header.trailer.2">4.5</a>, <a href="#rfc.iref.h.9"><b>8.6</b></a>, <a href="#rfc.xref.header.trailer.3">9.1</a></li> 2927 <li>Transfer-Encoding <a href="#rfc.xref.header.transfer-encoding.1">3.4</a>, <a href="#rfc.xref.header.transfer-encoding.2">4.3</a>, <a href="#rfc.xref.header.transfer-encoding.3">4.4</a>, <a href="#rfc.xref.header.transfer-encoding.4">4.5</a>, <a href="#rfc.iref.h.10"><b>8.7</b></a>, <a href="#rfc.xref.header.transfer-encoding.5">9.1</a></li> 2928 <li>Upgrade <a href="#rfc.xref.header.upgrade.1">4.5</a>, <a href="#rfc.iref.h.11"><b>8.8</b></a>, <a href="#rfc.xref.header.upgrade.2">9.1</a></li> 2929 <li>Via <a href="#rfc.xref.header.via.1">4.5</a>, <a href="#rfc.iref.h.12"><b>8.9</b></a>, <a href="#rfc.xref.header.via.2">9.1</a></li> 2930 </ul> 2931 </li> 2932 <li>Host header <a href="#rfc.iref.h.6"><b>8.4</b></a>, <a href="#rfc.xref.header.host.1">9.1</a>, <a href="#rfc.xref.header.host.2">C.1.1</a></li> 2933 <li>http URI scheme <a href="#rfc.iref.h.1"><b>3.2.2</b></a></li> 2934 <li>https URI scheme <a href="#rfc.iref.h.2">3.2.2</a></li> 2935 </ul> 2936 </li> 2937 <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul> 2938 <li>implied *LWS <a href="#rfc.iref.i.2"><b>2.1</b></a></li> 2939 <li>inbound <a href="#rfc.iref.i.1">1.3</a></li> 2940 <li><em>ISO-8859-1</em> <a href="#rfc.xref.ISO-8859-1.1">2.2</a>, <a href="#ISO-8859-1"><b>12.1</b></a></li> 2941 </ul> 2942 </li> 2943 <li><a id="rfc.index.K" href="#rfc.index.K"><b>K</b></a><ul> 2944 <li><em>Kri2001</em> <a href="#rfc.xref.Kri2001.1">4.2</a>, <a href="#Kri2001"><b>12.2</b></a></li> 2945 </ul> 2946 </li> 2947 <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul> 2948 <li>Media Type 2949 <ul> 2950 <li>application/http <a href="#rfc.iref.m.4"><b>9.3.2</b></a></li> 2951 <li>message/http <a href="#rfc.iref.m.2"><b>9.3.1</b></a></li> 2952 </ul> 2953 </li> 2954 <li>message <a href="#rfc.iref.m.1">1.3</a></li> 2955 <li>message/http Media Type <a href="#rfc.iref.m.3"><b>9.3.1</b></a></li> 2956 </ul> 2957 </li> 2958 <li><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul> 2959 <li><em>Nie1997</em> <a href="#rfc.xref.Nie1997.1">7.1.1</a>, <a href="#Nie1997"><b>12.2</b></a>, <a href="#rfc.xref.Nie1997.2">C.3</a></li> 2960 </ul> 2961 </li> 2962 <li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul> 2963 <li>origin server <a href="#rfc.iref.o.1">1.3</a></li> 2964 <li>outbound <a href="#rfc.iref.o.2">1.3</a></li> 2965 </ul> 2966 </li> 2967 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 2968 <li><em>Pad1995</em> <a href="#rfc.xref.Pad1995.1">7.1.1</a>, <a href="#Pad1995"><b>12.2</b></a></li> 2969 <li><em>Part2</em> <a href="#rfc.xref.Part2.1">2.3</a>, <a href="#rfc.xref.Part2.2">2.3</a>, <a href="#rfc.xref.Part2.3">3.2.1</a>, <a href="#rfc.xref.Part2.4">4.2</a>, <a href="#rfc.xref.Part2.5">4.2</a>, <a href="#rfc.xref.Part2.6">4.3</a>, <a href="#rfc.xref.Part2.7">5</a>, <a href="#rfc.xref.Part2.8">5.1.2</a>, <a href="#rfc.xref.Part2.9">6</a>, <a href="#rfc.xref.Part2.10">6.1.1</a>, <a href="#rfc.xref.Part2.11">7.1.2.2</a>, <a href="#rfc.xref.Part2.12">7.1.4</a>, <a href="#rfc.xref.Part2.13">7.2.3</a>, <a href="#rfc.xref.Part2.14">7.2.3</a>, <a href="#rfc.xref.Part2.15">7.2.3</a>, <a href="#rfc.xref.Part2.16">7.2.3</a>, <a href="#Part2"><b>12.1</b></a><ul> 2970 <li><em>Section 3</em> <a href="#rfc.xref.Part2.6">4.3</a></li> 2971 <li><em>Section 4</em> <a href="#rfc.xref.Part2.1">2.3</a>, <a href="#rfc.xref.Part2.4">4.2</a>, <a href="#rfc.xref.Part2.7">5</a></li> 2972 <li><em>Section 6</em> <a href="#rfc.xref.Part2.2">2.3</a>, <a href="#rfc.xref.Part2.5">4.2</a>, <a href="#rfc.xref.Part2.9">6</a></li> 2973 <li><em>Section 8.1.2</em> <a href="#rfc.xref.Part2.11">7.1.2.2</a>, <a href="#rfc.xref.Part2.12">7.1.4</a></li> 2974 <li><em>Section 8.9</em> <a href="#rfc.xref.Part2.8">5.1.2</a></li> 2975 <li><em>Section 9</em> <a href="#rfc.xref.Part2.10">6.1.1</a></li> 2976 <li><em>Section 9.1.1</em> <a href="#rfc.xref.Part2.13">7.2.3</a></li> 2977 <li><em>Section 9.1</em> <a href="#rfc.xref.Part2.16">7.2.3</a></li> 2978 <li><em>Section 9.4.15</em> <a href="#rfc.xref.Part2.3">3.2.1</a></li> 2979 <li><em>Section 10.2</em> <a href="#rfc.xref.Part2.14">7.2.3</a>, <a href="#rfc.xref.Part2.15">7.2.3</a></li> 2980 </ul> 2981 </li> 2982 <li><em>Part3</em> <a href="#rfc.xref.Part3.1">1.3</a>, <a href="#rfc.xref.Part3.2">1.3</a>, <a href="#rfc.xref.Part3.3">1.3</a>, <a href="#rfc.xref.Part3.4">1.4</a>, <a href="#rfc.xref.Part3.5">2.2</a>, <a href="#rfc.xref.Part3.6">2.3</a>, <a href="#rfc.xref.Part3.7">2.3</a>, <a href="#rfc.xref.Part3.8">2.3</a>, <a href="#rfc.xref.Part3.9">3.4</a>, <a href="#rfc.xref.Part3.10">3.4</a>, <a href="#rfc.xref.Part3.11">4.2</a>, <a href="#rfc.xref.Part3.12">5</a>, <a href="#rfc.xref.Part3.13">6</a>, <a href="#rfc.xref.Part3.14">8.5</a>, <a href="#Part3"><b>12.1</b></a>, <a href="#rfc.xref.Part3.15">A</a>, <a href="#rfc.xref.Part3.16">C.3</a><ul> 2983 <li><em>Section 3.2</em> <a href="#rfc.xref.Part3.9">3.4</a>, <a href="#rfc.xref.Part3.10">3.4</a></li> 2984 <li><em>Section 3.3</em> <a href="#rfc.xref.Part3.5">2.2</a></li> 2985 <li><em>Section 3.4</em> <a href="#rfc.xref.Part3.14">8.5</a></li> 2986 <li><em>Section 4</em> <a href="#rfc.xref.Part3.1">1.3</a></li> 2987 <li><em>Section 4.1</em> <a href="#rfc.xref.Part3.8">2.3</a>, <a href="#rfc.xref.Part3.11">4.2</a>, <a href="#rfc.xref.Part3.12">5</a>, <a href="#rfc.xref.Part3.13">6</a></li> 2988 <li><em>Section 4.2</em> <a href="#rfc.xref.Part3.7">2.3</a></li> 2989 <li><em>Section 5</em> <a href="#rfc.xref.Part3.2">1.3</a>, <a href="#rfc.xref.Part3.3">1.3</a></li> 2990 <li><em>Section 6.1</em> <a href="#rfc.xref.Part3.6">2.3</a></li> 2991 <li><em>Appendix A</em> <a href="#rfc.xref.Part3.4">1.4</a></li> 2992 </ul> 2993 </li> 2994 <li><em>Part5</em> <a href="#Part5"><b>12.1</b></a>, <a href="#rfc.xref.Part5.1">C.3</a></li> 2995 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">1.3</a>, <a href="#rfc.xref.Part6.2">1.4</a>, <a href="#rfc.xref.Part6.3">2.3</a>, <a href="#rfc.xref.Part6.4">2.3</a>, <a href="#rfc.xref.Part6.5">2.3</a>, <a href="#rfc.xref.Part6.6">4.5</a>, <a href="#rfc.xref.Part6.7">4.5</a>, <a href="#rfc.xref.Part6.8">4.5</a>, <a href="#Part6"><b>12.1</b></a>, <a href="#rfc.xref.Part6.9">C.3</a><ul> 2996 <li><em>Section 1</em> <a href="#rfc.xref.Part6.1">1.3</a>, <a href="#rfc.xref.Part6.2">1.4</a></li> 2997 <li><em>Section 16.2</em> <a href="#rfc.xref.Part6.6">4.5</a></li> 2998 <li><em>Section 16.4</em> <a href="#rfc.xref.Part6.3">2.3</a>, <a href="#rfc.xref.Part6.4">2.3</a>, <a href="#rfc.xref.Part6.7">4.5</a></li> 2999 <li><em>Section 16.6</em> <a href="#rfc.xref.Part6.5">2.3</a>, <a href="#rfc.xref.Part6.8">4.5</a></li> 3000 </ul> 3001 </li> 3002 <li>proxy <a href="#rfc.iref.p.1">1.3</a></li> 3003 </ul> 3004 </li> 3005 <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul> 3006 <li>representation <a href="#rfc.iref.r.4">1.3</a></li> 3007 <li>request <a href="#rfc.iref.r.1">1.3</a></li> 3008 <li>resource <a href="#rfc.iref.r.3">1.3</a></li> 3009 <li>response <a href="#rfc.iref.r.2">1.3</a></li> 3010 <li><em>RFC1123</em> <a href="#rfc.xref.RFC1123.1">3.3.1</a>, <a href="#RFC1123"><b>12.2</b></a></li> 3011 <li><em>RFC1305</em> <a href="#rfc.xref.RFC1305.1">8.3</a>, <a href="#RFC1305"><b>12.2</b></a></li> 3012 <li><em>RFC1436</em> <a href="#rfc.xref.RFC1436.1">1.1</a>, <a href="#RFC1436"><b>12.2</b></a></li> 3013 <li><em>RFC1630</em> <a href="#rfc.xref.RFC1630.1">1.1</a>, <a href="#rfc.xref.RFC1630.2">3.2</a>, <a href="#RFC1630"><b>12.2</b></a></li> 3014 <li><em>RFC1737</em> <a href="#rfc.xref.RFC1737.1">1.1</a>, <a href="#rfc.xref.RFC1737.2">3.2</a>, <a href="#RFC1737"><b>12.2</b></a></li> 3015 <li><em>RFC1738</em> <a href="#rfc.xref.RFC1738.1">1.1</a>, <a href="#rfc.xref.RFC1738.2">3.2</a>, <a href="#rfc.xref.RFC1738.3">3.2.1</a>, <a href="#RFC1738"><b>12.2</b></a></li> 3016 <li><em>RFC1808</em> <a href="#rfc.xref.RFC1808.1">3.2.1</a>, <a href="#rfc.xref.RFC1808.2">3.2.1</a>, <a href="#RFC1808"><b>12.2</b></a></li> 3017 <li><em>RFC1900</em> <a href="#rfc.xref.RFC1900.1">3.2.2</a>, <a href="#rfc.xref.RFC1900.2">10.4</a>, <a href="#RFC1900"><b>12.2</b></a></li> 3018 <li><em>RFC1945</em> <a href="#rfc.xref.RFC1945.1">1</a>, <a href="#RFC1945"><b>12.2</b></a></li> 3019 <li><em>RFC2045</em> <a href="#rfc.xref.RFC2045.1">1.1</a>, <a href="#rfc.xref.RFC2045.2">3.4</a>, <a href="#rfc.xref.RFC2045.3">11</a>, <a href="#RFC2045"><b>12.1</b></a></li> 3020 <li><em>RFC2047</em> <a href="#rfc.xref.RFC2047.1">2.2</a>, <a href="#RFC2047"><b>12.1</b></a></li> 3021 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">3.1</a>, <a href="#rfc.xref.RFC2068.2">7.1.1</a>, <a href="#rfc.xref.RFC2068.3">7.1.3</a>, <a href="#rfc.xref.RFC2068.4">7.2.3</a>, <a href="#rfc.xref.RFC2068.5">11</a>, <a href="#RFC2068"><b>12.2</b></a>, <a href="#rfc.xref.RFC2068.6">C</a>, <a href="#rfc.xref.RFC2068.7">C.2</a><ul> 3022 <li><em>Section 19.7.1</em> <a href="#rfc.xref.RFC2068.6">C</a></li> 3023 </ul> 3024 </li> 3025 <li><em>RFC2109</em> <a href="#rfc.xref.RFC2109.1">4.2</a>, <a href="#RFC2109"><b>12.2</b></a></li> 3026 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.2</a>, <a href="#RFC2119"><b>12.1</b></a>, <a href="#rfc.xref.RFC2119.2">C.3</a></li> 3027 <li><em>RFC2145</em> <a href="#rfc.xref.RFC2145.1">3.1</a>, <a href="#rfc.xref.RFC2145.2">3.1</a>, <a href="#RFC2145"><b>12.2</b></a>, <a href="#rfc.xref.RFC2145.3">C.3</a></li> 3028 <li><em>RFC2324</em> <a href="#rfc.xref.RFC2324.1">1.1</a>, <a href="#RFC2324"><b>12.2</b></a></li> 3029 <li><em>RFC2396</em> <a href="#rfc.xref.RFC2396.1">3.2.1</a>, <a href="#rfc.xref.RFC2396.2">3.2.1</a>, <a href="#rfc.xref.RFC2396.3">3.2.1</a>, <a href="#rfc.xref.RFC2396.4">3.2.1</a>, <a href="#rfc.xref.RFC2396.5">3.2.1</a>, <a href="#rfc.xref.RFC2396.6">3.2.1</a>, <a href="#rfc.xref.RFC2396.7">3.2.1</a>, <a href="#rfc.xref.RFC2396.8">3.2.1</a>, <a href="#rfc.xref.RFC2396.9">3.2.1</a>, <a href="#rfc.xref.RFC2396.10">3.2.3</a>, <a href="#rfc.xref.RFC2396.11">5.1.2</a>, <a href="#RFC2396"><b>12.1</b></a>, <a href="#rfc.xref.RFC2396.12">C.4</a><ul> 3030 <li><em>Section 2.2</em> <a href="#rfc.xref.RFC2396.10">3.2.3</a></li> 3031 <li><em>Section 2.4.1</em> <a href="#rfc.xref.RFC2396.11">5.1.2</a></li> 3032 <li><em>Section 3</em> <a href="#rfc.xref.RFC2396.2">3.2.1</a>, <a href="#rfc.xref.RFC2396.5">3.2.1</a>, <a href="#rfc.xref.RFC2396.12">C.4</a></li> 3033 <li><em>Section 3.2</em> <a href="#rfc.xref.RFC2396.3">3.2.1</a></li> 3034 <li><em>Section 3.2.2</em> <a href="#rfc.xref.RFC2396.6">3.2.1</a>, <a href="#rfc.xref.RFC2396.9">3.2.1</a></li> 3035 <li><em>Section 3.4</em> <a href="#rfc.xref.RFC2396.7">3.2.1</a></li> 3036 <li><em>Section 4.1</em> <a href="#rfc.xref.RFC2396.4">3.2.1</a></li> 3037 <li><em>Section 5</em> <a href="#rfc.xref.RFC2396.8">3.2.1</a></li> 3038 </ul> 3039 </li> 3040 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">1</a>, <a href="#rfc.xref.RFC2616.3">11</a>, <a href="#RFC2616"><b>12.2</b></a>, <a href="#rfc.xref.RFC2616.4">D.1</a></li> 3041 <li><em>RFC2818</em> <a href="#rfc.xref.RFC2818.1">3.2.2</a>, <a href="#RFC2818"><b>12.2</b></a></li> 3042 <li><em>RFC2821</em> <a href="#rfc.xref.RFC2821.1">1.1</a>, <a href="#RFC2821"><b>12.2</b></a></li> 3043 <li><em>RFC2822</em> <a href="#rfc.xref.RFC2822.1">1.1</a>, <a href="#rfc.xref.RFC2822.2">4.1</a>, <a href="#rfc.xref.RFC2822.3">4.2</a>, <a href="#rfc.xref.RFC2822.4">8.3</a>, <a href="#rfc.xref.RFC2822.5">8.9</a>, <a href="#RFC2822"><b>12.2</b></a><ul> 3044 <li><em>Section 2.1</em> <a href="#rfc.xref.RFC2822.3">4.2</a></li> 3045 <li><em>Section 3.6.1</em> <a href="#rfc.xref.RFC2822.4">8.3</a></li> 3046 <li><em>Section 3.6.7</em> <a href="#rfc.xref.RFC2822.5">8.9</a></li> 3047 </ul> 3048 </li> 3049 <li><em>RFC2965</em> <a href="#rfc.xref.RFC2965.1">4.2</a>, <a href="#RFC2965"><b>12.2</b></a></li> 3050 <li><em>RFC3864</em> <a href="#rfc.xref.RFC3864.1">9.1</a>, <a href="#RFC3864"><b>12.2</b></a></li> 3051 <li><em>RFC3977</em> <a href="#rfc.xref.RFC3977.1">1.1</a>, <a href="#RFC3977"><b>12.2</b></a></li> 3052 <li><em>RFC4288</em> <a href="#rfc.xref.RFC4288.1">9.3</a>, <a href="#RFC4288"><b>12.2</b></a></li> 3053 <li><em>RFC4395</em> <a href="#rfc.xref.RFC4395.1">9.2</a>, <a href="#RFC4395"><b>12.2</b></a></li> 3054 <li><em>RFC822</em> <a href="#rfc.xref.RFC822.1">3.3.1</a>, <a href="#RFC822"><b>12.2</b></a></li> 3055 <li><em>RFC822ABNF</em> <a href="#rfc.xref.RFC822ABNF.1">2.1</a>, <a href="#rfc.xref.RFC822ABNF.2">11</a>, <a href="#RFC822ABNF"><b>12.1</b></a></li> 3056 <li><em>RFC959</em> <a href="#rfc.xref.RFC959.1">1.1</a>, <a href="#RFC959"><b>12.2</b></a></li> 3057 </ul> 3058 </li> 3059 <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul> 3060 <li>server <a href="#rfc.iref.s.1">1.3</a></li> 3061 <li><em>Spe</em> <a href="#rfc.xref.Spe.1">7.1.1</a>, <a href="#Spe"><b>12.2</b></a></li> 3062 </ul> 3063 </li> 3064 <li><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul> 3065 <li>TE header <a href="#rfc.xref.header.te.1">3.4</a>, <a href="#rfc.xref.header.te.2">3.4.1</a>, <a href="#rfc.iref.t.2"><b>8.5</b></a>, <a href="#rfc.xref.header.te.3">9.1</a>, <a href="#rfc.xref.header.te.4">C.3</a></li> 3066 <li><em>Tou1998</em> <a href="#rfc.xref.Tou1998.1">7.1.1</a>, <a href="#Tou1998"><b>12.2</b></a></li> 3067 <li>Trailer header <a href="#rfc.xref.header.trailer.1">3.4.1</a>, <a href="#rfc.xref.header.trailer.2">4.5</a>, <a href="#rfc.iref.t.3"><b>8.6</b></a>, <a href="#rfc.xref.header.trailer.3">9.1</a></li> 3068 <li>Transfer-Encoding header <a href="#rfc.xref.header.transfer-encoding.1">3.4</a>, <a href="#rfc.xref.header.transfer-encoding.2">4.3</a>, <a href="#rfc.xref.header.transfer-encoding.3">4.4</a>, <a href="#rfc.xref.header.transfer-encoding.4">4.5</a>, <a href="#rfc.iref.t.4"><b>8.7</b></a>, <a href="#rfc.xref.header.transfer-encoding.5">9.1</a></li> 3069 <li>tunnel <a href="#rfc.iref.t.1">1.3</a></li> 3070 </ul> 3071 </li> 3072 <li><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul> 3073 <li>Upgrade header <a href="#rfc.xref.header.upgrade.1">4.5</a>, <a href="#rfc.iref.u.5"><b>8.8</b></a>, <a href="#rfc.xref.header.upgrade.2">9.1</a></li> 3074 <li>upstream <a href="#rfc.iref.u.2">1.3</a></li> 3075 <li>URI scheme 3076 <ul> 3077 <li>http <a href="#rfc.iref.u.3"><b>3.2.2</b></a></li> 3078 <li>https <a href="#rfc.iref.u.4">3.2.2</a></li> 3079 </ul> 3080 </li> 3081 <li><em>USASCII</em> <a href="#rfc.xref.USASCII.1">2.2</a>, <a href="#USASCII"><b>12.1</b></a></li> 3082 <li>user agent <a href="#rfc.iref.u.1">1.3</a></li> 3083 </ul> 3084 </li> 3085 <li><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul> 3086 <li>variant <a href="#rfc.iref.v.1">1.3</a></li> 3087 <li>Via header <a href="#rfc.xref.header.via.1">4.5</a>, <a href="#rfc.iref.v.2"><b>8.9</b></a>, <a href="#rfc.xref.header.via.2">9.1</a></li> 3088 </ul> 3089 </li> 3090 <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul> 3091 <li><em>WAIS</em> <a href="#rfc.xref.WAIS.1">1.1</a>, <a href="#WAIS"><b>12.2</b></a></li> 3092 </ul> 3093 </li> 3094 </ul> 3095 </div> 2779 3096 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> 3097 <p>Copyright © The IETF Trust (2008).</p> 2780 3098 <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the 2781 3099 authors retain all their rights. … … 2795 3113 <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result 2796 3114 of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users 2797 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>>.3115 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>. 2798 3116 </p> 2799 3117 <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary … … 2801 3119 at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>. 2802 3120 </p> 2803 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>2804 <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.E">E</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.K">K</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a> <a href="#rfc.index.W">W</a>2805 </p>2806 <div class="print2col">2807 <ul class="ind">2808 <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind">2809 <li class="indline1">application/http Media Type <a class="iref" href="#rfc.iref.a.1"><b>9.3.2</b></a></li>2810 </ul>2811 </li>2812 <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">2813 <li class="indline1">cache <a class="iref" href="#rfc.iref.c.4">1.3</a></li>2814 <li class="indline1">cacheable <a class="iref" href="#rfc.iref.c.5">1.3</a></li>2815 <li class="indline1">client <a class="iref" href="#rfc.iref.c.3">1.3</a></li>2816 <li class="indline1">connection <a class="iref" href="#rfc.iref.c.1">1.3</a></li>2817 <li class="indline1">Connection header <a class="iref" href="#rfc.xref.header.connection.1">4.5</a>, <a class="iref" href="#rfc.xref.header.connection.2">7.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">7.1.3</a>, <a class="iref" href="#rfc.iref.c.6"><b>8.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.4">8.5</a>, <a class="iref" href="#rfc.xref.header.connection.5">8.8</a>, <a class="iref" href="#rfc.xref.header.connection.6">9.1</a>, <a class="iref" href="#rfc.xref.header.connection.7">C.2</a>, <a class="iref" href="#rfc.xref.header.connection.8">C.4</a></li>2818 <li class="indline1">content negotiation <a class="iref" href="#rfc.iref.c.2">1.3</a></li>2819 <li class="indline1">Content-Length header <a class="iref" href="#rfc.xref.header.content-length.1">4.4</a>, <a class="iref" href="#rfc.iref.c.7"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">9.1</a>, <a class="iref" href="#rfc.xref.header.content-length.3">C.3</a></li>2820 </ul>2821 </li>2822 <li class="indline0"><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul class="ind">2823 <li class="indline1">Date header <a class="iref" href="#rfc.xref.header.date.1">4.5</a>, <a class="iref" href="#rfc.iref.d.2"><b>8.3</b></a>, <a class="iref" href="#rfc.xref.header.date.2">9.1</a></li>2824 <li class="indline1">downstream <a class="iref" href="#rfc.iref.d.1">1.3</a></li>2825 </ul>2826 </li>2827 <li class="indline0"><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul class="ind">2828 <li class="indline1">entity <a class="iref" href="#rfc.iref.e.1">1.3</a></li>2829 </ul>2830 </li>2831 <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind">2832 <li class="indline1">gateway <a class="iref" href="#rfc.iref.g.1">1.3</a></li>2833 <li class="indline1"><tt>Grammar</tt> 2834 <ul class="ind">2835 <li class="indline1"><tt>absoluteURI</tt> <a class="iref" href="#rfc.iref.g.27"><b>3.2.1</b></a></li>2836 <li class="indline1"><tt>ALPHA</tt> <a class="iref" href="#rfc.iref.g.4"><b>2.2</b></a></li>2837 <li class="indline1"><tt>asctime-date</tt> <a class="iref" href="#rfc.iref.g.39"><b>3.3.1</b></a></li>2838 <li class="indline1"><tt>attribute</tt> <a class="iref" href="#rfc.iref.g.50"><b>3.4</b></a></li>2839 <li class="indline1"><tt>authority</tt> <a class="iref" href="#rfc.iref.g.28"><b>3.2.1</b></a></li>2840 <li class="indline1"><tt>CHAR</tt> <a class="iref" href="#rfc.iref.g.3"><b>2.2</b></a></li>2841 <li class="indline1"><tt>chunk</tt> <a class="iref" href="#rfc.iref.g.53"><b>3.4.1</b></a></li>2842 <li class="indline1"><tt>chunk-data</tt> <a class="iref" href="#rfc.iref.g.59"><b>3.4.1</b></a></li>2843 <li class="indline1"><tt>chunk-ext-name</tt> <a class="iref" href="#rfc.iref.g.57"><b>3.4.1</b></a></li>2844 <li class="indline1"><tt>chunk-ext-val</tt> <a class="iref" href="#rfc.iref.g.58"><b>3.4.1</b></a></li>2845 <li class="indline1"><tt>chunk-extension</tt> <a class="iref" href="#rfc.iref.g.56"><b>3.4.1</b></a></li>2846 <li class="indline1"><tt>chunk-size</tt> <a class="iref" href="#rfc.iref.g.54"><b>3.4.1</b></a></li>2847 <li class="indline1"><tt>Chunked-Body</tt> <a class="iref" href="#rfc.iref.g.52"><b>3.4.1</b></a></li>2848 <li class="indline1"><tt>comment</tt> <a class="iref" href="#rfc.iref.g.19"><b>2.2</b></a></li>2849 <li class="indline1"><tt>Connection</tt> <a class="iref" href="#rfc.iref.g.82"><b>8.1</b></a></li>2850 <li class="indline1"><tt>connection-token</tt> <a class="iref" href="#rfc.iref.g.83"><b>8.1</b></a></li>2851 <li class="indline1"><tt>Content-Length</tt> <a class="iref" href="#rfc.iref.g.84"><b>8.2</b></a></li>2852 <li class="indline1"><tt>CR</tt> <a class="iref" href="#rfc.iref.g.7"><b>2.2</b></a></li>2853 <li class="indline1"><tt>CRLF</tt> <a class="iref" href="#rfc.iref.g.12"><b>2.2</b></a></li>2854 <li class="indline1"><tt>ctext</tt> <a class="iref" href="#rfc.iref.g.20"><b>2.2</b></a></li>2855 <li class="indline1"><tt>CTL</tt> <a class="iref" href="#rfc.iref.g.6"><b>2.2</b></a></li>2856 <li class="indline1"><tt>Date</tt> <a class="iref" href="#rfc.iref.g.85"><b>8.3</b></a></li>2857 <li class="indline1"><tt>date1</tt> <a class="iref" href="#rfc.iref.g.40"><b>3.3.1</b></a></li>2858 <li class="indline1"><tt>date2</tt> <a class="iref" href="#rfc.iref.g.41"><b>3.3.1</b></a></li>2859 <li class="indline1"><tt>date3</tt> <a class="iref" href="#rfc.iref.g.42"><b>3.3.1</b></a></li>2860 <li class="indline1"><tt>DIGIT</tt> <a class="iref" href="#rfc.iref.g.5"><b>2.2</b></a></li>2861 <li class="indline1"><tt>DQUOTE</tt> <a class="iref" href="#rfc.iref.g.11"><b>2.2</b></a></li>2862 <li class="indline1"><tt>extension-code</tt> <a class="iref" href="#rfc.iref.g.80"><b>6.1.1</b></a></li>2863 <li class="indline1"><tt>extension-method</tt> <a class="iref" href="#rfc.iref.g.75"><b>5.1.1</b></a></li>2864 <li class="indline1"><tt>field-content</tt> <a class="iref" href="#rfc.iref.g.69"><b>4.2</b></a></li>2865 <li class="indline1"><tt>field-name</tt> <a class="iref" href="#rfc.iref.g.67"><b>4.2</b></a></li>2866 <li class="indline1"><tt>field-value</tt> <a class="iref" href="#rfc.iref.g.68"><b>4.2</b></a></li>2867 <li class="indline1"><tt>general-header</tt> <a class="iref" href="#rfc.iref.g.71"><b>4.5</b></a></li>2868 <li class="indline1"><tt>generic-message</tt> <a class="iref" href="#rfc.iref.g.64"><b>4.1</b></a></li>2869 <li class="indline1"><tt>HEXDIG</tt> <a class="iref" href="#rfc.iref.g.15"><b>2.2</b></a></li>2870 <li class="indline1"><tt>Host</tt> <a class="iref" href="#rfc.iref.g.86"><b>8.4</b></a></li>2871 <li class="indline1"><tt>HTAB</tt> <a class="iref" href="#rfc.iref.g.10"><b>2.2</b></a></li>2872 <li class="indline1"><tt>HTTP-date</tt> <a class="iref" href="#rfc.iref.g.35"><b>3.3.1</b></a></li>2873 <li class="indline1"><tt>HTTP-message</tt> <a class="iref" href="#rfc.iref.g.63"><b>4.1</b></a></li>2874 <li class="indline1"><tt>HTTP-Prot-Name</tt> <a class="iref" href="#rfc.iref.g.26"><b>3.1</b></a></li>2875 <li class="indline1"><tt>http-URL</tt> <a class="iref" href="#rfc.iref.g.34"><b>3.2.2</b></a></li>2876 <li class="indline1"><tt>HTTP-Version</tt> <a class="iref" href="#rfc.iref.g.25"><b>3.1</b></a></li>2877 <li class="indline1"><tt>last-chunk</tt> <a class="iref" href="#rfc.iref.g.55"><b>3.4.1</b></a></li>2878 <li class="indline1"><tt>LF</tt> <a class="iref" href="#rfc.iref.g.8"><b>2.2</b></a></li>2879 <li class="indline1"><tt>LWS</tt> <a class="iref" href="#rfc.iref.g.13"><b>2.2</b></a></li>2880 <li class="indline1"><tt>message-body</tt> <a class="iref" href="#rfc.iref.g.70"><b>4.3</b></a></li>2881 <li class="indline1"><tt>message-header</tt> <a class="iref" href="#rfc.iref.g.66"><b>4.2</b></a></li>2882 <li class="indline1"><tt>Method</tt> <a class="iref" href="#rfc.iref.g.74"><b>5.1.1</b></a></li>2883 <li class="indline1"><tt>month</tt> <a class="iref" href="#rfc.iref.g.46"><b>3.3.1</b></a></li>2884 <li class="indline1"><tt>obsolete-date</tt> <a class="iref" href="#rfc.iref.g.37"><b>3.3.1</b></a></li>2885 <li class="indline1"><tt>OCTET</tt> <a class="iref" href="#rfc.iref.g.2"><b>2.2</b></a></li>2886 <li class="indline1"><tt>parameter</tt> <a class="iref" href="#rfc.iref.g.49"><b>3.4</b></a></li>2887 <li class="indline1"><tt>path-absolute</tt> <a class="iref" href="#rfc.iref.g.29"><b>3.2.1</b></a></li>2888 <li class="indline1"><tt>port</tt> <a class="iref" href="#rfc.iref.g.30"><b>3.2.1</b></a></li>2889 <li class="indline1"><tt>product</tt> <a class="iref" href="#rfc.iref.g.61"><b>3.5</b></a></li>2890 <li class="indline1"><tt>product-version</tt> <a class="iref" href="#rfc.iref.g.62"><b>3.5</b></a></li>2891 <li class="indline1"><tt>protocol-name</tt> <a class="iref" href="#rfc.iref.g.94"><b>8.9</b></a></li>2892 <li class="indline1"><tt>protocol-version</tt> <a class="iref" href="#rfc.iref.g.95"><b>8.9</b></a></li>2893 <li class="indline1"><tt>pseudonym</tt> <a class="iref" href="#rfc.iref.g.97"><b>8.9</b></a></li>2894 <li class="indline1"><tt>qdtext</tt> <a class="iref" href="#rfc.iref.g.22"><b>2.2</b></a></li>2895 <li class="indline1"><tt>query</tt> <a class="iref" href="#rfc.iref.g.31"><b>3.2.1</b></a></li>2896 <li class="indline1"><tt>quoted-pair</tt> <a class="iref" href="#rfc.iref.g.24"><b>2.2</b></a></li>2897 <li class="indline1"><tt>quoted-string</tt> <a class="iref" href="#rfc.iref.g.21"><b>2.2</b></a></li>2898 <li class="indline1"><tt>quoted-text</tt> <a class="iref" href="#rfc.iref.g.23"><b>2.2</b></a></li>2899 <li class="indline1"><tt>Reason-Phrase</tt> <a class="iref" href="#rfc.iref.g.81"><b>6.1.1</b></a></li>2900 <li class="indline1"><tt>received-by</tt> <a class="iref" href="#rfc.iref.g.96"><b>8.9</b></a></li>2901 <li class="indline1"><tt>received-protocol</tt> <a class="iref" href="#rfc.iref.g.93"><b>8.9</b></a></li>2902 <li class="indline1"><tt>relativeURI</tt> <a class="iref" href="#rfc.iref.g.32"><b>3.2.1</b></a></li>2903 <li class="indline1"><tt>Request</tt> <a class="iref" href="#rfc.iref.g.72"><b>5</b></a></li>2904 <li class="indline1"><tt>Request-Line</tt> <a class="iref" href="#rfc.iref.g.73"><b>5.1</b></a></li>2905 <li class="indline1"><tt>Request-URI</tt> <a class="iref" href="#rfc.iref.g.76"><b>5.1.2</b></a></li>2906 <li class="indline1"><tt>Response</tt> <a class="iref" href="#rfc.iref.g.77"><b>6</b></a></li>2907 <li class="indline1"><tt>rfc1123-date</tt> <a class="iref" href="#rfc.iref.g.36"><b>3.3.1</b></a></li>2908 <li class="indline1"><tt>rfc850-date</tt> <a class="iref" href="#rfc.iref.g.38"><b>3.3.1</b></a></li>2909 <li class="indline1"><tt>separators</tt> <a class="iref" href="#rfc.iref.g.18"><b>2.2</b></a></li>2910 <li class="indline1"><tt>SP</tt> <a class="iref" href="#rfc.iref.g.9"><b>2.2</b></a></li>2911 <li class="indline1"><tt>start-line</tt> <a class="iref" href="#rfc.iref.g.65"><b>4.1</b></a></li>2912 <li class="indline1"><tt>Status-Code</tt> <a class="iref" href="#rfc.iref.g.79"><b>6.1.1</b></a></li>2913 <li class="indline1"><tt>Status-Line</tt> <a class="iref" href="#rfc.iref.g.78"><b>6.1</b></a></li>2914 <li class="indline1"><tt>t-codings</tt> <a class="iref" href="#rfc.iref.g.88"><b>8.5</b></a></li>2915 <li class="indline1"><tt>tchar</tt> <a class="iref" href="#rfc.iref.g.17"><b>2.2</b></a></li>2916 <li class="indline1"><tt>TE</tt> <a class="iref" href="#rfc.iref.g.87"><b>8.5</b></a></li>2917 <li class="indline1"><tt>TEXT</tt> <a class="iref" href="#rfc.iref.g.14"><b>2.2</b></a></li>2918 <li class="indline1"><tt>time</tt> <a class="iref" href="#rfc.iref.g.43"><b>3.3.1</b></a></li>2919 <li class="indline1"><tt>token</tt> <a class="iref" href="#rfc.iref.g.16"><b>2.2</b></a></li>2920 <li class="indline1"><tt>Trailer</tt> <a class="iref" href="#rfc.iref.g.89"><b>8.6</b></a></li>2921 <li class="indline1"><tt>trailer-part</tt> <a class="iref" href="#rfc.iref.g.60"><b>3.4.1</b></a></li>2922 <li class="indline1"><tt>transfer-coding</tt> <a class="iref" href="#rfc.iref.g.47"><b>3.4</b></a></li>2923 <li class="indline1"><tt>Transfer-Encoding</tt> <a class="iref" href="#rfc.iref.g.90"><b>8.7</b></a></li>2924 <li class="indline1"><tt>transfer-extension</tt> <a class="iref" href="#rfc.iref.g.48"><b>3.4</b></a></li>2925 <li class="indline1"><tt>Upgrade</tt> <a class="iref" href="#rfc.iref.g.91"><b>8.8</b></a></li>2926 <li class="indline1"><tt>uri-host</tt> <a class="iref" href="#rfc.iref.g.33"><b>3.2.1</b></a></li>2927 <li class="indline1"><tt>value</tt> <a class="iref" href="#rfc.iref.g.51"><b>3.4</b></a></li>2928 <li class="indline1"><tt>Via</tt> <a class="iref" href="#rfc.iref.g.92"><b>8.9</b></a></li>2929 <li class="indline1"><tt>weekday</tt> <a class="iref" href="#rfc.iref.g.45"><b>3.3.1</b></a></li>2930 <li class="indline1"><tt>wkday</tt> <a class="iref" href="#rfc.iref.g.44"><b>3.3.1</b></a></li>2931 </ul>2932 </li>2933 </ul>2934 </li>2935 <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">2936 <li class="indline1">Headers 2937 <ul class="ind">2938 <li class="indline1">Connection <a class="iref" href="#rfc.xref.header.connection.1">4.5</a>, <a class="iref" href="#rfc.xref.header.connection.2">7.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">7.1.3</a>, <a class="iref" href="#rfc.iref.h.3"><b>8.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.4">8.5</a>, <a class="iref" href="#rfc.xref.header.connection.5">8.8</a>, <a class="iref" href="#rfc.xref.header.connection.6">9.1</a>, <a class="iref" href="#rfc.xref.header.connection.7">C.2</a>, <a class="iref" href="#rfc.xref.header.connection.8">C.4</a></li>2939 <li class="indline1">Content-Length <a class="iref" href="#rfc.xref.header.content-length.1">4.4</a>, <a class="iref" href="#rfc.iref.h.4"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">9.1</a>, <a class="iref" href="#rfc.xref.header.content-length.3">C.3</a></li>2940 <li class="indline1">Date <a class="iref" href="#rfc.xref.header.date.1">4.5</a>, <a class="iref" href="#rfc.iref.h.5"><b>8.3</b></a>, <a class="iref" href="#rfc.xref.header.date.2">9.1</a></li>2941 <li class="indline1">Host <a class="iref" href="#rfc.iref.h.7"><b>8.4</b></a>, <a class="iref" href="#rfc.xref.header.host.1">9.1</a>, <a class="iref" href="#rfc.xref.header.host.2">C.1.1</a></li>2942 <li class="indline1">TE <a class="iref" href="#rfc.xref.header.te.1">3.4</a>, <a class="iref" href="#rfc.xref.header.te.2">3.4.1</a>, <a class="iref" href="#rfc.iref.h.8"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.header.te.3">9.1</a>, <a class="iref" href="#rfc.xref.header.te.4">C.3</a></li>2943 <li class="indline1">Trailer <a class="iref" href="#rfc.xref.header.trailer.1">3.4.1</a>, <a class="iref" href="#rfc.xref.header.trailer.2">4.5</a>, <a class="iref" href="#rfc.iref.h.9"><b>8.6</b></a>, <a class="iref" href="#rfc.xref.header.trailer.3">9.1</a></li>2944 <li class="indline1">Transfer-Encoding <a class="iref" href="#rfc.xref.header.transfer-encoding.1">3.4</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.2">4.3</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.3">4.4</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.4">4.5</a>, <a class="iref" href="#rfc.iref.h.10"><b>8.7</b></a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.5">9.1</a></li>2945 <li class="indline1">Upgrade <a class="iref" href="#rfc.xref.header.upgrade.1">4.5</a>, <a class="iref" href="#rfc.iref.h.11"><b>8.8</b></a>, <a class="iref" href="#rfc.xref.header.upgrade.2">9.1</a></li>2946 <li class="indline1">Via <a class="iref" href="#rfc.xref.header.via.1">4.5</a>, <a class="iref" href="#rfc.iref.h.12"><b>8.9</b></a>, <a class="iref" href="#rfc.xref.header.via.2">9.1</a></li>2947 </ul>2948 </li>2949 <li class="indline1">Host header <a class="iref" href="#rfc.iref.h.6"><b>8.4</b></a>, <a class="iref" href="#rfc.xref.header.host.1">9.1</a>, <a class="iref" href="#rfc.xref.header.host.2">C.1.1</a></li>2950 <li class="indline1">http URI scheme <a class="iref" href="#rfc.iref.h.1"><b>3.2.2</b></a></li>2951 <li class="indline1">https URI scheme <a class="iref" href="#rfc.iref.h.2">3.2.2</a></li>2952 </ul>2953 </li>2954 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">2955 <li class="indline1">implied *LWS <a class="iref" href="#rfc.iref.i.2"><b>2.1</b></a></li>2956 <li class="indline1">inbound <a class="iref" href="#rfc.iref.i.1">1.3</a></li>2957 <li class="indline1"><em>ISO-8859-1</em> <a class="iref" href="#rfc.xref.ISO-8859-1.1">2.2</a>, <a class="iref" href="#ISO-8859-1"><b>12.1</b></a></li>2958 </ul>2959 </li>2960 <li class="indline0"><a id="rfc.index.K" href="#rfc.index.K"><b>K</b></a><ul class="ind">2961 <li class="indline1"><em>Kri2001</em> <a class="iref" href="#rfc.xref.Kri2001.1">4.2</a>, <a class="iref" href="#Kri2001"><b>12.2</b></a></li>2962 </ul>2963 </li>2964 <li class="indline0"><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul class="ind">2965 <li class="indline1">Media Type 2966 <ul class="ind">2967 <li class="indline1">application/http <a class="iref" href="#rfc.iref.m.4"><b>9.3.2</b></a></li>2968 <li class="indline1">message/http <a class="iref" href="#rfc.iref.m.2"><b>9.3.1</b></a></li>2969 </ul>2970 </li>2971 <li class="indline1">message <a class="iref" href="#rfc.iref.m.1">1.3</a></li>2972 <li class="indline1">message/http Media Type <a class="iref" href="#rfc.iref.m.3"><b>9.3.1</b></a></li>2973 </ul>2974 </li>2975 <li class="indline0"><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul class="ind">2976 <li class="indline1"><em>Nie1997</em> <a class="iref" href="#rfc.xref.Nie1997.1">7.1.1</a>, <a class="iref" href="#Nie1997"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.Nie1997.2">C.3</a></li>2977 </ul>2978 </li>2979 <li class="indline0"><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul class="ind">2980 <li class="indline1">origin server <a class="iref" href="#rfc.iref.o.1">1.3</a></li>2981 <li class="indline1">outbound <a class="iref" href="#rfc.iref.o.2">1.3</a></li>2982 </ul>2983 </li>2984 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">2985 <li class="indline1"><em>Pad1995</em> <a class="iref" href="#rfc.xref.Pad1995.1">7.1.1</a>, <a class="iref" href="#Pad1995"><b>12.2</b></a></li>2986 <li class="indline1"><em>Part2</em> <a class="iref" href="#rfc.xref.Part2.1">2.3</a>, <a class="iref" href="#rfc.xref.Part2.2">2.3</a>, <a class="iref" href="#rfc.xref.Part2.3">3.2.1</a>, <a class="iref" href="#rfc.xref.Part2.4">4.2</a>, <a class="iref" href="#rfc.xref.Part2.5">4.2</a>, <a class="iref" href="#rfc.xref.Part2.6">4.3</a>, <a class="iref" href="#rfc.xref.Part2.7">5</a>, <a class="iref" href="#rfc.xref.Part2.8">5.1.2</a>, <a class="iref" href="#rfc.xref.Part2.9">6</a>, <a class="iref" href="#rfc.xref.Part2.10">6.1.1</a>, <a class="iref" href="#rfc.xref.Part2.11">7.1.2.2</a>, <a class="iref" href="#rfc.xref.Part2.12">7.1.4</a>, <a class="iref" href="#rfc.xref.Part2.13">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.14">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.15">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.16">7.2.3</a>, <a class="iref" href="#Part2"><b>12.1</b></a><ul class="ind">2987 <li class="indline1"><em>Section 3</em> <a class="iref" href="#rfc.xref.Part2.6">4.3</a></li>2988 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part2.1">2.3</a>, <a class="iref" href="#rfc.xref.Part2.4">4.2</a>, <a class="iref" href="#rfc.xref.Part2.7">5</a></li>2989 <li class="indline1"><em>Section 6</em> <a class="iref" href="#rfc.xref.Part2.2">2.3</a>, <a class="iref" href="#rfc.xref.Part2.5">4.2</a>, <a class="iref" href="#rfc.xref.Part2.9">6</a></li>2990 <li class="indline1"><em>Section 8.1.2</em> <a class="iref" href="#rfc.xref.Part2.11">7.1.2.2</a>, <a class="iref" href="#rfc.xref.Part2.12">7.1.4</a></li>2991 <li class="indline1"><em>Section 8.9</em> <a class="iref" href="#rfc.xref.Part2.8">5.1.2</a></li>2992 <li class="indline1"><em>Section 9</em> <a class="iref" href="#rfc.xref.Part2.10">6.1.1</a></li>2993 <li class="indline1"><em>Section 9.1.1</em> <a class="iref" href="#rfc.xref.Part2.13">7.2.3</a></li>2994 <li class="indline1"><em>Section 9.1</em> <a class="iref" href="#rfc.xref.Part2.16">7.2.3</a></li>2995 <li class="indline1"><em>Section 9.4.15</em> <a class="iref" href="#rfc.xref.Part2.3">3.2.1</a></li>2996 <li class="indline1"><em>Section 10.2</em> <a class="iref" href="#rfc.xref.Part2.14">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.15">7.2.3</a></li>2997 </ul>2998 </li>2999 <li class="indline1"><em>Part3</em> <a class="iref" href="#rfc.xref.Part3.1">1.3</a>, <a class="iref" href="#rfc.xref.Part3.2">1.3</a>, <a class="iref" href="#rfc.xref.Part3.3">1.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.4</a>, <a class="iref" href="#rfc.xref.Part3.5">2.2</a>, <a class="iref" href="#rfc.xref.Part3.6">2.3</a>, <a class="iref" href="#rfc.xref.Part3.7">2.3</a>, <a class="iref" href="#rfc.xref.Part3.8">2.3</a>, <a class="iref" href="#rfc.xref.Part3.9">3.4</a>, <a class="iref" href="#rfc.xref.Part3.10">3.4</a>, <a class="iref" href="#rfc.xref.Part3.11">4.2</a>, <a class="iref" href="#rfc.xref.Part3.12">5</a>, <a class="iref" href="#rfc.xref.Part3.13">6</a>, <a class="iref" href="#rfc.xref.Part3.14">8.5</a>, <a class="iref" href="#Part3"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part3.15">A</a>, <a class="iref" href="#rfc.xref.Part3.16">C.3</a><ul class="ind">3000 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part3.9">3.4</a>, <a class="iref" href="#rfc.xref.Part3.10">3.4</a></li>3001 <li class="indline1"><em>Section 3.3</em> <a class="iref" href="#rfc.xref.Part3.5">2.2</a></li>3002 <li class="indline1"><em>Section 3.4</em> <a class="iref" href="#rfc.xref.Part3.14">8.5</a></li>3003 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part3.1">1.3</a></li>3004 <li class="indline1"><em>Section 4.1</em> <a class="iref" href="#rfc.xref.Part3.8">2.3</a>, <a class="iref" href="#rfc.xref.Part3.11">4.2</a>, <a class="iref" href="#rfc.xref.Part3.12">5</a>, <a class="iref" href="#rfc.xref.Part3.13">6</a></li>3005 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part3.7">2.3</a></li>3006 <li class="indline1"><em>Section 5</em> <a class="iref" href="#rfc.xref.Part3.2">1.3</a>, <a class="iref" href="#rfc.xref.Part3.3">1.3</a></li>3007 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part3.6">2.3</a></li>3008 <li class="indline1"><em>Appendix A</em> <a class="iref" href="#rfc.xref.Part3.4">1.4</a></li>3009 </ul>3010 </li>3011 <li class="indline1"><em>Part5</em> <a class="iref" href="#Part5"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part5.1">C.3</a></li>3012 <li class="indline1"><em>Part6</em> <a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a>, <a class="iref" href="#rfc.xref.Part6.3">2.3</a>, <a class="iref" href="#rfc.xref.Part6.4">2.3</a>, <a class="iref" href="#rfc.xref.Part6.5">2.3</a>, <a class="iref" href="#rfc.xref.Part6.6">4.5</a>, <a class="iref" href="#rfc.xref.Part6.7">4.5</a>, <a class="iref" href="#rfc.xref.Part6.8">4.5</a>, <a class="iref" href="#Part6"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part6.9">C.3</a><ul class="ind">3013 <li class="indline1"><em>Section 1</em> <a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a></li>3014 <li class="indline1"><em>Section 16.2</em> <a class="iref" href="#rfc.xref.Part6.6">4.5</a></li>3015 <li class="indline1"><em>Section 16.4</em> <a class="iref" href="#rfc.xref.Part6.3">2.3</a>, <a class="iref" href="#rfc.xref.Part6.4">2.3</a>, <a class="iref" href="#rfc.xref.Part6.7">4.5</a></li>3016 <li class="indline1"><em>Section 16.6</em> <a class="iref" href="#rfc.xref.Part6.5">2.3</a>, <a class="iref" href="#rfc.xref.Part6.8">4.5</a></li>3017 </ul>3018 </li>3019 <li class="indline1">proxy <a class="iref" href="#rfc.iref.p.1">1.3</a></li>3020 </ul>3021 </li>3022 <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">3023 <li class="indline1">representation <a class="iref" href="#rfc.iref.r.4">1.3</a></li>3024 <li class="indline1">request <a class="iref" href="#rfc.iref.r.1">1.3</a></li>3025 <li class="indline1">resource <a class="iref" href="#rfc.iref.r.3">1.3</a></li>3026 <li class="indline1">response <a class="iref" href="#rfc.iref.r.2">1.3</a></li>3027 <li class="indline1"><em>RFC1123</em> <a class="iref" href="#rfc.xref.RFC1123.1">3.3.1</a>, <a class="iref" href="#RFC1123"><b>12.2</b></a></li>3028 <li class="indline1"><em>RFC1305</em> <a class="iref" href="#rfc.xref.RFC1305.1">8.3</a>, <a class="iref" href="#RFC1305"><b>12.2</b></a></li>3029 <li class="indline1"><em>RFC1436</em> <a class="iref" href="#rfc.xref.RFC1436.1">1.1</a>, <a class="iref" href="#RFC1436"><b>12.2</b></a></li>3030 <li class="indline1"><em>RFC1630</em> <a class="iref" href="#rfc.xref.RFC1630.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC1630.2">3.2</a>, <a class="iref" href="#RFC1630"><b>12.2</b></a></li>3031 <li class="indline1"><em>RFC1737</em> <a class="iref" href="#rfc.xref.RFC1737.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC1737.2">3.2</a>, <a class="iref" href="#RFC1737"><b>12.2</b></a></li>3032 <li class="indline1"><em>RFC1738</em> <a class="iref" href="#rfc.xref.RFC1738.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC1738.2">3.2</a>, <a class="iref" href="#rfc.xref.RFC1738.3">3.2.1</a>, <a class="iref" href="#RFC1738"><b>12.2</b></a></li>3033 <li class="indline1"><em>RFC1808</em> <a class="iref" href="#rfc.xref.RFC1808.1">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC1808.2">3.2.1</a>, <a class="iref" href="#RFC1808"><b>12.2</b></a></li>3034 <li class="indline1"><em>RFC1900</em> <a class="iref" href="#rfc.xref.RFC1900.1">3.2.2</a>, <a class="iref" href="#rfc.xref.RFC1900.2">10.4</a>, <a class="iref" href="#RFC1900"><b>12.2</b></a></li>3035 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#rfc.xref.RFC1945.1">1</a>, <a class="iref" href="#RFC1945"><b>12.2</b></a></li>3036 <li class="indline1"><em>RFC2045</em> <a class="iref" href="#rfc.xref.RFC2045.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC2045.2">3.4</a>, <a class="iref" href="#rfc.xref.RFC2045.3">11</a>, <a class="iref" href="#RFC2045"><b>12.1</b></a></li>3037 <li class="indline1"><em>RFC2047</em> <a class="iref" href="#rfc.xref.RFC2047.1">2.2</a>, <a class="iref" href="#RFC2047"><b>12.1</b></a></li>3038 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC2068.2">7.1.1</a>, <a class="iref" href="#rfc.xref.RFC2068.3">7.1.3</a>, <a class="iref" href="#rfc.xref.RFC2068.4">7.2.3</a>, <a class="iref" href="#rfc.xref.RFC2068.5">11</a>, <a class="iref" href="#RFC2068"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.6">C</a>, <a class="iref" href="#rfc.xref.RFC2068.7">C.2</a><ul class="ind">3039 <li class="indline1"><em>Section 19.7.1</em> <a class="iref" href="#rfc.xref.RFC2068.6">C</a></li>3040 </ul>3041 </li>3042 <li class="indline1"><em>RFC2109</em> <a class="iref" href="#rfc.xref.RFC2109.1">4.2</a>, <a class="iref" href="#RFC2109"><b>12.2</b></a></li>3043 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.2</a>, <a class="iref" href="#RFC2119"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.RFC2119.2">C.3</a></li>3044 <li class="indline1"><em>RFC2145</em> <a class="iref" href="#rfc.xref.RFC2145.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC2145.2">3.1</a>, <a class="iref" href="#RFC2145"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2145.3">C.3</a></li>3045 <li class="indline1"><em>RFC2324</em> <a class="iref" href="#rfc.xref.RFC2324.1">1.1</a>, <a class="iref" href="#RFC2324"><b>12.2</b></a></li>3046 <li class="indline1"><em>RFC2396</em> <a class="iref" href="#rfc.xref.RFC2396.1">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.2">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.3">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.4">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.5">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.6">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.7">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.8">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.9">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.10">3.2.3</a>, <a class="iref" href="#rfc.xref.RFC2396.11">5.1.2</a>, <a class="iref" href="#RFC2396"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.RFC2396.12">C.4</a><ul class="ind">3047 <li class="indline1"><em>Section 2.4.1</em> <a class="iref" href="#rfc.xref.RFC2396.11">5.1.2</a></li>3048 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.RFC2396.10">3.2.3</a></li>3049 <li class="indline1"><em>Section 3.2.2</em> <a class="iref" href="#rfc.xref.RFC2396.6">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.9">3.2.1</a></li>3050 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.RFC2396.3">3.2.1</a></li>3051 <li class="indline1"><em>Section 3.4</em> <a class="iref" href="#rfc.xref.RFC2396.7">3.2.1</a></li>3052 <li class="indline1"><em>Section 3</em> <a class="iref" href="#rfc.xref.RFC2396.2">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.5">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC2396.12">C.4</a></li>3053 <li class="indline1"><em>Section 4.1</em> <a class="iref" href="#rfc.xref.RFC2396.4">3.2.1</a></li>3054 <li class="indline1"><em>Section 5</em> <a class="iref" href="#rfc.xref.RFC2396.8">3.2.1</a></li>3055 </ul>3056 </li>3057 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">1</a>, <a class="iref" href="#rfc.xref.RFC2616.3">11</a>, <a class="iref" href="#RFC2616"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.4">D.1</a></li>3058 <li class="indline1"><em>RFC2818</em> <a class="iref" href="#rfc.xref.RFC2818.1">3.2.2</a>, <a class="iref" href="#RFC2818"><b>12.2</b></a></li>3059 <li class="indline1"><em>RFC2821</em> <a class="iref" href="#rfc.xref.RFC2821.1">1.1</a>, <a class="iref" href="#RFC2821"><b>12.2</b></a></li>3060 <li class="indline1"><em>RFC2822</em> <a class="iref" href="#rfc.xref.RFC2822.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC2822.2">4.1</a>, <a class="iref" href="#rfc.xref.RFC2822.3">4.2</a>, <a class="iref" href="#rfc.xref.RFC2822.4">8.3</a>, <a class="iref" href="#rfc.xref.RFC2822.5">8.9</a>, <a class="iref" href="#RFC2822"><b>12.2</b></a><ul class="ind">3061 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.RFC2822.3">4.2</a></li>3062 <li class="indline1"><em>Section 3.6.1</em> <a class="iref" href="#rfc.xref.RFC2822.4">8.3</a></li>3063 <li class="indline1"><em>Section 3.6.7</em> <a class="iref" href="#rfc.xref.RFC2822.5">8.9</a></li>3064 </ul>3065 </li>3066 <li class="indline1"><em>RFC2965</em> <a class="iref" href="#rfc.xref.RFC2965.1">4.2</a>, <a class="iref" href="#RFC2965"><b>12.2</b></a></li>3067 <li class="indline1"><em>RFC3864</em> <a class="iref" href="#rfc.xref.RFC3864.1">9.1</a>, <a class="iref" href="#RFC3864"><b>12.2</b></a></li>3068 <li class="indline1"><em>RFC3977</em> <a class="iref" href="#rfc.xref.RFC3977.1">1.1</a>, <a class="iref" href="#RFC3977"><b>12.2</b></a></li>3069 <li class="indline1"><em>RFC4288</em> <a class="iref" href="#rfc.xref.RFC4288.1">9.3</a>, <a class="iref" href="#RFC4288"><b>12.2</b></a></li>3070 <li class="indline1"><em>RFC4395</em> <a class="iref" href="#rfc.xref.RFC4395.1">9.2</a>, <a class="iref" href="#RFC4395"><b>12.2</b></a></li>3071 <li class="indline1"><em>RFC822</em> <a class="iref" href="#rfc.xref.RFC822.1">3.3.1</a>, <a class="iref" href="#RFC822"><b>12.2</b></a></li>3072 <li class="indline1"><em>RFC822ABNF</em> <a class="iref" href="#rfc.xref.RFC822ABNF.1">2.1</a>, <a class="iref" href="#rfc.xref.RFC822ABNF.2">11</a>, <a class="iref" href="#RFC822ABNF"><b>12.1</b></a></li>3073 <li class="indline1"><em>RFC959</em> <a class="iref" href="#rfc.xref.RFC959.1">1.1</a>, <a class="iref" href="#RFC959"><b>12.2</b></a></li>3074 </ul>3075 </li>3076 <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind">3077 <li class="indline1">server <a class="iref" href="#rfc.iref.s.1">1.3</a></li>3078 <li class="indline1"><em>Spe</em> <a class="iref" href="#rfc.xref.Spe.1">7.1.1</a>, <a class="iref" href="#Spe"><b>12.2</b></a></li>3079 </ul>3080 </li>3081 <li class="indline0"><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul class="ind">3082 <li class="indline1">TE header <a class="iref" href="#rfc.xref.header.te.1">3.4</a>, <a class="iref" href="#rfc.xref.header.te.2">3.4.1</a>, <a class="iref" href="#rfc.iref.t.2"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.header.te.3">9.1</a>, <a class="iref" href="#rfc.xref.header.te.4">C.3</a></li>3083 <li class="indline1"><em>Tou1998</em> <a class="iref" href="#rfc.xref.Tou1998.1">7.1.1</a>, <a class="iref" href="#Tou1998"><b>12.2</b></a></li>3084 <li class="indline1">Trailer header <a class="iref" href="#rfc.xref.header.trailer.1">3.4.1</a>, <a class="iref" href="#rfc.xref.header.trailer.2">4.5</a>, <a class="iref" href="#rfc.iref.t.3"><b>8.6</b></a>, <a class="iref" href="#rfc.xref.header.trailer.3">9.1</a></li>3085 <li class="indline1">Transfer-Encoding header <a class="iref" href="#rfc.xref.header.transfer-encoding.1">3.4</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.2">4.3</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.3">4.4</a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.4">4.5</a>, <a class="iref" href="#rfc.iref.t.4"><b>8.7</b></a>, <a class="iref" href="#rfc.xref.header.transfer-encoding.5">9.1</a></li>3086 <li class="indline1">tunnel <a class="iref" href="#rfc.iref.t.1">1.3</a></li>3087 </ul>3088 </li>3089 <li class="indline0"><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul class="ind">3090 <li class="indline1">Upgrade header <a class="iref" href="#rfc.xref.header.upgrade.1">4.5</a>, <a class="iref" href="#rfc.iref.u.5"><b>8.8</b></a>, <a class="iref" href="#rfc.xref.header.upgrade.2">9.1</a></li>3091 <li class="indline1">upstream <a class="iref" href="#rfc.iref.u.2">1.3</a></li>3092 <li class="indline1">URI scheme 3093 <ul class="ind">3094 <li class="indline1">http <a class="iref" href="#rfc.iref.u.3"><b>3.2.2</b></a></li>3095 <li class="indline1">https <a class="iref" href="#rfc.iref.u.4">3.2.2</a></li>3096 </ul>3097 </li>3098 <li class="indline1"><em>USASCII</em> <a class="iref" href="#rfc.xref.USASCII.1">2.2</a>, <a class="iref" href="#USASCII"><b>12.1</b></a></li>3099 <li class="indline1">user agent <a class="iref" href="#rfc.iref.u.1">1.3</a></li>3100 </ul>3101 </li>3102 <li class="indline0"><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul class="ind">3103 <li class="indline1">variant <a class="iref" href="#rfc.iref.v.1">1.3</a></li>3104 <li class="indline1">Via header <a class="iref" href="#rfc.xref.header.via.1">4.5</a>, <a class="iref" href="#rfc.iref.v.2"><b>8.9</b></a>, <a class="iref" href="#rfc.xref.header.via.2">9.1</a></li>3105 </ul>3106 </li>3107 <li class="indline0"><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul class="ind">3108 <li class="indline1"><em>WAIS</em> <a class="iref" href="#rfc.xref.WAIS.1">1.1</a>, <a class="iref" href="#WAIS"><b>12.2</b></a></li>3109 </ul>3110 </li>3111 </ul>3112 </div>3113 3121 </body> 3114 3122 </html>
Note: See TracChangeset
for help on using the changeset viewer.
