![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 1099 for draft-ietf-httpbis/00/p1-messaging.html
- Timestamp:
- 01/01/11 17:23:02 (10 years ago)
- File:
-
- 1 edited
-
draft-ietf-httpbis/00/p1-messaging.html (modified) (34 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/00/p1-messaging.html
r230 r1099 2 2 PUBLIC "-//W3C//DTD HTML 4.01//EN"> 3 3 <html lang="en"> 4 <head profile="http://www.w3.org/2006/03/hcard ">4 <head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/"> 5 5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> 6 6 <title>HTTP/1.1, part 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 } … … 135 121 } 136 122 table.header { 123 border-spacing: 1px; 137 124 width: 95%; 138 125 font-size: 10pt; … … 146 133 white-space: nowrap; 147 134 } 148 t d.header{135 table.header td { 149 136 background-color: gray; 150 137 width: 50%; 151 138 } 152 t d.header a {139 table.header a { 153 140 color: white; 154 141 } … … 161 148 display:table-header-group; 162 149 } 163 ul.toc {150 ul.toc, ul.toc ul { 164 151 list-style: none; 165 152 margin-left: 1.5em; … … 167 154 padding-left: 0em; 168 155 } 169 li.tocline0{156 ul.toc li { 170 157 line-height: 150%; 171 158 font-weight: bold; … … 174 161 margin-right: 0em; 175 162 } 176 li.tocline1{163 ul.toc li li { 177 164 line-height: normal; 178 165 font-weight: normal; … … 181 168 margin-right: 0em; 182 169 } 183 li. tocline2{170 li.excluded { 184 171 font-size: 0pt; 185 172 } … … 187 174 margin-left: 0em; 188 175 } 189 ul.ind {176 ul.ind, ul.ind ul { 190 177 list-style: none; 191 178 margin-left: 1.5em; 192 179 margin-right: 0em; 193 180 padding-left: 0em; 194 } 195 li.indline0 { 181 page-break-before: avoid; 182 } 183 ul.ind li { 196 184 font-weight: bold; 197 185 line-height: 200%; … … 199 187 margin-right: 0em; 200 188 } 201 li.indline1{189 ul.ind li li { 202 190 font-weight: normal; 203 191 line-height: 150%; 204 192 margin-left: 0em; 205 193 margin-right: 0em; 194 } 195 .avoidbreak { 196 page-break-inside: avoid; 206 197 } 207 198 .bcp14 { … … 288 279 } 289 280 290 a.iref{281 ul.ind li li a { 291 282 content: target-counter(attr(href), page); 292 283 } … … 301 292 @page { 302 293 @top-left { 303 content: "I NTERNET DRAFT";294 content: "Internet-Draft"; 304 295 } 305 296 @top-right { … … 351 342 <link rel="Appendix" title="C Conversion of Date Formats" href="#rfc.section.C"> 352 343 <link rel="Appendix" title="D Compatibility with Previous Versions" href="#rfc.section.D"> 353 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.365, 2008-03-07 07:17:25, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 354 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 355 <meta name="DC.Creator" content="Fielding, R."> 356 <meta name="DC.Creator" content="Gettys, J."> 357 <meta name="DC.Creator" content="Mogul, J."> 358 <meta name="DC.Creator" content="Frystyk, H."> 359 <meta name="DC.Creator" content="Masinter, L."> 360 <meta name="DC.Creator" content="Leach, P."> 361 <meta name="DC.Creator" content="Berners-Lee, T."> 362 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-00"> 363 <meta name="DC.Date.Issued" scheme="ISO8601" content="2007-12"> 364 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2068"> 365 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 366 <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."> 344 <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/"> 345 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 346 <meta name="dct.creator" content="Fielding, R."> 347 <meta name="dct.creator" content="Gettys, J."> 348 <meta name="dct.creator" content="Mogul, J."> 349 <meta name="dct.creator" content="Frystyk, H."> 350 <meta name="dct.creator" content="Masinter, L."> 351 <meta name="dct.creator" content="Leach, P."> 352 <meta name="dct.creator" content="Berners-Lee, T."> 353 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-00"> 354 <meta name="dct.issued" scheme="ISO8601" content="2007-12-20"> 355 <meta name="dct.replaces" content="urn:ietf:rfc:2068"> 356 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 357 <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."> 358 <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."> 367 359 </head> 368 360 <body> 369 <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1"> 370 <tr> 371 <td class="header left">Network Working Group</td> 372 <td class="header right">R. Fielding, Editor</td> 373 </tr> 374 <tr> 375 <td class="header left">Internet Draft</td> 376 <td class="header right">Day Software</td> 377 </tr> 378 <tr> 379 <td class="header left"> 380 <draft-ietf-httpbis-p1-messaging-00> 381 382 </td> 383 <td class="header right">J. Gettys</td> 384 </tr> 385 <tr> 386 <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2068">2068</a>, 387 <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 388 </td> 389 <td class="header right">One Laptop per Child</td> 390 </tr> 391 <tr> 392 <td class="header left">Intended status: Standards Track</td> 393 <td class="header right">J. Mogul</td> 394 </tr> 395 <tr> 396 <td class="header left">Expires: June 2008</td> 397 <td class="header right">HP</td> 398 </tr> 399 <tr> 400 <td class="header left"></td> 401 <td class="header right">H. Frystyk</td> 402 </tr> 403 <tr> 404 <td class="header left"></td> 405 <td class="header right">Microsoft</td> 406 </tr> 407 <tr> 408 <td class="header left"></td> 409 <td class="header right">L. Masinter</td> 410 </tr> 411 <tr> 412 <td class="header left"></td> 413 <td class="header right">Adobe Systems</td> 414 </tr> 415 <tr> 416 <td class="header left"></td> 417 <td class="header right">P. Leach</td> 418 </tr> 419 <tr> 420 <td class="header left"></td> 421 <td class="header right">Microsoft</td> 422 </tr> 423 <tr> 424 <td class="header left"></td> 425 <td class="header right">T. Berners-Lee</td> 426 </tr> 427 <tr> 428 <td class="header left"></td> 429 <td class="header right">W3C/MIT</td> 430 </tr> 431 <tr> 432 <td class="header left"></td> 433 <td class="header right">December 20, 2007</td> 434 </tr> 361 <table class="header"> 362 <tbody> 363 <tr> 364 <td class="left">Network Working Group</td> 365 <td class="right">R. Fielding, Editor</td> 366 </tr> 367 <tr> 368 <td class="left">Internet-Draft</td> 369 <td class="right">Day Software</td> 370 </tr> 371 <tr> 372 <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2068">2068</a>, <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 373 </td> 374 <td class="right">J. Gettys</td> 375 </tr> 376 <tr> 377 <td class="left">Intended status: Standards Track</td> 378 <td class="right">One Laptop per Child</td> 379 </tr> 380 <tr> 381 <td class="left">Expires: June 22, 2008</td> 382 <td class="right">J. Mogul</td> 383 </tr> 384 <tr> 385 <td class="left"></td> 386 <td class="right">HP</td> 387 </tr> 388 <tr> 389 <td class="left"></td> 390 <td class="right">H. Frystyk</td> 391 </tr> 392 <tr> 393 <td class="left"></td> 394 <td class="right">Microsoft</td> 395 </tr> 396 <tr> 397 <td class="left"></td> 398 <td class="right">L. Masinter</td> 399 </tr> 400 <tr> 401 <td class="left"></td> 402 <td class="right">Adobe Systems</td> 403 </tr> 404 <tr> 405 <td class="left"></td> 406 <td class="right">P. Leach</td> 407 </tr> 408 <tr> 409 <td class="left"></td> 410 <td class="right">Microsoft</td> 411 </tr> 412 <tr> 413 <td class="left"></td> 414 <td class="right">T. Berners-Lee</td> 415 </tr> 416 <tr> 417 <td class="left"></td> 418 <td class="right">W3C/MIT</td> 419 </tr> 420 <tr> 421 <td class="left"></td> 422 <td class="right">December 20, 2007</td> 423 </tr> 424 </tbody> 435 425 </table> 436 426 <p class="title">HTTP/1.1, part 1: URIs, Connections, and Message Parsing<br><span class="filename">draft-ietf-httpbis-p1-messaging-00</span></p> … … 447 437 in progress”. 448 438 </p> 449 <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>>.450 </p> 451 <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>>.452 </p> 453 <p>This Internet-Draft will expire in June2008.</p>439 <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>. 440 </p> 441 <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>. 442 </p> 443 <p>This Internet-Draft will expire on June 22, 2008.</p> 454 444 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 455 445 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information … … 474 464 <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1> 475 465 <ul class="toc"> 476 <li class="tocline0">1. <a href="#introduction">Introduction</a><ul class="toc">477 <li class="tocline1">1.1 <a href="#intro.purpose">Purpose</a></li>478 <li class="tocline1">1.2 <a href="#intro.requirements">Requirements</a></li>479 <li class="tocline1">1.3 <a href="#intro.terminology">Terminology</a></li>480 <li class="tocline1">1.4 <a href="#intro.overall.operation">Overall Operation</a></li>466 <li>1. <a href="#introduction">Introduction</a><ul> 467 <li>1.1 <a href="#intro.purpose">Purpose</a></li> 468 <li>1.2 <a href="#intro.requirements">Requirements</a></li> 469 <li>1.3 <a href="#intro.terminology">Terminology</a></li> 470 <li>1.4 <a href="#intro.overall.operation">Overall Operation</a></li> 481 471 </ul> 482 472 </li> 483 <li class="tocline0">2. <a href="#notation">Notational Conventions and Generic Grammar</a><ul class="toc">484 <li class="tocline1">2.1 <a href="#notation.abnf">Augmented BNF</a></li>485 <li class="tocline1">2.2 <a href="#basic.rules">Basic Rules</a></li>473 <li>2. <a href="#notation">Notational Conventions and Generic Grammar</a><ul> 474 <li>2.1 <a href="#notation.abnf">Augmented BNF</a></li> 475 <li>2.2 <a href="#basic.rules">Basic Rules</a></li> 486 476 </ul> 487 477 </li> 488 <li class="tocline0">3. <a href="#protocol.parameters">Protocol Parameters</a><ul class="toc">489 <li class="tocline1">3.1 <a href="#http.version">HTTP Version</a></li>490 <li class="tocline1">3.2 <a href="#uri">Uniform Resource Identifiers</a><ul class="toc">491 <li class="tocline1">3.2.1 <a href="#general.syntax">General Syntax</a></li>492 <li class="tocline1">3.2.2 <a href="#http.url">http URL</a></li>493 <li class="tocline1">3.2.3 <a href="#uri.comparison">URI Comparison</a></li>478 <li>3. <a href="#protocol.parameters">Protocol Parameters</a><ul> 479 <li>3.1 <a href="#http.version">HTTP Version</a></li> 480 <li>3.2 <a href="#uri">Uniform Resource Identifiers</a><ul> 481 <li>3.2.1 <a href="#general.syntax">General Syntax</a></li> 482 <li>3.2.2 <a href="#http.url">http URL</a></li> 483 <li>3.2.3 <a href="#uri.comparison">URI Comparison</a></li> 494 484 </ul> 495 485 </li> 496 <li class="tocline1">3.3 <a href="#date.time.formats">Date/Time Formats</a><ul class="toc">497 <li class="tocline1">3.3.1 <a href="#full.date">Full Date</a></li>486 <li>3.3 <a href="#date.time.formats">Date/Time Formats</a><ul> 487 <li>3.3.1 <a href="#full.date">Full Date</a></li> 498 488 </ul> 499 489 </li> 500 <li class="tocline1">3.4 <a href="#transfer.codings">Transfer Codings</a><ul class="toc">501 <li class="tocline1">3.4.1 <a href="#chunked.transfer.encoding">Chunked Transfer Coding</a></li>490 <li>3.4 <a href="#transfer.codings">Transfer Codings</a><ul> 491 <li>3.4.1 <a href="#chunked.transfer.encoding">Chunked Transfer Coding</a></li> 502 492 </ul> 503 493 </li> 504 494 </ul> 505 495 </li> 506 <li class="tocline0">4. <a href="#http.message">HTTP Message</a><ul class="toc">507 <li class="tocline1">4.1 <a href="#message.types">Message Types</a></li>508 <li class="tocline1">4.2 <a href="#message.headers">Message Headers</a></li>509 <li class="tocline1">4.3 <a href="#message.body">Message Body</a></li>510 <li class="tocline1">4.4 <a href="#message.length">Message Length</a></li>511 <li class="tocline1">4.5 <a href="#general.header.fields">General Header Fields</a></li>496 <li>4. <a href="#http.message">HTTP Message</a><ul> 497 <li>4.1 <a href="#message.types">Message Types</a></li> 498 <li>4.2 <a href="#message.headers">Message Headers</a></li> 499 <li>4.3 <a href="#message.body">Message Body</a></li> 500 <li>4.4 <a href="#message.length">Message Length</a></li> 501 <li>4.5 <a href="#general.header.fields">General Header Fields</a></li> 512 502 </ul> 513 503 </li> 514 <li class="tocline0">5. <a href="#request">Request</a><ul class="toc">515 <li class="tocline1">5.1 <a href="#request-line">Request-Line</a><ul class="toc">516 <li class="tocline1">5.1.1 <a href="#method">Method</a></li>517 <li class="tocline1">5.1.2 <a href="#request-uri">Request-URI</a></li>504 <li>5. <a href="#request">Request</a><ul> 505 <li>5.1 <a href="#request-line">Request-Line</a><ul> 506 <li>5.1.1 <a href="#method">Method</a></li> 507 <li>5.1.2 <a href="#request-uri">Request-URI</a></li> 518 508 </ul> 519 509 </li> 520 <li class="tocline1">5.2 <a href="#the.resource.identified.by.a.request">The Resource Identified by a Request</a></li>510 <li>5.2 <a href="#the.resource.identified.by.a.request">The Resource Identified by a Request</a></li> 521 511 </ul> 522 512 </li> 523 <li class="tocline0">6. <a href="#response">Response</a><ul class="toc">524 <li class="tocline1">6.1 <a href="#status-line">Status-Line</a><ul class="toc">525 <li class="tocline1">6.1.1 <a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></li>513 <li>6. <a href="#response">Response</a><ul> 514 <li>6.1 <a href="#status-line">Status-Line</a><ul> 515 <li>6.1.1 <a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></li> 526 516 </ul> 527 517 </li> 528 518 </ul> 529 519 </li> 530 <li class="tocline0">7. <a href="#connections">Connections</a><ul class="toc">531 <li class="tocline1">7.1 <a href="#persistent.connections">Persistent Connections</a><ul class="toc">532 <li class="tocline1">7.1.1 <a href="#persistent.purpose">Purpose</a></li>533 <li class="tocline1">7.1.2 <a href="#persistent.overall">Overall Operation</a><ul class="toc">534 <li class="tocline1">7.1.2.1 <a href="#persistent.negotiation">Negotiation</a></li>535 <li class="tocline1">7.1.2.2 <a href="#pipelining">Pipelining</a></li>520 <li>7. <a href="#connections">Connections</a><ul> 521 <li>7.1 <a href="#persistent.connections">Persistent Connections</a><ul> 522 <li>7.1.1 <a href="#persistent.purpose">Purpose</a></li> 523 <li>7.1.2 <a href="#persistent.overall">Overall Operation</a><ul> 524 <li>7.1.2.1 <a href="#persistent.negotiation">Negotiation</a></li> 525 <li>7.1.2.2 <a href="#pipelining">Pipelining</a></li> 536 526 </ul> 537 527 </li> 538 <li class="tocline1">7.1.3 <a href="#persistent.proxy">Proxy Servers</a></li>539 <li class="tocline1">7.1.4 <a href="#persistent.practical">Practical Considerations</a></li>528 <li>7.1.3 <a href="#persistent.proxy">Proxy Servers</a></li> 529 <li>7.1.4 <a href="#persistent.practical">Practical Considerations</a></li> 540 530 </ul> 541 531 </li> 542 <li class="tocline1">7.2 <a href="#message.transmission.requirements">Message Transmission Requirements</a><ul class="toc">543 <li class="tocline1">7.2.1 <a href="#persistent.flow">Persistent Connections and Flow Control</a></li>544 <li class="tocline1">7.2.2 <a href="#persistent.monitor">Monitoring Connections for Error Status Messages</a></li>545 <li class="tocline1">7.2.3 <a href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></li>546 <li class="tocline1">7.2.4 <a href="#connection.premature">Client Behavior if Server Prematurely Closes Connection</a></li>532 <li>7.2 <a href="#message.transmission.requirements">Message Transmission Requirements</a><ul> 533 <li>7.2.1 <a href="#persistent.flow">Persistent Connections and Flow Control</a></li> 534 <li>7.2.2 <a href="#persistent.monitor">Monitoring Connections for Error Status Messages</a></li> 535 <li>7.2.3 <a href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></li> 536 <li>7.2.4 <a href="#connection.premature">Client Behavior if Server Prematurely Closes Connection</a></li> 547 537 </ul> 548 538 </li> 549 539 </ul> 550 540 </li> 551 <li class="tocline0">8. <a href="#header.fields">Header Field Definitions</a><ul class="toc">552 <li class="tocline1">8.1 <a href="#header.connection">Connection</a></li>553 <li class="tocline1">8.2 <a href="#header.content-length">Content-Length</a></li>554 <li class="tocline1">8.3 <a href="#header.date">Date</a><ul class="toc">555 <li class="tocline1">8.3.1 <a href="#clockless.origin.server.operation">Clockless Origin Server Operation</a></li>541 <li>8. <a href="#header.fields">Header Field Definitions</a><ul> 542 <li>8.1 <a href="#header.connection">Connection</a></li> 543 <li>8.2 <a href="#header.content-length">Content-Length</a></li> 544 <li>8.3 <a href="#header.date">Date</a><ul> 545 <li>8.3.1 <a href="#clockless.origin.server.operation">Clockless Origin Server Operation</a></li> 556 546 </ul> 557 547 </li> 558 <li class="tocline1">8.4 <a href="#header.host">Host</a></li>559 <li class="tocline1">8.5 <a href="#header.te">TE</a></li>560 <li class="tocline1">8.6 <a href="#header.trailer">Trailer</a></li>561 <li class="tocline1">8.7 <a href="#header.transfer-encoding">Transfer-Encoding</a></li>562 <li class="tocline1">8.8 <a href="#header.upgrade">Upgrade</a></li>563 <li class="tocline1">8.9 <a href="#header.via">Via</a></li>548 <li>8.4 <a href="#header.host">Host</a></li> 549 <li>8.5 <a href="#header.te">TE</a></li> 550 <li>8.6 <a href="#header.trailer">Trailer</a></li> 551 <li>8.7 <a href="#header.transfer-encoding">Transfer-Encoding</a></li> 552 <li>8.8 <a href="#header.upgrade">Upgrade</a></li> 553 <li>8.9 <a href="#header.via">Via</a></li> 564 554 </ul> 565 555 </li> 566 <li class="tocline0">9. <a href="#IANA.considerations">IANA Considerations</a></li>567 <li class="tocline0">10. <a href="#security.considerations">Security Considerations</a><ul class="toc">568 <li class="tocline1">10.1 <a href="#personal.information">Personal Information</a></li>569 <li class="tocline1">10.2 <a href="#abuse.of.server.log.information">Abuse of Server Log Information</a></li>570 <li class="tocline1">10.3 <a href="#attack.pathname">Attacks Based On File and Path Names</a></li>571 <li class="tocline1">10.4 <a href="#dns.spoofing">DNS Spoofing</a></li>572 <li class="tocline1">10.5 <a href="#attack.proxies">Proxies and Caching</a></li>573 <li class="tocline1">10.6 <a href="#attack.DoS">Denial of Service Attacks on Proxies</a></li>556 <li>9. <a href="#IANA.considerations">IANA Considerations</a></li> 557 <li>10. <a href="#security.considerations">Security Considerations</a><ul> 558 <li>10.1 <a href="#personal.information">Personal Information</a></li> 559 <li>10.2 <a href="#abuse.of.server.log.information">Abuse of Server Log Information</a></li> 560 <li>10.3 <a href="#attack.pathname">Attacks Based On File and Path Names</a></li> 561 <li>10.4 <a href="#dns.spoofing">DNS Spoofing</a></li> 562 <li>10.5 <a href="#attack.proxies">Proxies and Caching</a></li> 563 <li>10.6 <a href="#attack.DoS">Denial of Service Attacks on Proxies</a></li> 574 564 </ul> 575 565 </li> 576 <li class="tocline0">11. <a href="#ack">Acknowledgments</a></li>577 <li class="tocline0">12. <a href="#rfc.references">References</a></li>578 <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>579 <li class="tocline0">A. <a href="#internet.media.type.http">Internet Media Type message/http and application/http</a></li>580 <li class="tocline0">B. <a href="#tolerant.applications">Tolerant Applications</a></li>581 <li class="tocline0">C. <a href="#conversion.of.date.formats">Conversion of Date Formats</a></li>582 <li class="tocline0">D. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc">583 <li class="tocline1">D.1 <a href="#changes.from.1.0">Changes from HTTP/1.0</a><ul class="toc">584 <li class="tocline1">D.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>566 <li>11. <a href="#ack">Acknowledgments</a></li> 567 <li>12. <a href="#rfc.references">References</a></li> 568 <li><a href="#rfc.authors">Authors' Addresses</a></li> 569 <li>A. <a href="#internet.media.type.http">Internet Media Type message/http and application/http</a></li> 570 <li>B. <a href="#tolerant.applications">Tolerant Applications</a></li> 571 <li>C. <a href="#conversion.of.date.formats">Conversion of Date Formats</a></li> 572 <li>D. <a href="#compatibility">Compatibility with Previous Versions</a><ul> 573 <li>D.1 <a href="#changes.from.1.0">Changes from HTTP/1.0</a><ul> 574 <li>D.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> 585 575 </ul> 586 576 </li> 587 <li class="tocline1">D.2 <a href="#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></li>588 <li class="tocline1">D.3 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>577 <li>D.2 <a href="#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></li> 578 <li>D.3 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li> 589 579 </ul> 590 580 </li> 591 <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>592 <li class="tocline0"><a href="#rfc.index">Index</a></li>581 <li><a href="#rfc.index">Index</a></li> 582 <li><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li> 593 583 </ul> 594 584 <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> <a id="introduction" href="#introduction">Introduction</a></h1> … … 625 615 <p id="rfc.section.1.3.p.2"> <span id="rfc.iref.c.1"></span> <dfn>connection</dfn> 626 616 </p> 627 < dl class="empty">628 < dd>A transport layer virtual circuit established between two programs for the purpose of communication.</dd>629 </ dl>617 <ul class="empty"> 618 <li>A transport layer virtual circuit established between two programs for the purpose of communication.</li> 619 </ul> 630 620 <p id="rfc.section.1.3.p.3"> <span id="rfc.iref.m.1"></span> <dfn>message</dfn> 631 621 </p> 632 < dl class="empty">633 < 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.634 </ dd>635 </ dl>622 <ul class="empty"> 623 <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. 624 </li> 625 </ul> 636 626 <p id="rfc.section.1.3.p.4"> <span id="rfc.iref.r.1"></span> <dfn>request</dfn> 637 627 </p> 638 < dl class="empty">639 < dd>An HTTP request message, as defined in <a href="#request" title="Request">Section 5</a>.640 </ dd>641 </ dl>628 <ul class="empty"> 629 <li>An HTTP request message, as defined in <a href="#request" title="Request">Section 5</a>. 630 </li> 631 </ul> 642 632 <p id="rfc.section.1.3.p.5"> <span id="rfc.iref.r.2"></span> <dfn>response</dfn> 643 633 </p> 644 < dl class="empty">645 < dd>An HTTP response message, as defined in <a href="#response" title="Response">Section 6</a>.646 </ dd>647 </ dl>634 <ul class="empty"> 635 <li>An HTTP response message, as defined in <a href="#response" title="Response">Section 6</a>. 636 </li> 637 </ul> 648 638 <p id="rfc.section.1.3.p.6"> <span id="rfc.iref.r.3"></span> <dfn>resource</dfn> 649 639 </p> 650 < dl class="empty">651 < 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) or640 <ul class="empty"> 641 <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 652 642 vary in other ways. 653 </ dd>654 </ dl>643 </li> 644 </ul> 655 645 <p id="rfc.section.1.3.p.7"> <span id="rfc.iref.e.1"></span> <dfn>entity</dfn> 656 646 </p> 657 < dl class="empty">658 < dd>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of647 <ul class="empty"> 648 <li>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of 659 649 entity-header fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="Entity">Section 3</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>. 660 </ dd>661 </ dl>650 </li> 651 </ul> 662 652 <p id="rfc.section.1.3.p.8"> <span id="rfc.iref.r.4"></span> <dfn>representation</dfn> 663 653 </p> 664 < dl class="empty">665 < 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 4</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.666 </ dd>667 </ dl>654 <ul class="empty"> 655 <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 4</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. 656 </li> 657 </ul> 668 658 <p id="rfc.section.1.3.p.9"> <span id="rfc.iref.c.2"></span> <dfn>content negotiation</dfn> 669 659 </p> 670 < dl class="empty">671 < 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 4</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).672 </ dd>673 </ dl>660 <ul class="empty"> 661 <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 4</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). 662 </li> 663 </ul> 674 664 <p id="rfc.section.1.3.p.10"> <span id="rfc.iref.v.1"></span> <dfn>variant</dfn> 675 665 </p> 676 < dl class="empty">677 < dd>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations666 <ul class="empty"> 667 <li>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations 678 668 is termed a `varriant'. Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation. 679 </ dd>680 </ dl>669 </li> 670 </ul> 681 671 <p id="rfc.section.1.3.p.11"> <span id="rfc.iref.c.3"></span> <dfn>client</dfn> 682 672 </p> 683 < dl class="empty">684 < dd>A program that establishes connections for the purpose of sending requests.</dd>685 </ dl>673 <ul class="empty"> 674 <li>A program that establishes connections for the purpose of sending requests.</li> 675 </ul> 686 676 <p id="rfc.section.1.3.p.12"> <span id="rfc.iref.u.1"></span> <dfn>user agent</dfn> 687 677 </p> 688 < dl class="empty">689 < dd>The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user678 <ul class="empty"> 679 <li>The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user 690 680 tools. 691 </ dd>692 </ dl>681 </li> 682 </ul> 693 683 <p id="rfc.section.1.3.p.13"> <span id="rfc.iref.s.1"></span> <dfn>server</dfn> 694 684 </p> 695 < dl class="empty">696 < dd>An application program that accepts connections in order to service requests by sending back responses. Any given program685 <ul class="empty"> 686 <li>An application program that accepts connections in order to service requests by sending back responses. Any given program 697 687 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 698 688 program for a particular connection, rather than to the program's capabilities in general. Likewise, any server may act as 699 689 an origin server, proxy, gateway, or tunnel, switching behavior based on the nature of each request. 700 </ dd>701 </ dl>690 </li> 691 </ul> 702 692 <p id="rfc.section.1.3.p.14"> <span id="rfc.iref.o.1"></span> <dfn>origin server</dfn> 703 693 </p> 704 < dl class="empty">705 < dd>The server on which a given resource resides or is to be created.</dd>706 </ dl>694 <ul class="empty"> 695 <li>The server on which a given resource resides or is to be created.</li> 696 </ul> 707 697 <p id="rfc.section.1.3.p.15"> <span id="rfc.iref.p.1"></span> <dfn>proxy</dfn> 708 698 </p> 709 < dl class="empty">710 < dd>An intermediary program which acts as both a server and a client for the purpose of making requests on behalf of other clients.699 <ul class="empty"> 700 <li>An intermediary program which acts as both a server and a client for the purpose of making requests on behalf of other clients. 711 701 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 712 702 the request or response beyond what is required for proxy authentication and identification. A "non-transparent proxy" is … … 714 704 services, media type transformation, protocol reduction, or anonymity filtering. Except where either transparent or non-transparent 715 705 behavior is explicitly stated, the HTTP proxy requirements apply to both types of proxies. 716 </ dd>717 </ dl>706 </li> 707 </ul> 718 708 <p id="rfc.section.1.3.p.16"> <span id="rfc.iref.g.1"></span> <dfn>gateway</dfn> 719 709 </p> 720 < dl class="empty">721 < dd>A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the710 <ul class="empty"> 711 <li>A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the 722 712 origin server for the requested resource; the requesting client may not be aware that it is communicating with a gateway. 723 </ dd>724 </ dl>713 </li> 714 </ul> 725 715 <p id="rfc.section.1.3.p.17"> <span id="rfc.iref.t.1"></span> <dfn>tunnel</dfn> 726 716 </p> 727 < dl class="empty">728 < dd>An intermediary program which is acting as a blind relay between two connections. Once active, a tunnel is not considered717 <ul class="empty"> 718 <li>An intermediary program which is acting as a blind relay between two connections. Once active, a tunnel is not considered 729 719 a party to the HTTP communication, though the tunnel may have been initiated by an HTTP request. The tunnel ceases to exist 730 720 when both ends of the relayed connections are closed. 731 </ dd>732 </ dl>721 </li> 722 </ul> 733 723 <p id="rfc.section.1.3.p.18"> <span id="rfc.iref.c.4"></span> <dfn>cache</dfn> 734 724 </p> 735 < dl class="empty">736 < dd>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion.725 <ul class="empty"> 726 <li>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion. 737 727 A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent 738 728 requests. Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel. 739 </ dd>740 </ dl>729 </li> 730 </ul> 741 731 <p id="rfc.section.1.3.p.19"> <span id="rfc.iref.c.5"></span> <dfn>cacheable</dfn> 742 732 </p> 743 < dl class="empty">744 < dd>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.733 <ul class="empty"> 734 <li>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests. 745 735 The rules for determining the cacheability of HTTP responses are defined in <a href="p6-cache.html#caching" title="Caching in HTTP">Section 2</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 746 736 request. 747 </ dd>748 </ dl>737 </li> 738 </ul> 749 739 <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> 750 740 </p> 751 < dl class="empty">752 < dd>Upstream and downstream describe the flow of a message: all messages flow from upstream to downstream.</dd>753 </ dl>741 <ul class="empty"> 742 <li>Upstream and downstream describe the flow of a message: all messages flow from upstream to downstream.</li> 743 </ul> 754 744 <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> 755 745 </p> 756 < dl class="empty">757 < dd>Inbound and outbound refer to the request and response paths for messages: "inbound" means "traveling toward the origin server",746 <ul class="empty"> 747 <li>Inbound and outbound refer to the request and response paths for messages: "inbound" means "traveling toward the origin server", 758 748 and "outbound" means "traveling toward the user agent" 759 </ dd>760 </ dl>749 </li> 750 </ul> 761 751 <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> 762 752 <p id="rfc.section.1.4.p.1">The HTTP protocol is a request/response protocol. A client sends a request to the server in the form of a request method, … … 825 815 </p> 826 816 <p id="rfc.section.2.1.p.2">name = definition </p> 827 < dl class="empty">828 < dd>The name of a rule is simply the name itself (without any enclosing "<" and ">") and is separated from its definition by the817 <ul class="empty"> 818 <li>The name of a rule is simply the name itself (without any enclosing "<" and ">") and is separated from its definition by the 829 819 equal "=" character. White space is only significant in that indentation of continuation lines is used to indicate a rule 830 820 definition that spans more than one line. Certain basic rules are in uppercase, such as SP, LWS, HT, CRLF, DIGIT, ALPHA, etc. 831 821 Angle brackets are used within definitions whenever their presence will facilitate discerning the use of rule names. 832 </ dd>833 </ dl>822 </li> 823 </ul> 834 824 <p id="rfc.section.2.1.p.3">"literal" </p> 835 < dl class="empty">836 < dd>Quotation marks surround literal text. Unless stated otherwise, the text is case-insensitive.</dd>837 </ dl>825 <ul class="empty"> 826 <li>Quotation marks surround literal text. Unless stated otherwise, the text is case-insensitive.</li> 827 </ul> 838 828 <p id="rfc.section.2.1.p.4">rule1 | rule2 </p> 839 < dl class="empty">840 < dd>Elements separated by a bar ("|") are alternatives, e.g., "yes | no" will accept yes or no.</dd>841 </ dl>829 <ul class="empty"> 830 <li>Elements separated by a bar ("|") are alternatives, e.g., "yes | no" will accept yes or no.</li> 831 </ul> 842 832 <p id="rfc.section.2.1.p.5">(rule1 rule2) </p> 843 < dl class="empty">844 < dd>Elements enclosed in parentheses are treated as a single element. Thus, "(elem (foo | bar) elem)" allows the token sequences833 <ul class="empty"> 834 <li>Elements enclosed in parentheses are treated as a single element. Thus, "(elem (foo | bar) elem)" allows the token sequences 845 835 "elem foo elem" and "elem bar elem". 846 </ dd>847 </ dl>836 </li> 837 </ul> 848 838 <p id="rfc.section.2.1.p.6">*rule </p> 849 < dl class="empty">850 < dd>The character "*" preceding an element indicates repetition. The full form is "<n>*<m>element" indicating at least <n> and839 <ul class="empty"> 840 <li>The character "*" preceding an element indicates repetition. The full form is "<n>*<m>element" indicating at least <n> and 851 841 at most <m> occurrences of element. Default values are 0 and infinity so that "*(element)" allows any number, including zero; 852 842 "1*element" requires at least one; and "1*2element" allows one or two. 853 </ dd>854 </ dl>843 </li> 844 </ul> 855 845 <p id="rfc.section.2.1.p.7">[rule] </p> 856 < dl class="empty">857 < dd>Square brackets enclose optional elements; "[foo bar]" is equivalent to "*1(foo bar)".</dd>858 </ dl>846 <ul class="empty"> 847 <li>Square brackets enclose optional elements; "[foo bar]" is equivalent to "*1(foo bar)".</li> 848 </ul> 859 849 <p id="rfc.section.2.1.p.8">N rule </p> 860 < dl class="empty">861 < dd>Specific repetition: "<n>(element)" is equivalent to "<n>*<n>(element)"; that is, exactly <n> occurrences of (element). Thus850 <ul class="empty"> 851 <li>Specific repetition: "<n>(element)" is equivalent to "<n>*<n>(element)"; that is, exactly <n> occurrences of (element). Thus 862 852 2DIGIT is a 2-digit number, and 3ALPHA is a string of three alphabetic characters. 863 </ dd>864 </ dl>853 </li> 854 </ul> 865 855 <p id="rfc.section.2.1.p.9">#rule </p> 866 < dl class="empty">867 < dd>A construct "#" is defined, similar to "*", for defining lists of elements. The full form is "<n>#<m>element" indicating at856 <ul class="empty"> 857 <li>A construct "#" is defined, similar to "*", for defining lists of elements. The full form is "<n>#<m>element" indicating at 868 858 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 869 </ dd>870 < dd>( *LWS element *( *LWS "," *LWS element ))</dd>871 < dd>can be shown as</dd>872 < dd>1#element</dd>873 < dd>Wherever this construct is used, null elements are allowed, but do not contribute to the count of elements present. That is,859 </li> 860 <li>( *LWS element *( *LWS "," *LWS element ))</li> 861 <li>can be shown as</li> 862 <li>1#element</li> 863 <li>Wherever this construct is used, null elements are allowed, but do not contribute to the count of elements present. That is, 874 864 "(element), , (element) " is permitted, but counts as only two elements. Therefore, where at least one element is required, 875 865 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 876 866 least one; and "1#2element" allows one or two. 877 </ dd>878 </ dl>867 </li> 868 </ul> 879 869 <p id="rfc.section.2.1.p.10">; comment </p> 880 < dl class="empty">881 < 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 is870 <ul class="empty"> 871 <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 882 872 a simple way of including useful notes in parallel with the specifications. 883 </ dd>884 </ dl>873 </li> 874 </ul> 885 875 <p id="rfc.section.2.1.p.11">implied *LWS </p> 886 < dl class="empty">887 < dd>The grammar described by this specification is word-based. Except where noted otherwise, linear white space (LWS) can be included876 <ul class="empty"> 877 <li>The grammar described by this specification is word-based. Except where noted otherwise, linear white space (LWS) can be included 888 878 between any two adjacent words (token or quoted-string), and between adjacent words and separators, without changing the interpretation 889 879 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 890 880 token. 891 </ dd>892 </ dl>881 </li> 882 </ul> 893 883 <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> 894 884 <p id="rfc.section.2.2.p.1">The following rules are used throughout this specification to describe basic parsing constructs. The US-ASCII coded character … … 973 963 </p> 974 964 <p id="rfc.section.3.1.p.9"> </p> 975 < dl class="empty">976 < dd> <b>Note:</b> Converting between versions of HTTP may involve modification of header fields required or forbidden by the versions involved.977 </ dd>978 </ dl>965 <ul class="empty"> 966 <li> <b>Note:</b> Converting between versions of HTTP may involve modification of header fields required or forbidden by the versions involved. 967 </li> 968 </ul> 979 969 <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> 980 970 <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, … … 990 980 </p> 991 981 <p id="rfc.section.3.2.1.p.3"> </p> 992 < dl class="empty">993 < dd> <b>Note:</b> Servers ought to be cautious about depending on URI lengths above 255 bytes, because some older client or proxy implementations982 <ul class="empty"> 983 <li> <b>Note:</b> Servers ought to be cautious about depending on URI lengths above 255 bytes, because some older client or proxy implementations 994 984 might not properly support these lengths. 995 </ dd>996 </ dl>985 </li> 986 </ul> 997 987 <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> 998 988 <p id="rfc.section.3.2.2.p.1">The "http" scheme is used to locate network resources via the HTTP protocol. This section defines the scheme-specific syntax … … 1028 1018 </pre><p id="rfc.section.3.3.1.p.3">The first format is preferred as an Internet standard and represents a fixed-length subset of that defined by RFC 1123 <a href="#RFC1123" id="rfc.xref.RFC1123.1"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a> (an update to RFC 822 <a href="#RFC822" id="rfc.xref.RFC822.3"><cite title="Standard for the format of ARPA Internet text messages">[RFC822]</cite></a>). The second format is in common use, but is based on the obsolete RFC 850 <a href="#RFC1036" id="rfc.xref.RFC1036.1"><cite title="Standard for interchange of USENET messages">[RFC1036]</cite></a> date format and lacks a four-digit year. HTTP/1.1 clients and servers 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 B</a> for further information. 1029 1019 </p> 1030 < dl class="empty">1031 < 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,1020 <ul class="empty"> 1021 <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, 1032 1022 as is sometimes the case when retrieving or posting messages via proxies/gateways to SMTP or NNTP. 1033 </ dd>1034 </ dl>1023 </li> 1024 </ul> 1035 1025 <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 1036 1026 Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as the three-letter abbreviation for … … 1238 1228 can parse multipart/byteranges responses. 1239 1229 </p> 1240 < dl class="empty">1241 < 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.1242 </ dd>1243 </ dl>1230 <ul class="empty"> 1231 <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. 1232 </li> 1233 </ul> 1244 1234 </li> 1245 1235 <li> … … 1329 1319 </p> 1330 1320 <p id="rfc.section.5.1.2.p.14"> </p> 1331 < dl class="empty">1332 < dd> <b>Note:</b> The "no rewrite" rule prevents the proxy from changing the meaning of the request when the origin server is improperly using1321 <ul class="empty"> 1322 <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 1333 1323 a non-reserved URI character for a reserved purpose. Implementors should be aware that some pre-HTTP/1.1 proxies have been 1334 1324 known to rewrite the Request-URI. 1335 </ dd>1336 </ dl>1325 </li> 1326 </ul> 1337 1327 <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> 1338 1328 <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> … … 1936 1926 <h1 id="rfc.references"><a href="#rfc.section.12" id="rfc.section.12">12.</a> References 1937 1927 </h1> 1938 <table summary="References">1928 <table> 1939 1929 <tr> 1940 1930 <td class="reference"><b id="ISO-8859">[ISO-8859]</b></td> … … 1947 1937 <tr> 1948 1938 <td class="reference"><b id="Nie1997">[Nie1997]</b></td> 1949 <td class="top">Nielsen, H. F.., Gettys, J., Prud'hommeaux, E., Lie, H., and C. Lilley, “Network Performance Effects of HTTP/1.1, CSS1, and PNG”, Proceedings of ACM SIGCOMM '97, Cannes France, Sep 1997.</td>1939 <td class="top">Nielsen, H., Gettys, J., Prud'hommeaux, E., Lie, H., and C. Lilley, “Network Performance Effects of HTTP/1.1, CSS1, and PNG”, Proceedings of ACM SIGCOMM '97, Cannes France, Sep 1997.</td> 1950 1940 </tr> 1951 1941 <tr> 1952 1942 <td class="reference"><b id="Pad1995">[Pad1995]</b></td> 1953 <td class="top">Padmanabhan, V. N. and J.C. Mogul, “Improving HTTP Latency”, Computer Networks and ISDN Systems v. 28, pp. 25-35, Dec 1995.<br>Slightly revised version of paper in Proc. 2nd International WWW Conference '94: Mosaic and the Web, Oct. 1994, which is available1943 <td class="top">Padmanabhan, V. and J. Mogul, “Improving HTTP Latency”, Computer Networks and ISDN Systems v. 28, pp. 25-35, Dec 1995.<br>Slightly revised version of paper in Proc. 2nd International WWW Conference '94: Mosaic and the Web, Oct. 1994, which is available 1954 1944 at <<a href="http://www.ncsa.uiuc.edu/SDG/IT94/Proceedings/DDay/mogul/HTTPLatency.html">http://www.ncsa.uiuc.edu/SDG/IT94/Proceedings/DDay/mogul/HTTPLatency.html</a>>. 1955 1945 </td> … … 1957 1947 <tr> 1958 1948 <td class="reference"><b id="Part2">[Part2]</b></td> 1959 <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>, and <atitle="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-00">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-00 (work in progress), December 2007.1949 <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>, and <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-00">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-00 (work in progress), December 2007. 1960 1950 </td> 1961 1951 </tr> 1962 1952 <tr> 1963 1953 <td class="reference"><b id="Part3">[Part3]</b></td> 1964 <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>, and <atitle="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-00">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-00 (work in progress), December 2007.1954 <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>, and <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-00">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-00 (work in progress), December 2007. 1965 1955 </td> 1966 1956 </tr> 1967 1957 <tr> 1968 1958 <td class="reference"><b id="Part6">[Part6]</b></td> 1969 <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>, and <atitle="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-00">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-00 (work in progress), December 2007.1959 <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>, and <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-00">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-00 (work in progress), December 2007. 1970 1960 </td> 1971 1961 </tr> … … 1977 1967 <tr> 1978 1968 <td class="reference"><b id="RFC1123">[RFC1123]</b></td> 1979 <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.1969 <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. 1980 1970 </td> 1981 1971 </tr> 1982 1972 <tr> 1983 1973 <td class="reference"><b id="RFC1305">[RFC1305]</b></td> 1984 <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.1974 <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. 1985 1975 </td> 1986 1976 </tr> 1987 1977 <tr> 1988 1978 <td class="reference"><b id="RFC1436">[RFC1436]</b></td> 1989 <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.1979 <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. 1990 1980 </td> 1991 1981 </tr> 1992 1982 <tr> 1993 1983 <td class="reference"><b id="RFC1590">[RFC1590]</b></td> 1994 <td class="top"><a title="USC/Information Sciences Institute">Postel, J.</a>, “<a href="http://tools.ietf.org/html/rfc1590">Media Type Registration Procedure</a>”, RFC 1590, November 1996.1984 <td class="top"><a href="mailto:Postel@ISI.EDU" title="USC/Information Sciences Institute">Postel, J.</a>, “<a href="http://tools.ietf.org/html/rfc1590">Media Type Registration Procedure</a>”, RFC 1590, November 1996. 1995 1985 </td> 1996 1986 </tr> 1997 1987 <tr> 1998 1988 <td class="reference"><b id="RFC1630">[RFC1630]</b></td> 1999 <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 Network1989 <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 2000 1990 as used in the World-Wide Web</a>”, RFC 1630, June 1994. 2001 1991 </td> … … 2003 1993 <tr> 2004 1994 <td class="reference"><b id="RFC1700">[RFC1700]</b></td> 2005 <td class="top"><a title="USC/Information Sciences Institute">Reynolds, J.</a> and <atitle="USC/Information Sciences Institute">J. Postel</a>, “<a href="http://tools.ietf.org/html/rfc1700">Assigned Numbers</a>”, STD 2, RFC 1700, October 1994.1995 <td class="top"><a href="mailto:jkrey@isi.edu" title="USC/Information Sciences Institute">Reynolds, J.</a> and <a href="mailto:postel@isi.edu" title="USC/Information Sciences Institute">J. Postel</a>, “<a href="http://tools.ietf.org/html/rfc1700">Assigned Numbers</a>”, STD 2, RFC 1700, October 1994. 2006 1996 </td> 2007 1997 </tr> 2008 1998 <tr> 2009 1999 <td class="reference"><b id="RFC1737">[RFC1737]</b></td> 2010 <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.2000 <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. 2011 2001 </td> 2012 2002 </tr> 2013 2003 <tr> 2014 2004 <td class="reference"><b id="RFC1738">[RFC1738]</b></td> 2015 <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.2005 <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. 2016 2006 </td> 2017 2007 </tr> 2018 2008 <tr> 2019 2009 <td class="reference"><b id="RFC1808">[RFC1808]</b></td> 2020 <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.2010 <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. 2021 2011 </td> 2022 2012 </tr> 2023 2013 <tr> 2024 2014 <td class="reference"><b id="RFC1900">[RFC1900]</b></td> 2025 <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.2015 <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. 2026 2016 </td> 2027 2017 </tr> 2028 2018 <tr> 2029 2019 <td class="reference"><b id="RFC1945">[RFC1945]</b></td> 2030 <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.2020 <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. 2031 2021 </td> 2032 2022 </tr> 2033 2023 <tr> 2034 2024 <td class="reference"><b id="RFC2045">[RFC2045]</b></td> 2035 <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.2025 <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. 2036 2026 </td> 2037 2027 </tr> 2038 2028 <tr> 2039 2029 <td class="reference"><b id="RFC2047">[RFC2047]</b></td> 2040 <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.2030 <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. 2041 2031 </td> 2042 2032 </tr> 2043 2033 <tr> 2044 2034 <td class="reference"><b id="RFC2068">[RFC2068]</b></td> 2045 <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.2035 <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. 2046 2036 </td> 2047 2037 </tr> 2048 2038 <tr> 2049 2039 <td class="reference"><b id="RFC2119">[RFC2119]</b></td> 2050 <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.2040 <td class="top"><a href="mailto:-" 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. 2051 2041 </td> 2052 2042 </tr> 2053 2043 <tr> 2054 2044 <td class="reference"><b id="RFC2145">[RFC2145]</b></td> 2055 <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.2045 <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. 2056 2046 </td> 2057 2047 </tr> 2058 2048 <tr> 2059 2049 <td class="reference"><b id="RFC2324">[RFC2324]</b></td> 2060 <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.2050 <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. 2061 2051 </td> 2062 2052 </tr> 2063 2053 <tr> 2064 2054 <td class="reference"><b id="RFC2396">[RFC2396]</b></td> 2065 <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.2055 <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. 2066 2056 </td> 2067 2057 </tr> 2068 2058 <tr> 2069 2059 <td class="reference"><b id="RFC2616">[RFC2616]</b></td> 2070 <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.2060 <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. 2071 2061 </td> 2072 2062 </tr> 2073 2063 <tr> 2074 2064 <td class="reference"><b id="RFC821">[RFC821]</b></td> 2075 <td class="top">Postel, J. B., “<a href="http://tools.ietf.org/html/rfc821">Simple Mail Transfer Protocol</a>”, STD 10, RFC 821, August 1982.2065 <td class="top">Postel, J., “<a href="http://tools.ietf.org/html/rfc821">Simple Mail Transfer Protocol</a>”, STD 10, RFC 821, August 1982. 2076 2066 </td> 2077 2067 </tr> 2078 2068 <tr> 2079 2069 <td class="reference"><b id="RFC822">[RFC822]</b></td> 2080 <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.2070 <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. 2081 2071 </td> 2082 2072 </tr> … … 2098 2088 <tr> 2099 2089 <td class="reference"><b id="Tou1998">[Tou1998]</b></td> 2100 <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 (original report dated Aug.1996), Aug 1998, <<a href="http://www.isi.edu/touch/pubs/http-perf96/">http://www.isi.edu/touch/pubs/http-perf96/</a>>.2090 <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 (original report dated Aug.1996), Aug 1998, <<a href="http://www.isi.edu/touch/pubs/http-perf96/">http://www.isi.edu/touch/pubs/http-perf96/</a>>. 2101 2091 </td> 2102 2092 </tr> … … 2110 2100 </tr> 2111 2101 </table> 2112 <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1> 2113 <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span> 2114 (editor) 2115 <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> 2116 <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> 2117 <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> 2118 <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> 2119 <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> 2120 <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> 2121 <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> 2102 <div class="avoidbreak"> 2103 <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1> 2104 <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span> 2105 (editor) 2106 <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> 2107 <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> 2108 <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> 2109 <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> 2110 <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> 2111 <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> 2112 <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> 2113 </div> 2122 2114 <div id="rfc.iref.m.2"></div> 2123 2115 <div id="rfc.iref.m.3"></div> 2124 2116 <div id="rfc.iref.m.4"></div> 2125 2117 <div id="rfc.iref.a.1"></div> 2126 <h1 id="rfc.section.A" ><a href="#rfc.section.A">A.</a> <a id="internet.media.type.http" href="#internet.media.type.http">Internet Media Type message/http and application/http</a></h1>2118 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="internet.media.type.http" href="#internet.media.type.http">Internet Media Type message/http and application/http</a></h1> 2127 2119 <p id="rfc.section.A.p.1">In addition to defining the HTTP/1.1 protocol, this document serves as the specification for the Internet media type "message/http" 2128 2120 and "application/http". The message/http type can be used to enclose a single HTTP request or response message, provided that … … 2288 2280 authentication trailers, chunked encoding and HTTP/1.0 clients.(Section <a href="#transfer.codings" title="Transfer Codings">3.4</a>, <a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">3.4.1</a>, and <a href="#header.te" id="rfc.xref.header.te.3" title="TE">8.5</a>) 2289 2281 </p> 2282 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 2283 <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.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> 2284 </p> 2285 <div class="print2col"> 2286 <ul class="ind"> 2287 <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul> 2288 <li>application/http Media Type <a href="#rfc.iref.a.1"><b>A</b></a></li> 2289 </ul> 2290 </li> 2291 <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul> 2292 <li>cache <a href="#rfc.iref.c.4">1.3</a></li> 2293 <li>cacheable <a href="#rfc.iref.c.5">1.3</a></li> 2294 <li>client <a href="#rfc.iref.c.3">1.3</a></li> 2295 <li>connection <a href="#rfc.iref.c.1">1.3</a></li> 2296 <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">D.2</a></li> 2297 <li>content negotiation <a href="#rfc.iref.c.2">1.3</a></li> 2298 <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></li> 2299 </ul> 2300 </li> 2301 <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul> 2302 <li>Date header <a href="#rfc.xref.header.date.1">4.5</a>, <a href="#rfc.iref.d.2"><b>8.3</b></a></li> 2303 <li>downstream <a href="#rfc.iref.d.1">1.3</a></li> 2304 </ul> 2305 </li> 2306 <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul> 2307 <li>entity <a href="#rfc.iref.e.1">1.3</a></li> 2308 </ul> 2309 </li> 2310 <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul> 2311 <li>gateway <a href="#rfc.iref.g.1">1.3</a></li> 2312 <li><tt>Grammar</tt> 2313 <ul> 2314 <li><tt>ALPHA</tt> <a href="#rfc.iref.g.6"><b>2.2</b></a></li> 2315 <li><tt>asctime-date</tt> <a href="#rfc.iref.g.29"><b>3.3.1</b></a></li> 2316 <li><tt>attribute</tt> <a href="#rfc.iref.g.40"><b>3.4</b></a></li> 2317 <li><tt>CHAR</tt> <a href="#rfc.iref.g.3"><b>2.2</b></a></li> 2318 <li><tt>chunk</tt> <a href="#rfc.iref.g.43"><b>3.4.1</b></a></li> 2319 <li><tt>chunk-data</tt> <a href="#rfc.iref.g.49"><b>3.4.1</b></a></li> 2320 <li><tt>chunk-ext-name</tt> <a href="#rfc.iref.g.47"><b>3.4.1</b></a></li> 2321 <li><tt>chunk-ext-val</tt> <a href="#rfc.iref.g.48"><b>3.4.1</b></a></li> 2322 <li><tt>chunk-extension</tt> <a href="#rfc.iref.g.46"><b>3.4.1</b></a></li> 2323 <li><tt>chunk-size</tt> <a href="#rfc.iref.g.44"><b>3.4.1</b></a></li> 2324 <li><tt>Chunked-Body</tt> <a href="#rfc.iref.g.42"><b>3.4.1</b></a></li> 2325 <li><tt>comment</tt> <a href="#rfc.iref.g.19"><b>2.2</b></a></li> 2326 <li><tt>Connection</tt> <a href="#rfc.iref.g.70"><b>8.1</b></a></li> 2327 <li><tt>connection-token</tt> <a href="#rfc.iref.g.71"><b>8.1</b></a></li> 2328 <li><tt>Content-Length</tt> <a href="#rfc.iref.g.72"><b>8.2</b></a></li> 2329 <li><tt>CR</tt> <a href="#rfc.iref.g.9"><b>2.2</b></a></li> 2330 <li><tt>CRLF</tt> <a href="#rfc.iref.g.13"><b>2.2</b></a></li> 2331 <li><tt>ctext</tt> <a href="#rfc.iref.g.20"><b>2.2</b></a></li> 2332 <li><tt>CTL</tt> <a href="#rfc.iref.g.8"><b>2.2</b></a></li> 2333 <li><tt>Date</tt> <a href="#rfc.iref.g.73"><b>8.3</b></a></li> 2334 <li><tt>date1</tt> <a href="#rfc.iref.g.30"><b>3.3.1</b></a></li> 2335 <li><tt>date2</tt> <a href="#rfc.iref.g.31"><b>3.3.1</b></a></li> 2336 <li><tt>date3</tt> <a href="#rfc.iref.g.32"><b>3.3.1</b></a></li> 2337 <li><tt>DIGIT</tt> <a href="#rfc.iref.g.7"><b>2.2</b></a></li> 2338 <li><tt>extension-code</tt> <a href="#rfc.iref.g.68"><b>6.1.1</b></a></li> 2339 <li><tt>extension-method</tt> <a href="#rfc.iref.g.63"><b>5.1.1</b></a></li> 2340 <li><tt>field-content</tt> <a href="#rfc.iref.g.57"><b>4.2</b></a></li> 2341 <li><tt>field-name</tt> <a href="#rfc.iref.g.55"><b>4.2</b></a></li> 2342 <li><tt>field-value</tt> <a href="#rfc.iref.g.56"><b>4.2</b></a></li> 2343 <li><tt>general-header</tt> <a href="#rfc.iref.g.59"><b>4.5</b></a></li> 2344 <li><tt>generic-message</tt> <a href="#rfc.iref.g.52"><b>4.1</b></a></li> 2345 <li><tt>HEX</tt> <a href="#rfc.iref.g.16"><b>2.2</b></a></li> 2346 <li><tt>Host</tt> <a href="#rfc.iref.g.74"><b>8.4</b></a></li> 2347 <li><tt>HT</tt> <a href="#rfc.iref.g.12"><b>2.2</b></a></li> 2348 <li><tt>HTTP-date</tt> <a href="#rfc.iref.g.26"><b>3.3.1</b></a></li> 2349 <li><tt>HTTP-message</tt> <a href="#rfc.iref.g.51"><b>4.1</b></a></li> 2350 <li><tt>HTTP-Version</tt> <a href="#rfc.iref.g.24"><b>3.1</b></a></li> 2351 <li><tt>http_URL</tt> <a href="#rfc.iref.g.25"><b>3.2.2</b></a></li> 2352 <li><tt>last-chunk</tt> <a href="#rfc.iref.g.45"><b>3.4.1</b></a></li> 2353 <li><tt>LF</tt> <a href="#rfc.iref.g.10"><b>2.2</b></a></li> 2354 <li><tt>LOALPHA</tt> <a href="#rfc.iref.g.5"><b>2.2</b></a></li> 2355 <li><tt>LWS</tt> <a href="#rfc.iref.g.14"><b>2.2</b></a></li> 2356 <li><tt>message-body</tt> <a href="#rfc.iref.g.58"><b>4.3</b></a></li> 2357 <li><tt>message-header</tt> <a href="#rfc.iref.g.54"><b>4.2</b></a></li> 2358 <li><tt>Method</tt> <a href="#rfc.iref.g.62"><b>5.1.1</b></a></li> 2359 <li><tt>month</tt> <a href="#rfc.iref.g.36"><b>3.3.1</b></a></li> 2360 <li><tt>OCTET</tt> <a href="#rfc.iref.g.2"><b>2.2</b></a></li> 2361 <li><tt>parameter</tt> <a href="#rfc.iref.g.39"><b>3.4</b></a></li> 2362 <li><tt>protocol-name</tt> <a href="#rfc.iref.g.82"><b>8.9</b></a></li> 2363 <li><tt>protocol-version</tt> <a href="#rfc.iref.g.83"><b>8.9</b></a></li> 2364 <li><tt>pseudonym</tt> <a href="#rfc.iref.g.85"><b>8.9</b></a></li> 2365 <li><tt>qdtext</tt> <a href="#rfc.iref.g.22"><b>2.2</b></a></li> 2366 <li><tt>quoted-pair</tt> <a href="#rfc.iref.g.23"><b>2.2</b></a></li> 2367 <li><tt>quoted-string</tt> <a href="#rfc.iref.g.21"><b>2.2</b></a></li> 2368 <li><tt>Reason-Phrase</tt> <a href="#rfc.iref.g.69"><b>6.1.1</b></a></li> 2369 <li><tt>received-by</tt> <a href="#rfc.iref.g.84"><b>8.9</b></a></li> 2370 <li><tt>received-protocol</tt> <a href="#rfc.iref.g.81"><b>8.9</b></a></li> 2371 <li><tt>Request</tt> <a href="#rfc.iref.g.60"><b>5</b></a></li> 2372 <li><tt>Request-Line</tt> <a href="#rfc.iref.g.61"><b>5.1</b></a></li> 2373 <li><tt>Request-URI</tt> <a href="#rfc.iref.g.64"><b>5.1.2</b></a></li> 2374 <li><tt>Response</tt> <a href="#rfc.iref.g.65"><b>6</b></a></li> 2375 <li><tt>rfc1123-date</tt> <a href="#rfc.iref.g.27"><b>3.3.1</b></a></li> 2376 <li><tt>rfc850-date</tt> <a href="#rfc.iref.g.28"><b>3.3.1</b></a></li> 2377 <li><tt>separators</tt> <a href="#rfc.iref.g.18"><b>2.2</b></a></li> 2378 <li><tt>SP</tt> <a href="#rfc.iref.g.11"><b>2.2</b></a></li> 2379 <li><tt>start-line</tt> <a href="#rfc.iref.g.53"><b>4.1</b></a></li> 2380 <li><tt>Status-Code</tt> <a href="#rfc.iref.g.67"><b>6.1.1</b></a></li> 2381 <li><tt>Status-Line</tt> <a href="#rfc.iref.g.66"><b>6.1</b></a></li> 2382 <li><tt>t-codings</tt> <a href="#rfc.iref.g.76"><b>8.5</b></a></li> 2383 <li><tt>TE</tt> <a href="#rfc.iref.g.75"><b>8.5</b></a></li> 2384 <li><tt>TEXT</tt> <a href="#rfc.iref.g.15"><b>2.2</b></a></li> 2385 <li><tt>time</tt> <a href="#rfc.iref.g.33"><b>3.3.1</b></a></li> 2386 <li><tt>token</tt> <a href="#rfc.iref.g.17"><b>2.2</b></a></li> 2387 <li><tt>trailer</tt> <a href="#rfc.iref.g.50"><b>3.4.1</b></a></li> 2388 <li><tt>Trailer</tt> <a href="#rfc.iref.g.77"><b>8.6</b></a></li> 2389 <li><tt>transfer-coding</tt> <a href="#rfc.iref.g.37"><b>3.4</b></a></li> 2390 <li><tt>Transfer-Encoding</tt> <a href="#rfc.iref.g.78"><b>8.7</b></a></li> 2391 <li><tt>transfer-extension</tt> <a href="#rfc.iref.g.38"><b>3.4</b></a></li> 2392 <li><tt>UPALPHA</tt> <a href="#rfc.iref.g.4"><b>2.2</b></a></li> 2393 <li><tt>Upgrade</tt> <a href="#rfc.iref.g.79"><b>8.8</b></a></li> 2394 <li><tt>value</tt> <a href="#rfc.iref.g.41"><b>3.4</b></a></li> 2395 <li><tt>Via</tt> <a href="#rfc.iref.g.80"><b>8.9</b></a></li> 2396 <li><tt>weekday</tt> <a href="#rfc.iref.g.35"><b>3.3.1</b></a></li> 2397 <li><tt>wkday</tt> <a href="#rfc.iref.g.34"><b>3.3.1</b></a></li> 2398 </ul> 2399 </li> 2400 </ul> 2401 </li> 2402 <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul> 2403 <li>Headers 2404 <ul> 2405 <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.1"><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">D.2</a></li> 2406 <li>Content-Length <a href="#rfc.xref.header.content-length.1">4.4</a>, <a href="#rfc.iref.h.2"><b>8.2</b></a></li> 2407 <li>Date <a href="#rfc.xref.header.date.1">4.5</a>, <a href="#rfc.iref.h.3"><b>8.3</b></a></li> 2408 <li>Host <a href="#rfc.iref.h.5"><b>8.4</b></a>, <a href="#rfc.xref.header.host.1">D.1.1</a></li> 2409 <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.6"><b>8.5</b></a>, <a href="#rfc.xref.header.te.3">D.3</a></li> 2410 <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.7"><b>8.6</b></a></li> 2411 <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.8"><b>8.7</b></a></li> 2412 <li>Upgrade <a href="#rfc.xref.header.upgrade.1">4.5</a>, <a href="#rfc.iref.h.9"><b>8.8</b></a></li> 2413 <li>Via <a href="#rfc.xref.header.via.1">4.5</a>, <a href="#rfc.iref.h.10"><b>8.9</b></a></li> 2414 </ul> 2415 </li> 2416 <li>Host header <a href="#rfc.iref.h.4"><b>8.4</b></a>, <a href="#rfc.xref.header.host.1">D.1.1</a></li> 2417 </ul> 2418 </li> 2419 <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul> 2420 <li>inbound <a href="#rfc.iref.i.1">1.3</a></li> 2421 <li><em>ISO-8859</em> <a href="#rfc.xref.ISO-8859.1">2.2</a>, <a href="#ISO-8859"><b>12</b></a></li> 2422 </ul> 2423 </li> 2424 <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul> 2425 <li>Media Type 2426 <ul> 2427 <li>application/http <a href="#rfc.iref.m.4"><b>A</b></a></li> 2428 <li>message/http <a href="#rfc.iref.m.2"><b>A</b></a></li> 2429 </ul> 2430 </li> 2431 <li>message <a href="#rfc.iref.m.1">1.3</a></li> 2432 <li>message/http Media Type <a href="#rfc.iref.m.3"><b>A</b></a></li> 2433 </ul> 2434 </li> 2435 <li><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul> 2436 <li><em>Nie1997</em> <a href="#rfc.xref.Nie1997.1">7.1.1</a>, <a href="#Nie1997"><b>12</b></a>, <a href="#rfc.xref.Nie1997.2">D.3</a></li> 2437 </ul> 2438 </li> 2439 <li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul> 2440 <li>origin server <a href="#rfc.iref.o.1">1.3</a></li> 2441 <li>outbound <a href="#rfc.iref.o.2">1.3</a></li> 2442 </ul> 2443 </li> 2444 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 2445 <li><em>Pad1995</em> <a href="#rfc.xref.Pad1995.1">7.1.1</a>, <a href="#Pad1995"><b>12</b></a></li> 2446 <li><em>Part2</em> <a href="#rfc.xref.Part2.1">3.2.1</a>, <a href="#rfc.xref.Part2.2">4.2</a>, <a href="#rfc.xref.Part2.3">4.2</a>, <a href="#rfc.xref.Part2.4">4.3</a>, <a href="#rfc.xref.Part2.5">5</a>, <a href="#rfc.xref.Part2.6">5.1.2</a>, <a href="#rfc.xref.Part2.7">6</a>, <a href="#rfc.xref.Part2.8">6.1.1</a>, <a href="#rfc.xref.Part2.9">7.1.2.2</a>, <a href="#rfc.xref.Part2.10">7.1.4</a>, <a href="#rfc.xref.Part2.11">7.2.3</a>, <a href="#rfc.xref.Part2.12">7.2.3</a>, <a href="#rfc.xref.Part2.13">7.2.3</a>, <a href="#rfc.xref.Part2.14">7.2.3</a>, <a href="#Part2"><b>12</b></a><ul> 2447 <li><em>Section 3</em> <a href="#rfc.xref.Part2.4">4.3</a></li> 2448 <li><em>Section 4</em> <a href="#rfc.xref.Part2.2">4.2</a>, <a href="#rfc.xref.Part2.5">5</a></li> 2449 <li><em>Section 6</em> <a href="#rfc.xref.Part2.3">4.2</a>, <a href="#rfc.xref.Part2.7">6</a></li> 2450 <li><em>Section 8.1.2</em> <a href="#rfc.xref.Part2.9">7.1.2.2</a>, <a href="#rfc.xref.Part2.10">7.1.4</a></li> 2451 <li><em>Section 8.9</em> <a href="#rfc.xref.Part2.6">5.1.2</a></li> 2452 <li><em>Section 9</em> <a href="#rfc.xref.Part2.8">6.1.1</a></li> 2453 <li><em>Section 9.1.1</em> <a href="#rfc.xref.Part2.11">7.2.3</a></li> 2454 <li><em>Section 9.1</em> <a href="#rfc.xref.Part2.14">7.2.3</a></li> 2455 <li><em>Section 9.4.15</em> <a href="#rfc.xref.Part2.1">3.2.1</a></li> 2456 <li><em>Section 10.2</em> <a href="#rfc.xref.Part2.12">7.2.3</a>, <a href="#rfc.xref.Part2.13">7.2.3</a></li> 2457 </ul> 2458 </li> 2459 <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">3.4</a>, <a href="#rfc.xref.Part3.7">3.4</a>, <a href="#rfc.xref.Part3.8">3.4</a>, <a href="#rfc.xref.Part3.9">3.4</a>, <a href="#rfc.xref.Part3.10">4.2</a>, <a href="#rfc.xref.Part3.11">5</a>, <a href="#rfc.xref.Part3.12">6</a>, <a href="#rfc.xref.Part3.13">8.5</a>, <a href="#Part3"><b>12</b></a>, <a href="#rfc.xref.Part3.14">B</a><ul> 2460 <li><em>Section 2.4</em> <a href="#rfc.xref.Part3.13">8.5</a></li> 2461 <li><em>Section 3</em> <a href="#rfc.xref.Part3.1">1.3</a></li> 2462 <li><em>Section 3.1</em> <a href="#rfc.xref.Part3.10">4.2</a>, <a href="#rfc.xref.Part3.11">5</a>, <a href="#rfc.xref.Part3.12">6</a></li> 2463 <li><em>Section 4</em> <a href="#rfc.xref.Part3.2">1.3</a>, <a href="#rfc.xref.Part3.3">1.3</a></li> 2464 <li><em>Appendix A</em> <a href="#rfc.xref.Part3.4">1.4</a></li> 2465 </ul> 2466 </li> 2467 <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">4.5</a>, <a href="#rfc.xref.Part6.4">4.5</a>, <a href="#rfc.xref.Part6.5">4.5</a>, <a href="#Part6"><b>12</b></a><ul> 2468 <li><em>Section 2</em> <a href="#rfc.xref.Part6.1">1.3</a>, <a href="#rfc.xref.Part6.2">1.4</a></li> 2469 <li><em>Section 3.2</em> <a href="#rfc.xref.Part6.3">4.5</a></li> 2470 <li><em>Section 3.4</em> <a href="#rfc.xref.Part6.4">4.5</a></li> 2471 <li><em>Section 3.6</em> <a href="#rfc.xref.Part6.5">4.5</a></li> 2472 </ul> 2473 </li> 2474 <li>proxy <a href="#rfc.iref.p.1">1.3</a></li> 2475 </ul> 2476 </li> 2477 <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul> 2478 <li>representation <a href="#rfc.iref.r.4">1.3</a></li> 2479 <li>request <a href="#rfc.iref.r.1">1.3</a></li> 2480 <li>resource <a href="#rfc.iref.r.3">1.3</a></li> 2481 <li>response <a href="#rfc.iref.r.2">1.3</a></li> 2482 <li><em>RFC1036</em> <a href="#rfc.xref.RFC1036.1">3.3.1</a>, <a href="#RFC1036"><b>12</b></a></li> 2483 <li><em>RFC1123</em> <a href="#rfc.xref.RFC1123.1">3.3.1</a>, <a href="#rfc.xref.RFC1123.2">8.3</a>, <a href="#RFC1123"><b>12</b></a></li> 2484 <li><em>RFC1305</em> <a href="#rfc.xref.RFC1305.1">8.3</a>, <a href="#RFC1305"><b>12</b></a></li> 2485 <li><em>RFC1436</em> <a href="#rfc.xref.RFC1436.1">1.1</a>, <a href="#RFC1436"><b>12</b></a></li> 2486 <li><em>RFC1590</em> <a href="#RFC1590"><b>12</b></a>, <a href="#rfc.xref.RFC1590.1">A</a></li> 2487 <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</b></a></li> 2488 <li><em>RFC1700</em> <a href="#rfc.xref.RFC1700.1">1.4</a>, <a href="#RFC1700"><b>12</b></a></li> 2489 <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</b></a></li> 2490 <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</b></a></li> 2491 <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</b></a></li> 2492 <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</b></a></li> 2493 <li><em>RFC1945</em> <a href="#rfc.xref.RFC1945.1">1.1</a>, <a href="#RFC1945"><b>12</b></a></li> 2494 <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</b></a></li> 2495 <li><em>RFC2047</em> <a href="#rfc.xref.RFC2047.1">2.2</a>, <a href="#RFC2047"><b>12</b></a></li> 2496 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">3.1</a>, <a href="#rfc.xref.RFC2068.2">7.1.3</a>, <a href="#RFC2068"><b>12</b></a>, <a href="#rfc.xref.RFC2068.3">D</a>, <a href="#rfc.xref.RFC2068.4">D</a>, <a href="#rfc.xref.RFC2068.5">D.2</a><ul> 2497 <li><em>Section 19.7.1</em> <a href="#rfc.xref.RFC2068.3">D</a></li> 2498 </ul> 2499 </li> 2500 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.2</a>, <a href="#RFC2119"><b>12</b></a>, <a href="#rfc.xref.RFC2119.2">D.3</a></li> 2501 <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</b></a></li> 2502 <li><em>RFC2324</em> <a href="#rfc.xref.RFC2324.1">1.1</a>, <a href="#RFC2324"><b>12</b></a></li> 2503 <li><em>RFC2396</em> <a href="#rfc.xref.RFC2396.1">3.2.1</a>, <a href="#rfc.xref.RFC2396.2">3.2.3</a>, <a href="#rfc.xref.RFC2396.3">5.1.2</a>, <a href="#RFC2396"><b>12</b></a></li> 2504 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">§</a>, <a href="#rfc.xref.RFC2616.2">1</a>, <a href="#RFC2616"><b>12</b></a></li> 2505 <li><em>RFC821</em> <a href="#rfc.xref.RFC821.1">1.1</a>, <a href="#RFC821"><b>12</b></a></li> 2506 <li><em>RFC822</em> <a href="#rfc.xref.RFC822.1">1.1</a>, <a href="#rfc.xref.RFC822.2">2.1</a>, <a href="#rfc.xref.RFC822.3">3.3.1</a>, <a href="#rfc.xref.RFC822.4">4.1</a>, <a href="#rfc.xref.RFC822.5">4.2</a>, <a href="#rfc.xref.RFC822.6">4.2</a>, <a href="#rfc.xref.RFC822.7">8.9</a>, <a href="#rfc.xref.RFC822.8">11</a>, <a href="#RFC822"><b>12</b></a><ul> 2507 <li><em>Section 3.1</em> <a href="#rfc.xref.RFC822.5">4.2</a></li> 2508 </ul> 2509 </li> 2510 <li><em>RFC959</em> <a href="#rfc.xref.RFC959.1">1.1</a>, <a href="#RFC959"><b>12</b></a></li> 2511 <li><em>RFC977</em> <a href="#rfc.xref.RFC977.1">1.1</a>, <a href="#RFC977"><b>12</b></a></li> 2512 </ul> 2513 </li> 2514 <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul> 2515 <li>server <a href="#rfc.iref.s.1">1.3</a></li> 2516 <li><em>Spe</em> <a href="#rfc.xref.Spe.1">7.1.1</a>, <a href="#Spe"><b>12</b></a></li> 2517 </ul> 2518 </li> 2519 <li><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul> 2520 <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">D.3</a></li> 2521 <li><em>Tou1998</em> <a href="#rfc.xref.Tou1998.1">7.1.1</a>, <a href="#Tou1998"><b>12</b></a></li> 2522 <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></li> 2523 <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></li> 2524 <li>tunnel <a href="#rfc.iref.t.1">1.3</a></li> 2525 </ul> 2526 </li> 2527 <li><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul> 2528 <li>Upgrade header <a href="#rfc.xref.header.upgrade.1">4.5</a>, <a href="#rfc.iref.u.3"><b>8.8</b></a></li> 2529 <li>upstream <a href="#rfc.iref.u.2">1.3</a></li> 2530 <li><em>USASCII</em> <a href="#rfc.xref.USASCII.1">2.2</a>, <a href="#USASCII"><b>12</b></a></li> 2531 <li>user agent <a href="#rfc.iref.u.1">1.3</a></li> 2532 </ul> 2533 </li> 2534 <li><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul> 2535 <li>variant <a href="#rfc.iref.v.1">1.3</a></li> 2536 <li>Via header <a href="#rfc.xref.header.via.1">4.5</a>, <a href="#rfc.iref.v.2"><b>8.9</b></a></li> 2537 </ul> 2538 </li> 2539 <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul> 2540 <li><em>WAIS</em> <a href="#rfc.xref.WAIS.1">1.1</a>, <a href="#WAIS"><b>12</b></a></li> 2541 </ul> 2542 </li> 2543 </ul> 2544 </div> 2290 2545 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> 2546 <p>Copyright © The IETF Trust (2007).</p> 2291 2547 <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the 2292 2548 authors retain all their rights. … … 2306 2562 <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result 2307 2563 of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users 2308 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>>.2564 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>. 2309 2565 </p> 2310 2566 <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary … … 2312 2568 at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>. 2313 2569 </p> 2314 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>2315 <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.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>2316 </p>2317 <div class="print2col">2318 <ul class="ind">2319 <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind">2320 <li class="indline1">application/http Media Type <a class="iref" href="#rfc.iref.a.1"><b>A</b></a></li>2321 </ul>2322 </li>2323 <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">2324 <li class="indline1">cache <a class="iref" href="#rfc.iref.c.4">1.3</a></li>2325 <li class="indline1">cacheable <a class="iref" href="#rfc.iref.c.5">1.3</a></li>2326 <li class="indline1">client <a class="iref" href="#rfc.iref.c.3">1.3</a></li>2327 <li class="indline1">connection <a class="iref" href="#rfc.iref.c.1">1.3</a></li>2328 <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">D.2</a></li>2329 <li class="indline1">content negotiation <a class="iref" href="#rfc.iref.c.2">1.3</a></li>2330 <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></li>2331 </ul>2332 </li>2333 <li class="indline0"><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul class="ind">2334 <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></li>2335 <li class="indline1">downstream <a class="iref" href="#rfc.iref.d.1">1.3</a></li>2336 </ul>2337 </li>2338 <li class="indline0"><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul class="ind">2339 <li class="indline1">entity <a class="iref" href="#rfc.iref.e.1">1.3</a></li>2340 </ul>2341 </li>2342 <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind">2343 <li class="indline1">gateway <a class="iref" href="#rfc.iref.g.1">1.3</a></li>2344 <li class="indline1"><tt>Grammar</tt> 2345 <ul class="ind">2346 <li class="indline1"><tt>ALPHA</tt> <a class="iref" href="#rfc.iref.g.6"><b>2.2</b></a></li>2347 <li class="indline1"><tt>asctime-date</tt> <a class="iref" href="#rfc.iref.g.29"><b>3.3.1</b></a></li>2348 <li class="indline1"><tt>attribute</tt> <a class="iref" href="#rfc.iref.g.40"><b>3.4</b></a></li>2349 <li class="indline1"><tt>CHAR</tt> <a class="iref" href="#rfc.iref.g.3"><b>2.2</b></a></li>2350 <li class="indline1"><tt>chunk</tt> <a class="iref" href="#rfc.iref.g.43"><b>3.4.1</b></a></li>2351 <li class="indline1"><tt>chunk-data</tt> <a class="iref" href="#rfc.iref.g.49"><b>3.4.1</b></a></li>2352 <li class="indline1"><tt>chunk-ext-name</tt> <a class="iref" href="#rfc.iref.g.47"><b>3.4.1</b></a></li>2353 <li class="indline1"><tt>chunk-ext-val</tt> <a class="iref" href="#rfc.iref.g.48"><b>3.4.1</b></a></li>2354 <li class="indline1"><tt>chunk-extension</tt> <a class="iref" href="#rfc.iref.g.46"><b>3.4.1</b></a></li>2355 <li class="indline1"><tt>chunk-size</tt> <a class="iref" href="#rfc.iref.g.44"><b>3.4.1</b></a></li>2356 <li class="indline1"><tt>Chunked-Body</tt> <a class="iref" href="#rfc.iref.g.42"><b>3.4.1</b></a></li>2357 <li class="indline1"><tt>comment</tt> <a class="iref" href="#rfc.iref.g.19"><b>2.2</b></a></li>2358 <li class="indline1"><tt>Connection</tt> <a class="iref" href="#rfc.iref.g.70"><b>8.1</b></a></li>2359 <li class="indline1"><tt>connection-token</tt> <a class="iref" href="#rfc.iref.g.71"><b>8.1</b></a></li>2360 <li class="indline1"><tt>Content-Length</tt> <a class="iref" href="#rfc.iref.g.72"><b>8.2</b></a></li>2361 <li class="indline1"><tt>CR</tt> <a class="iref" href="#rfc.iref.g.9"><b>2.2</b></a></li>2362 <li class="indline1"><tt>CRLF</tt> <a class="iref" href="#rfc.iref.g.13"><b>2.2</b></a></li>2363 <li class="indline1"><tt>ctext</tt> <a class="iref" href="#rfc.iref.g.20"><b>2.2</b></a></li>2364 <li class="indline1"><tt>CTL</tt> <a class="iref" href="#rfc.iref.g.8"><b>2.2</b></a></li>2365 <li class="indline1"><tt>Date</tt> <a class="iref" href="#rfc.iref.g.73"><b>8.3</b></a></li>2366 <li class="indline1"><tt>date1</tt> <a class="iref" href="#rfc.iref.g.30"><b>3.3.1</b></a></li>2367 <li class="indline1"><tt>date2</tt> <a class="iref" href="#rfc.iref.g.31"><b>3.3.1</b></a></li>2368 <li class="indline1"><tt>date3</tt> <a class="iref" href="#rfc.iref.g.32"><b>3.3.1</b></a></li>2369 <li class="indline1"><tt>DIGIT</tt> <a class="iref" href="#rfc.iref.g.7"><b>2.2</b></a></li>2370 <li class="indline1"><tt>extension-code</tt> <a class="iref" href="#rfc.iref.g.68"><b>6.1.1</b></a></li>2371 <li class="indline1"><tt>extension-method</tt> <a class="iref" href="#rfc.iref.g.63"><b>5.1.1</b></a></li>2372 <li class="indline1"><tt>field-content</tt> <a class="iref" href="#rfc.iref.g.57"><b>4.2</b></a></li>2373 <li class="indline1"><tt>field-name</tt> <a class="iref" href="#rfc.iref.g.55"><b>4.2</b></a></li>2374 <li class="indline1"><tt>field-value</tt> <a class="iref" href="#rfc.iref.g.56"><b>4.2</b></a></li>2375 <li class="indline1"><tt>general-header</tt> <a class="iref" href="#rfc.iref.g.59"><b>4.5</b></a></li>2376 <li class="indline1"><tt>generic-message</tt> <a class="iref" href="#rfc.iref.g.52"><b>4.1</b></a></li>2377 <li class="indline1"><tt>HEX</tt> <a class="iref" href="#rfc.iref.g.16"><b>2.2</b></a></li>2378 <li class="indline1"><tt>Host</tt> <a class="iref" href="#rfc.iref.g.74"><b>8.4</b></a></li>2379 <li class="indline1"><tt>HT</tt> <a class="iref" href="#rfc.iref.g.12"><b>2.2</b></a></li>2380 <li class="indline1"><tt>HTTP-date</tt> <a class="iref" href="#rfc.iref.g.26"><b>3.3.1</b></a></li>2381 <li class="indline1"><tt>HTTP-message</tt> <a class="iref" href="#rfc.iref.g.51"><b>4.1</b></a></li>2382 <li class="indline1"><tt>HTTP-Version</tt> <a class="iref" href="#rfc.iref.g.24"><b>3.1</b></a></li>2383 <li class="indline1"><tt>http_URL</tt> <a class="iref" href="#rfc.iref.g.25"><b>3.2.2</b></a></li>2384 <li class="indline1"><tt>last-chunk</tt> <a class="iref" href="#rfc.iref.g.45"><b>3.4.1</b></a></li>2385 <li class="indline1"><tt>LF</tt> <a class="iref" href="#rfc.iref.g.10"><b>2.2</b></a></li>2386 <li class="indline1"><tt>LOALPHA</tt> <a class="iref" href="#rfc.iref.g.5"><b>2.2</b></a></li>2387 <li class="indline1"><tt>LWS</tt> <a class="iref" href="#rfc.iref.g.14"><b>2.2</b></a></li>2388 <li class="indline1"><tt>message-body</tt> <a class="iref" href="#rfc.iref.g.58"><b>4.3</b></a></li>2389 <li class="indline1"><tt>message-header</tt> <a class="iref" href="#rfc.iref.g.54"><b>4.2</b></a></li>2390 <li class="indline1"><tt>Method</tt> <a class="iref" href="#rfc.iref.g.62"><b>5.1.1</b></a></li>2391 <li class="indline1"><tt>month</tt> <a class="iref" href="#rfc.iref.g.36"><b>3.3.1</b></a></li>2392 <li class="indline1"><tt>OCTET</tt> <a class="iref" href="#rfc.iref.g.2"><b>2.2</b></a></li>2393 <li class="indline1"><tt>parameter</tt> <a class="iref" href="#rfc.iref.g.39"><b>3.4</b></a></li>2394 <li class="indline1"><tt>protocol-name</tt> <a class="iref" href="#rfc.iref.g.82"><b>8.9</b></a></li>2395 <li class="indline1"><tt>protocol-version</tt> <a class="iref" href="#rfc.iref.g.83"><b>8.9</b></a></li>2396 <li class="indline1"><tt>pseudonym</tt> <a class="iref" href="#rfc.iref.g.85"><b>8.9</b></a></li>2397 <li class="indline1"><tt>qdtext</tt> <a class="iref" href="#rfc.iref.g.22"><b>2.2</b></a></li>2398 <li class="indline1"><tt>quoted-pair</tt> <a class="iref" href="#rfc.iref.g.23"><b>2.2</b></a></li>2399 <li class="indline1"><tt>quoted-string</tt> <a class="iref" href="#rfc.iref.g.21"><b>2.2</b></a></li>2400 <li class="indline1"><tt>Reason-Phrase</tt> <a class="iref" href="#rfc.iref.g.69"><b>6.1.1</b></a></li>2401 <li class="indline1"><tt>received-by</tt> <a class="iref" href="#rfc.iref.g.84"><b>8.9</b></a></li>2402 <li class="indline1"><tt>received-protocol</tt> <a class="iref" href="#rfc.iref.g.81"><b>8.9</b></a></li>2403 <li class="indline1"><tt>Request</tt> <a class="iref" href="#rfc.iref.g.60"><b>5</b></a></li>2404 <li class="indline1"><tt>Request-Line</tt> <a class="iref" href="#rfc.iref.g.61"><b>5.1</b></a></li>2405 <li class="indline1"><tt>Request-URI</tt> <a class="iref" href="#rfc.iref.g.64"><b>5.1.2</b></a></li>2406 <li class="indline1"><tt>Response</tt> <a class="iref" href="#rfc.iref.g.65"><b>6</b></a></li>2407 <li class="indline1"><tt>rfc1123-date</tt> <a class="iref" href="#rfc.iref.g.27"><b>3.3.1</b></a></li>2408 <li class="indline1"><tt>rfc850-date</tt> <a class="iref" href="#rfc.iref.g.28"><b>3.3.1</b></a></li>2409 <li class="indline1"><tt>separators</tt> <a class="iref" href="#rfc.iref.g.18"><b>2.2</b></a></li>2410 <li class="indline1"><tt>SP</tt> <a class="iref" href="#rfc.iref.g.11"><b>2.2</b></a></li>2411 <li class="indline1"><tt>start-line</tt> <a class="iref" href="#rfc.iref.g.53"><b>4.1</b></a></li>2412 <li class="indline1"><tt>Status-Code</tt> <a class="iref" href="#rfc.iref.g.67"><b>6.1.1</b></a></li>2413 <li class="indline1"><tt>Status-Line</tt> <a class="iref" href="#rfc.iref.g.66"><b>6.1</b></a></li>2414 <li class="indline1"><tt>t-codings</tt> <a class="iref" href="#rfc.iref.g.76"><b>8.5</b></a></li>2415 <li class="indline1"><tt>TE</tt> <a class="iref" href="#rfc.iref.g.75"><b>8.5</b></a></li>2416 <li class="indline1"><tt>TEXT</tt> <a class="iref" href="#rfc.iref.g.15"><b>2.2</b></a></li>2417 <li class="indline1"><tt>time</tt> <a class="iref" href="#rfc.iref.g.33"><b>3.3.1</b></a></li>2418 <li class="indline1"><tt>token</tt> <a class="iref" href="#rfc.iref.g.17"><b>2.2</b></a></li>2419 <li class="indline1"><tt>trailer</tt> <a class="iref" href="#rfc.iref.g.50"><b>3.4.1</b></a></li>2420 <li class="indline1"><tt>Trailer</tt> <a class="iref" href="#rfc.iref.g.77"><b>8.6</b></a></li>2421 <li class="indline1"><tt>transfer-coding</tt> <a class="iref" href="#rfc.iref.g.37"><b>3.4</b></a></li>2422 <li class="indline1"><tt>Transfer-Encoding</tt> <a class="iref" href="#rfc.iref.g.78"><b>8.7</b></a></li>2423 <li class="indline1"><tt>transfer-extension</tt> <a class="iref" href="#rfc.iref.g.38"><b>3.4</b></a></li>2424 <li class="indline1"><tt>UPALPHA</tt> <a class="iref" href="#rfc.iref.g.4"><b>2.2</b></a></li>2425 <li class="indline1"><tt>Upgrade</tt> <a class="iref" href="#rfc.iref.g.79"><b>8.8</b></a></li>2426 <li class="indline1"><tt>value</tt> <a class="iref" href="#rfc.iref.g.41"><b>3.4</b></a></li>2427 <li class="indline1"><tt>Via</tt> <a class="iref" href="#rfc.iref.g.80"><b>8.9</b></a></li>2428 <li class="indline1"><tt>weekday</tt> <a class="iref" href="#rfc.iref.g.35"><b>3.3.1</b></a></li>2429 <li class="indline1"><tt>wkday</tt> <a class="iref" href="#rfc.iref.g.34"><b>3.3.1</b></a></li>2430 </ul>2431 </li>2432 </ul>2433 </li>2434 <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">2435 <li class="indline1">Headers 2436 <ul class="ind">2437 <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.1"><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">D.2</a></li>2438 <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.2"><b>8.2</b></a></li>2439 <li class="indline1">Date <a class="iref" href="#rfc.xref.header.date.1">4.5</a>, <a class="iref" href="#rfc.iref.h.3"><b>8.3</b></a></li>2440 <li class="indline1">Host <a class="iref" href="#rfc.iref.h.5"><b>8.4</b></a>, <a class="iref" href="#rfc.xref.header.host.1">D.1.1</a></li>2441 <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.6"><b>8.5</b></a>, <a class="iref" href="#rfc.xref.header.te.3">D.3</a></li>2442 <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.7"><b>8.6</b></a></li>2443 <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.8"><b>8.7</b></a></li>2444 <li class="indline1">Upgrade <a class="iref" href="#rfc.xref.header.upgrade.1">4.5</a>, <a class="iref" href="#rfc.iref.h.9"><b>8.8</b></a></li>2445 <li class="indline1">Via <a class="iref" href="#rfc.xref.header.via.1">4.5</a>, <a class="iref" href="#rfc.iref.h.10"><b>8.9</b></a></li>2446 </ul>2447 </li>2448 <li class="indline1">Host header <a class="iref" href="#rfc.iref.h.4"><b>8.4</b></a>, <a class="iref" href="#rfc.xref.header.host.1">D.1.1</a></li>2449 </ul>2450 </li>2451 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">2452 <li class="indline1">inbound <a class="iref" href="#rfc.iref.i.1">1.3</a></li>2453 <li class="indline1"><em>ISO-8859</em> <a class="iref" href="#rfc.xref.ISO-8859.1">2.2</a>, <a class="iref" href="#ISO-8859"><b>12</b></a></li>2454 </ul>2455 </li>2456 <li class="indline0"><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul class="ind">2457 <li class="indline1">Media Type 2458 <ul class="ind">2459 <li class="indline1">application/http <a class="iref" href="#rfc.iref.m.4"><b>A</b></a></li>2460 <li class="indline1">message/http <a class="iref" href="#rfc.iref.m.2"><b>A</b></a></li>2461 </ul>2462 </li>2463 <li class="indline1">message <a class="iref" href="#rfc.iref.m.1">1.3</a></li>2464 <li class="indline1">message/http Media Type <a class="iref" href="#rfc.iref.m.3"><b>A</b></a></li>2465 </ul>2466 </li>2467 <li class="indline0"><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul class="ind">2468 <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</b></a>, <a class="iref" href="#rfc.xref.Nie1997.2">D.3</a></li>2469 </ul>2470 </li>2471 <li class="indline0"><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul class="ind">2472 <li class="indline1">origin server <a class="iref" href="#rfc.iref.o.1">1.3</a></li>2473 <li class="indline1">outbound <a class="iref" href="#rfc.iref.o.2">1.3</a></li>2474 </ul>2475 </li>2476 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">2477 <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</b></a></li>2478 <li class="indline1"><em>Part2</em> <a class="iref" href="#rfc.xref.Part2.1">3.2.1</a>, <a class="iref" href="#rfc.xref.Part2.2">4.2</a>, <a class="iref" href="#rfc.xref.Part2.3">4.2</a>, <a class="iref" href="#rfc.xref.Part2.4">4.3</a>, <a class="iref" href="#rfc.xref.Part2.5">5</a>, <a class="iref" href="#rfc.xref.Part2.6">5.1.2</a>, <a class="iref" href="#rfc.xref.Part2.7">6</a>, <a class="iref" href="#rfc.xref.Part2.8">6.1.1</a>, <a class="iref" href="#rfc.xref.Part2.9">7.1.2.2</a>, <a class="iref" href="#rfc.xref.Part2.10">7.1.4</a>, <a class="iref" href="#rfc.xref.Part2.11">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.12">7.2.3</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="#Part2"><b>12</b></a><ul class="ind">2479 <li class="indline1"><em>Section 3</em> <a class="iref" href="#rfc.xref.Part2.4">4.3</a></li>2480 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part2.2">4.2</a>, <a class="iref" href="#rfc.xref.Part2.5">5</a></li>2481 <li class="indline1"><em>Section 6</em> <a class="iref" href="#rfc.xref.Part2.3">4.2</a>, <a class="iref" href="#rfc.xref.Part2.7">6</a></li>2482 <li class="indline1"><em>Section 8.1.2</em> <a class="iref" href="#rfc.xref.Part2.9">7.1.2.2</a>, <a class="iref" href="#rfc.xref.Part2.10">7.1.4</a></li>2483 <li class="indline1"><em>Section 8.9</em> <a class="iref" href="#rfc.xref.Part2.6">5.1.2</a></li>2484 <li class="indline1"><em>Section 9</em> <a class="iref" href="#rfc.xref.Part2.8">6.1.1</a></li>2485 <li class="indline1"><em>Section 9.1.1</em> <a class="iref" href="#rfc.xref.Part2.11">7.2.3</a></li>2486 <li class="indline1"><em>Section 9.1</em> <a class="iref" href="#rfc.xref.Part2.14">7.2.3</a></li>2487 <li class="indline1"><em>Section 9.4.15</em> <a class="iref" href="#rfc.xref.Part2.1">3.2.1</a></li>2488 <li class="indline1"><em>Section 10.2</em> <a class="iref" href="#rfc.xref.Part2.12">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.13">7.2.3</a></li>2489 </ul>2490 </li>2491 <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">3.4</a>, <a class="iref" href="#rfc.xref.Part3.7">3.4</a>, <a class="iref" href="#rfc.xref.Part3.8">3.4</a>, <a class="iref" href="#rfc.xref.Part3.9">3.4</a>, <a class="iref" href="#rfc.xref.Part3.10">4.2</a>, <a class="iref" href="#rfc.xref.Part3.11">5</a>, <a class="iref" href="#rfc.xref.Part3.12">6</a>, <a class="iref" href="#rfc.xref.Part3.13">8.5</a>, <a class="iref" href="#Part3"><b>12</b></a>, <a class="iref" href="#rfc.xref.Part3.14">B</a><ul class="ind">2492 <li class="indline1"><em>Section 2.4</em> <a class="iref" href="#rfc.xref.Part3.13">8.5</a></li>2493 <li class="indline1"><em>Section 3</em> <a class="iref" href="#rfc.xref.Part3.1">1.3</a></li>2494 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part3.10">4.2</a>, <a class="iref" href="#rfc.xref.Part3.11">5</a>, <a class="iref" href="#rfc.xref.Part3.12">6</a></li>2495 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part3.2">1.3</a>, <a class="iref" href="#rfc.xref.Part3.3">1.3</a></li>2496 <li class="indline1"><em>Section A</em> <a class="iref" href="#rfc.xref.Part3.4">1.4</a></li>2497 </ul>2498 </li>2499 <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">4.5</a>, <a class="iref" href="#rfc.xref.Part6.4">4.5</a>, <a class="iref" href="#rfc.xref.Part6.5">4.5</a>, <a class="iref" href="#Part6"><b>12</b></a><ul class="ind">2500 <li class="indline1"><em>Section 2</em> <a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a></li>2501 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part6.3">4.5</a></li>2502 <li class="indline1"><em>Section 3.4</em> <a class="iref" href="#rfc.xref.Part6.4">4.5</a></li>2503 <li class="indline1"><em>Section 3.6</em> <a class="iref" href="#rfc.xref.Part6.5">4.5</a></li>2504 </ul>2505 </li>2506 <li class="indline1">proxy <a class="iref" href="#rfc.iref.p.1">1.3</a></li>2507 </ul>2508 </li>2509 <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">2510 <li class="indline1">representation <a class="iref" href="#rfc.iref.r.4">1.3</a></li>2511 <li class="indline1">request <a class="iref" href="#rfc.iref.r.1">1.3</a></li>2512 <li class="indline1">resource <a class="iref" href="#rfc.iref.r.3">1.3</a></li>2513 <li class="indline1">response <a class="iref" href="#rfc.iref.r.2">1.3</a></li>2514 <li class="indline1"><em>RFC1036</em> <a class="iref" href="#rfc.xref.RFC1036.1">3.3.1</a>, <a class="iref" href="#RFC1036"><b>12</b></a></li>2515 <li class="indline1"><em>RFC1123</em> <a class="iref" href="#rfc.xref.RFC1123.1">3.3.1</a>, <a class="iref" href="#rfc.xref.RFC1123.2">8.3</a>, <a class="iref" href="#RFC1123"><b>12</b></a></li>2516 <li class="indline1"><em>RFC1305</em> <a class="iref" href="#rfc.xref.RFC1305.1">8.3</a>, <a class="iref" href="#RFC1305"><b>12</b></a></li>2517 <li class="indline1"><em>RFC1436</em> <a class="iref" href="#rfc.xref.RFC1436.1">1.1</a>, <a class="iref" href="#RFC1436"><b>12</b></a></li>2518 <li class="indline1"><em>RFC1590</em> <a class="iref" href="#RFC1590"><b>12</b></a>, <a class="iref" href="#rfc.xref.RFC1590.1">A</a></li>2519 <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</b></a></li>2520 <li class="indline1"><em>RFC1700</em> <a class="iref" href="#rfc.xref.RFC1700.1">1.4</a>, <a class="iref" href="#RFC1700"><b>12</b></a></li>2521 <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</b></a></li>2522 <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</b></a></li>2523 <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</b></a></li>2524 <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</b></a></li>2525 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#rfc.xref.RFC1945.1">1.1</a>, <a class="iref" href="#RFC1945"><b>12</b></a></li>2526 <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</b></a></li>2527 <li class="indline1"><em>RFC2047</em> <a class="iref" href="#rfc.xref.RFC2047.1">2.2</a>, <a class="iref" href="#RFC2047"><b>12</b></a></li>2528 <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.3</a>, <a class="iref" href="#RFC2068"><b>12</b></a>, <a class="iref" href="#rfc.xref.RFC2068.3">D</a>, <a class="iref" href="#rfc.xref.RFC2068.4">D</a>, <a class="iref" href="#rfc.xref.RFC2068.5">D.2</a><ul class="ind">2529 <li class="indline1"><em>Section 19.7.1</em> <a class="iref" href="#rfc.xref.RFC2068.3">D</a></li>2530 </ul>2531 </li>2532 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.2</a>, <a class="iref" href="#RFC2119"><b>12</b></a>, <a class="iref" href="#rfc.xref.RFC2119.2">D.3</a></li>2533 <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</b></a></li>2534 <li class="indline1"><em>RFC2324</em> <a class="iref" href="#rfc.xref.RFC2324.1">1.1</a>, <a class="iref" href="#RFC2324"><b>12</b></a></li>2535 <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.3</a>, <a class="iref" href="#rfc.xref.RFC2396.3">5.1.2</a>, <a class="iref" href="#RFC2396"><b>12</b></a></li>2536 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">§</a>, <a class="iref" href="#rfc.xref.RFC2616.2">1</a>, <a class="iref" href="#RFC2616"><b>12</b></a></li>2537 <li class="indline1"><em>RFC821</em> <a class="iref" href="#rfc.xref.RFC821.1">1.1</a>, <a class="iref" href="#RFC821"><b>12</b></a></li>2538 <li class="indline1"><em>RFC822</em> <a class="iref" href="#rfc.xref.RFC822.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC822.2">2.1</a>, <a class="iref" href="#rfc.xref.RFC822.3">3.3.1</a>, <a class="iref" href="#rfc.xref.RFC822.4">4.1</a>, <a class="iref" href="#rfc.xref.RFC822.5">4.2</a>, <a class="iref" href="#rfc.xref.RFC822.6">4.2</a>, <a class="iref" href="#rfc.xref.RFC822.7">8.9</a>, <a class="iref" href="#rfc.xref.RFC822.8">11</a>, <a class="iref" href="#RFC822"><b>12</b></a><ul class="ind">2539 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.RFC822.5">4.2</a></li>2540 </ul>2541 </li>2542 <li class="indline1"><em>RFC959</em> <a class="iref" href="#rfc.xref.RFC959.1">1.1</a>, <a class="iref" href="#RFC959"><b>12</b></a></li>2543 <li class="indline1"><em>RFC977</em> <a class="iref" href="#rfc.xref.RFC977.1">1.1</a>, <a class="iref" href="#RFC977"><b>12</b></a></li>2544 </ul>2545 </li>2546 <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind">2547 <li class="indline1">server <a class="iref" href="#rfc.iref.s.1">1.3</a></li>2548 <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</b></a></li>2549 </ul>2550 </li>2551 <li class="indline0"><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul class="ind">2552 <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">D.3</a></li>2553 <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</b></a></li>2554 <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></li>2555 <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></li>2556 <li class="indline1">tunnel <a class="iref" href="#rfc.iref.t.1">1.3</a></li>2557 </ul>2558 </li>2559 <li class="indline0"><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul class="ind">2560 <li class="indline1">Upgrade header <a class="iref" href="#rfc.xref.header.upgrade.1">4.5</a>, <a class="iref" href="#rfc.iref.u.3"><b>8.8</b></a></li>2561 <li class="indline1">upstream <a class="iref" href="#rfc.iref.u.2">1.3</a></li>2562 <li class="indline1"><em>USASCII</em> <a class="iref" href="#rfc.xref.USASCII.1">2.2</a>, <a class="iref" href="#USASCII"><b>12</b></a></li>2563 <li class="indline1">user agent <a class="iref" href="#rfc.iref.u.1">1.3</a></li>2564 </ul>2565 </li>2566 <li class="indline0"><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul class="ind">2567 <li class="indline1">variant <a class="iref" href="#rfc.iref.v.1">1.3</a></li>2568 <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></li>2569 </ul>2570 </li>2571 <li class="indline0"><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul class="ind">2572 <li class="indline1"><em>WAIS</em> <a class="iref" href="#rfc.xref.WAIS.1">1.1</a>, <a class="iref" href="#WAIS"><b>12</b></a></li>2573 </ul>2574 </li>2575 </ul>2576 </div>2577 2570 </body> 2578 2571 </html>
Note: See TracChangeset
for help on using the changeset viewer.
