![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 1099 for draft-ietf-httpbis/01/p1-messaging.html
- Timestamp:
- 01/01/11 17:23:02 (9 years ago)
- File:
-
- 1 edited
-
draft-ietf-httpbis/01/p1-messaging.html (modified) (35 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/01/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 { … … 352 343 <link rel="Appendix" title="D Compatibility with Previous Versions" href="#rfc.section.D"> 353 344 <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E"> 354 <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/"> 355 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 356 <meta name="DC.Creator" content="Fielding, R."> 357 <meta name="DC.Creator" content="Gettys, J."> 358 <meta name="DC.Creator" content="Mogul, J."> 359 <meta name="DC.Creator" content="Frystyk, H."> 360 <meta name="DC.Creator" content="Masinter, L."> 361 <meta name="DC.Creator" content="Leach, P."> 362 <meta name="DC.Creator" content="Berners-Lee, T."> 363 <meta name="DC.Creator" content="Lafon, Y."> 364 <meta name="DC.Creator" content="Reschke, J. F."> 365 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-01"> 366 <meta name="DC.Date.Issued" scheme="ISO8601" content="2008-01"> 367 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 368 <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."> 345 <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/"> 346 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 347 <meta name="dct.creator" content="Fielding, R."> 348 <meta name="dct.creator" content="Gettys, J."> 349 <meta name="dct.creator" content="Mogul, J."> 350 <meta name="dct.creator" content="Frystyk, H."> 351 <meta name="dct.creator" content="Masinter, L."> 352 <meta name="dct.creator" content="Leach, P."> 353 <meta name="dct.creator" content="Berners-Lee, T."> 354 <meta name="dct.creator" content="Lafon, Y."> 355 <meta name="dct.creator" content="Reschke, J. F."> 356 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-01"> 357 <meta name="dct.issued" scheme="ISO8601" content="2008-01-12"> 358 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 359 <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."> 360 <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."> 369 361 </head> 370 362 <body> 371 <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1"> 372 <tr> 373 <td class="header left">Network Working Group</td> 374 <td class="header right">R. Fielding, Editor</td> 375 </tr> 376 <tr> 377 <td class="header left">Internet Draft</td> 378 <td class="header right">Day Software</td> 379 </tr> 380 <tr> 381 <td class="header left"> 382 <draft-ietf-httpbis-p1-messaging-01> 383 384 </td> 385 <td class="header right">J. Gettys</td> 386 </tr> 387 <tr> 388 <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 389 </td> 390 <td class="header right">One Laptop per Child</td> 391 </tr> 392 <tr> 393 <td class="header left">Intended status: Standards Track</td> 394 <td class="header right">J. Mogul</td> 395 </tr> 396 <tr> 397 <td class="header left">Expires: July 2008</td> 398 <td class="header right">HP</td> 399 </tr> 400 <tr> 401 <td class="header left"></td> 402 <td class="header right">H. Frystyk</td> 403 </tr> 404 <tr> 405 <td class="header left"></td> 406 <td class="header right">Microsoft</td> 407 </tr> 408 <tr> 409 <td class="header left"></td> 410 <td class="header right">L. Masinter</td> 411 </tr> 412 <tr> 413 <td class="header left"></td> 414 <td class="header right">Adobe Systems</td> 415 </tr> 416 <tr> 417 <td class="header left"></td> 418 <td class="header right">P. Leach</td> 419 </tr> 420 <tr> 421 <td class="header left"></td> 422 <td class="header right">Microsoft</td> 423 </tr> 424 <tr> 425 <td class="header left"></td> 426 <td class="header right">T. Berners-Lee</td> 427 </tr> 428 <tr> 429 <td class="header left"></td> 430 <td class="header right">W3C/MIT</td> 431 </tr> 432 <tr> 433 <td class="header left"></td> 434 <td class="header right">Y. Lafon, Editor</td> 435 </tr> 436 <tr> 437 <td class="header left"></td> 438 <td class="header right">W3C</td> 439 </tr> 440 <tr> 441 <td class="header left"></td> 442 <td class="header right">J. F. Reschke, Editor</td> 443 </tr> 444 <tr> 445 <td class="header left"></td> 446 <td class="header right">greenbytes</td> 447 </tr> 448 <tr> 449 <td class="header left"></td> 450 <td class="header right">January 12, 2008</td> 451 </tr> 363 <table class="header"> 364 <tbody> 365 <tr> 366 <td class="left">Network Working Group</td> 367 <td class="right">R. Fielding, Editor</td> 368 </tr> 369 <tr> 370 <td class="left">Internet-Draft</td> 371 <td class="right">Day Software</td> 372 </tr> 373 <tr> 374 <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved) 375 </td> 376 <td class="right">J. Gettys</td> 377 </tr> 378 <tr> 379 <td class="left">Intended status: Standards Track</td> 380 <td class="right">One Laptop per Child</td> 381 </tr> 382 <tr> 383 <td class="left">Expires: July 15, 2008</td> 384 <td class="right">J. Mogul</td> 385 </tr> 386 <tr> 387 <td class="left"></td> 388 <td class="right">HP</td> 389 </tr> 390 <tr> 391 <td class="left"></td> 392 <td class="right">H. Frystyk</td> 393 </tr> 394 <tr> 395 <td class="left"></td> 396 <td class="right">Microsoft</td> 397 </tr> 398 <tr> 399 <td class="left"></td> 400 <td class="right">L. Masinter</td> 401 </tr> 402 <tr> 403 <td class="left"></td> 404 <td class="right">Adobe Systems</td> 405 </tr> 406 <tr> 407 <td class="left"></td> 408 <td class="right">P. Leach</td> 409 </tr> 410 <tr> 411 <td class="left"></td> 412 <td class="right">Microsoft</td> 413 </tr> 414 <tr> 415 <td class="left"></td> 416 <td class="right">T. Berners-Lee</td> 417 </tr> 418 <tr> 419 <td class="left"></td> 420 <td class="right">W3C/MIT</td> 421 </tr> 422 <tr> 423 <td class="left"></td> 424 <td class="right">Y. Lafon, Editor</td> 425 </tr> 426 <tr> 427 <td class="left"></td> 428 <td class="right">W3C</td> 429 </tr> 430 <tr> 431 <td class="left"></td> 432 <td class="right">J. Reschke, Editor</td> 433 </tr> 434 <tr> 435 <td class="left"></td> 436 <td class="right">greenbytes</td> 437 </tr> 438 <tr> 439 <td class="left"></td> 440 <td class="right">January 12, 2008</td> 441 </tr> 442 </tbody> 452 443 </table> 453 444 <p class="title">HTTP/1.1, part 1: URIs, Connections, and Message Parsing<br><span class="filename">draft-ietf-httpbis-p1-messaging-01</span></p> … … 464 455 in progress”. 465 456 </p> 466 <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>>.467 </p> 468 <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>>.469 </p> 470 <p>This Internet-Draft will expire in July2008.</p>457 <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>. 458 </p> 459 <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>. 460 </p> 461 <p>This Internet-Draft will expire on July 15, 2008.</p> 471 462 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 472 463 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information … … 486 477 <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1> 487 478 <ul class="toc"> 488 <li class="tocline0">1. <a href="#introduction">Introduction</a><ul class="toc">489 <li class="tocline1">1.1 <a href="#intro.purpose">Purpose</a></li>490 <li class="tocline1">1.2 <a href="#intro.requirements">Requirements</a></li>491 <li class="tocline1">1.3 <a href="#intro.terminology">Terminology</a></li>492 <li class="tocline1">1.4 <a href="#intro.overall.operation">Overall Operation</a></li>479 <li>1. <a href="#introduction">Introduction</a><ul> 480 <li>1.1 <a href="#intro.purpose">Purpose</a></li> 481 <li>1.2 <a href="#intro.requirements">Requirements</a></li> 482 <li>1.3 <a href="#intro.terminology">Terminology</a></li> 483 <li>1.4 <a href="#intro.overall.operation">Overall Operation</a></li> 493 484 </ul> 494 485 </li> 495 <li class="tocline0">2. <a href="#notation">Notational Conventions and Generic Grammar</a><ul class="toc">496 <li class="tocline1">2.1 <a href="#notation.abnf">Augmented BNF</a></li>497 <li class="tocline1">2.2 <a href="#basic.rules">Basic Rules</a></li>486 <li>2. <a href="#notation">Notational Conventions and Generic Grammar</a><ul> 487 <li>2.1 <a href="#notation.abnf">Augmented BNF</a></li> 488 <li>2.2 <a href="#basic.rules">Basic Rules</a></li> 498 489 </ul> 499 490 </li> 500 <li class="tocline0">3. <a href="#protocol.parameters">Protocol Parameters</a><ul class="toc">501 <li class="tocline1">3.1 <a href="#http.version">HTTP Version</a></li>502 <li class="tocline1">3.2 <a href="#uri">Uniform Resource Identifiers</a><ul class="toc">503 <li class="tocline1">3.2.1 <a href="#general.syntax">General Syntax</a></li>504 <li class="tocline1">3.2.2 <a href="#http.url">http URL</a></li>505 <li class="tocline1">3.2.3 <a href="#uri.comparison">URI Comparison</a></li>491 <li>3. <a href="#protocol.parameters">Protocol Parameters</a><ul> 492 <li>3.1 <a href="#http.version">HTTP Version</a></li> 493 <li>3.2 <a href="#uri">Uniform Resource Identifiers</a><ul> 494 <li>3.2.1 <a href="#general.syntax">General Syntax</a></li> 495 <li>3.2.2 <a href="#http.url">http URL</a></li> 496 <li>3.2.3 <a href="#uri.comparison">URI Comparison</a></li> 506 497 </ul> 507 498 </li> 508 <li class="tocline1">3.3 <a href="#date.time.formats">Date/Time Formats</a><ul class="toc">509 <li class="tocline1">3.3.1 <a href="#full.date">Full Date</a></li>499 <li>3.3 <a href="#date.time.formats">Date/Time Formats</a><ul> 500 <li>3.3.1 <a href="#full.date">Full Date</a></li> 510 501 </ul> 511 502 </li> 512 <li class="tocline1">3.4 <a href="#transfer.codings">Transfer Codings</a><ul class="toc">513 <li class="tocline1">3.4.1 <a href="#chunked.transfer.encoding">Chunked Transfer Coding</a></li>503 <li>3.4 <a href="#transfer.codings">Transfer Codings</a><ul> 504 <li>3.4.1 <a href="#chunked.transfer.encoding">Chunked Transfer Coding</a></li> 514 505 </ul> 515 506 </li> 516 507 </ul> 517 508 </li> 518 <li class="tocline0">4. <a href="#http.message">HTTP Message</a><ul class="toc">519 <li class="tocline1">4.1 <a href="#message.types">Message Types</a></li>520 <li class="tocline1">4.2 <a href="#message.headers">Message Headers</a></li>521 <li class="tocline1">4.3 <a href="#message.body">Message Body</a></li>522 <li class="tocline1">4.4 <a href="#message.length">Message Length</a></li>523 <li class="tocline1">4.5 <a href="#general.header.fields">General Header Fields</a></li>509 <li>4. <a href="#http.message">HTTP Message</a><ul> 510 <li>4.1 <a href="#message.types">Message Types</a></li> 511 <li>4.2 <a href="#message.headers">Message Headers</a></li> 512 <li>4.3 <a href="#message.body">Message Body</a></li> 513 <li>4.4 <a href="#message.length">Message Length</a></li> 514 <li>4.5 <a href="#general.header.fields">General Header Fields</a></li> 524 515 </ul> 525 516 </li> 526 <li class="tocline0">5. <a href="#request">Request</a><ul class="toc">527 <li class="tocline1">5.1 <a href="#request-line">Request-Line</a><ul class="toc">528 <li class="tocline1">5.1.1 <a href="#method">Method</a></li>529 <li class="tocline1">5.1.2 <a href="#request-uri">Request-URI</a></li>517 <li>5. <a href="#request">Request</a><ul> 518 <li>5.1 <a href="#request-line">Request-Line</a><ul> 519 <li>5.1.1 <a href="#method">Method</a></li> 520 <li>5.1.2 <a href="#request-uri">Request-URI</a></li> 530 521 </ul> 531 522 </li> 532 <li class="tocline1">5.2 <a href="#the.resource.identified.by.a.request">The Resource Identified by a Request</a></li>523 <li>5.2 <a href="#the.resource.identified.by.a.request">The Resource Identified by a Request</a></li> 533 524 </ul> 534 525 </li> 535 <li class="tocline0">6. <a href="#response">Response</a><ul class="toc">536 <li class="tocline1">6.1 <a href="#status-line">Status-Line</a><ul class="toc">537 <li class="tocline1">6.1.1 <a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></li>526 <li>6. <a href="#response">Response</a><ul> 527 <li>6.1 <a href="#status-line">Status-Line</a><ul> 528 <li>6.1.1 <a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></li> 538 529 </ul> 539 530 </li> 540 531 </ul> 541 532 </li> 542 <li class="tocline0">7. <a href="#connections">Connections</a><ul class="toc">543 <li class="tocline1">7.1 <a href="#persistent.connections">Persistent Connections</a><ul class="toc">544 <li class="tocline1">7.1.1 <a href="#persistent.purpose">Purpose</a></li>545 <li class="tocline1">7.1.2 <a href="#persistent.overall">Overall Operation</a><ul class="toc">546 <li class="tocline1">7.1.2.1 <a href="#persistent.negotiation">Negotiation</a></li>547 <li class="tocline1">7.1.2.2 <a href="#pipelining">Pipelining</a></li>533 <li>7. <a href="#connections">Connections</a><ul> 534 <li>7.1 <a href="#persistent.connections">Persistent Connections</a><ul> 535 <li>7.1.1 <a href="#persistent.purpose">Purpose</a></li> 536 <li>7.1.2 <a href="#persistent.overall">Overall Operation</a><ul> 537 <li>7.1.2.1 <a href="#persistent.negotiation">Negotiation</a></li> 538 <li>7.1.2.2 <a href="#pipelining">Pipelining</a></li> 548 539 </ul> 549 540 </li> 550 <li class="tocline1">7.1.3 <a href="#persistent.proxy">Proxy Servers</a></li>551 <li class="tocline1">7.1.4 <a href="#persistent.practical">Practical Considerations</a></li>541 <li>7.1.3 <a href="#persistent.proxy">Proxy Servers</a></li> 542 <li>7.1.4 <a href="#persistent.practical">Practical Considerations</a></li> 552 543 </ul> 553 544 </li> 554 <li class="tocline1">7.2 <a href="#message.transmission.requirements">Message Transmission Requirements</a><ul class="toc">555 <li class="tocline1">7.2.1 <a href="#persistent.flow">Persistent Connections and Flow Control</a></li>556 <li class="tocline1">7.2.2 <a href="#persistent.monitor">Monitoring Connections for Error Status Messages</a></li>557 <li class="tocline1">7.2.3 <a href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></li>558 <li class="tocline1">7.2.4 <a href="#connection.premature">Client Behavior if Server Prematurely Closes Connection</a></li>545 <li>7.2 <a href="#message.transmission.requirements">Message Transmission Requirements</a><ul> 546 <li>7.2.1 <a href="#persistent.flow">Persistent Connections and Flow Control</a></li> 547 <li>7.2.2 <a href="#persistent.monitor">Monitoring Connections for Error Status Messages</a></li> 548 <li>7.2.3 <a href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></li> 549 <li>7.2.4 <a href="#connection.premature">Client Behavior if Server Prematurely Closes Connection</a></li> 559 550 </ul> 560 551 </li> 561 552 </ul> 562 553 </li> 563 <li class="tocline0">8. <a href="#header.fields">Header Field Definitions</a><ul class="toc">564 <li class="tocline1">8.1 <a href="#header.connection">Connection</a></li>565 <li class="tocline1">8.2 <a href="#header.content-length">Content-Length</a></li>566 <li class="tocline1">8.3 <a href="#header.date">Date</a><ul class="toc">567 <li class="tocline1">8.3.1 <a href="#clockless.origin.server.operation">Clockless Origin Server Operation</a></li>554 <li>8. <a href="#header.fields">Header Field Definitions</a><ul> 555 <li>8.1 <a href="#header.connection">Connection</a></li> 556 <li>8.2 <a href="#header.content-length">Content-Length</a></li> 557 <li>8.3 <a href="#header.date">Date</a><ul> 558 <li>8.3.1 <a href="#clockless.origin.server.operation">Clockless Origin Server Operation</a></li> 568 559 </ul> 569 560 </li> 570 <li class="tocline1">8.4 <a href="#header.host">Host</a></li>571 <li class="tocline1">8.5 <a href="#header.te">TE</a></li>572 <li class="tocline1">8.6 <a href="#header.trailer">Trailer</a></li>573 <li class="tocline1">8.7 <a href="#header.transfer-encoding">Transfer-Encoding</a></li>574 <li class="tocline1">8.8 <a href="#header.upgrade">Upgrade</a></li>575 <li class="tocline1">8.9 <a href="#header.via">Via</a></li>561 <li>8.4 <a href="#header.host">Host</a></li> 562 <li>8.5 <a href="#header.te">TE</a></li> 563 <li>8.6 <a href="#header.trailer">Trailer</a></li> 564 <li>8.7 <a href="#header.transfer-encoding">Transfer-Encoding</a></li> 565 <li>8.8 <a href="#header.upgrade">Upgrade</a></li> 566 <li>8.9 <a href="#header.via">Via</a></li> 576 567 </ul> 577 568 </li> 578 <li class="tocline0">9. <a href="#IANA.considerations">IANA Considerations</a></li>579 <li class="tocline0">10. <a href="#security.considerations">Security Considerations</a><ul class="toc">580 <li class="tocline1">10.1 <a href="#personal.information">Personal Information</a></li>581 <li class="tocline1">10.2 <a href="#abuse.of.server.log.information">Abuse of Server Log Information</a></li>582 <li class="tocline1">10.3 <a href="#attack.pathname">Attacks Based On File and Path Names</a></li>583 <li class="tocline1">10.4 <a href="#dns.spoofing">DNS Spoofing</a></li>584 <li class="tocline1">10.5 <a href="#attack.proxies">Proxies and Caching</a></li>585 <li class="tocline1">10.6 <a href="#attack.DoS">Denial of Service Attacks on Proxies</a></li>569 <li>9. <a href="#IANA.considerations">IANA Considerations</a></li> 570 <li>10. <a href="#security.considerations">Security Considerations</a><ul> 571 <li>10.1 <a href="#personal.information">Personal Information</a></li> 572 <li>10.2 <a href="#abuse.of.server.log.information">Abuse of Server Log Information</a></li> 573 <li>10.3 <a href="#attack.pathname">Attacks Based On File and Path Names</a></li> 574 <li>10.4 <a href="#dns.spoofing">DNS Spoofing</a></li> 575 <li>10.5 <a href="#attack.proxies">Proxies and Caching</a></li> 576 <li>10.6 <a href="#attack.DoS">Denial of Service Attacks on Proxies</a></li> 586 577 </ul> 587 578 </li> 588 <li class="tocline0">11. <a href="#ack">Acknowledgments</a></li>589 <li class="tocline0">12. <a href="#rfc.references">References</a><ul class="toc">590 <li class="tocline1">12.1 <a href="#rfc.references.1">Normative References</a></li>591 <li class="tocline1">12.2 <a href="#rfc.references.2">Informative References</a></li>579 <li>11. <a href="#ack">Acknowledgments</a></li> 580 <li>12. <a href="#rfc.references">References</a><ul> 581 <li>12.1 <a href="#rfc.references.1">Normative References</a></li> 582 <li>12.2 <a href="#rfc.references.2">Informative References</a></li> 592 583 </ul> 593 584 </li> 594 <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>595 <li class="tocline0">A. <a href="#internet.media.type.http">Internet Media Types</a><ul class="toc">596 <li class="tocline1">A.1 <a href="#internet.media.type.message.http">Internet Media Type message/http</a></li>597 <li class="tocline1">A.2 <a href="#internet.media.type.application.http">Internet Media Type application/http</a></li>585 <li><a href="#rfc.authors">Authors' Addresses</a></li> 586 <li>A. <a href="#internet.media.type.http">Internet Media Types</a><ul> 587 <li>A.1 <a href="#internet.media.type.message.http">Internet Media Type message/http</a></li> 588 <li>A.2 <a href="#internet.media.type.application.http">Internet Media Type application/http</a></li> 598 589 </ul> 599 590 </li> 600 <li class="tocline0">B. <a href="#tolerant.applications">Tolerant Applications</a></li>601 <li class="tocline0">C. <a href="#conversion.of.date.formats">Conversion of Date Formats</a></li>602 <li class="tocline0">D. <a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc">603 <li class="tocline1">D.1 <a href="#changes.from.1.0">Changes from HTTP/1.0</a><ul class="toc">604 <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>591 <li>B. <a href="#tolerant.applications">Tolerant Applications</a></li> 592 <li>C. <a href="#conversion.of.date.formats">Conversion of Date Formats</a></li> 593 <li>D. <a href="#compatibility">Compatibility with Previous Versions</a><ul> 594 <li>D.1 <a href="#changes.from.1.0">Changes from HTTP/1.0</a><ul> 595 <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> 605 596 </ul> 606 597 </li> 607 <li class="tocline1">D.2 <a href="#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></li>608 <li class="tocline1">D.3 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li>609 <li class="tocline1">D.4 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>598 <li>D.2 <a href="#compatibility.with.http.1.0.persistent.connections">Compatibility with HTTP/1.0 Persistent Connections</a></li> 599 <li>D.3 <a href="#changes.from.rfc.2068">Changes from RFC 2068</a></li> 600 <li>D.4 <a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li> 610 601 </ul> 611 602 </li> 612 <li class="tocline0">E. <a href="#rfc.section.E">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">613 <li class="tocline1">E.1 <a href="#rfc.section.E.1">Since RFC2616</a></li>614 <li class="tocline1">E.2 <a href="#rfc.section.E.2">Since draft-ietf-httpbis-p1-messaging-00</a></li>603 <li>E. <a href="#rfc.section.E">Change Log (to be removed by RFC Editor before publication)</a><ul> 604 <li>E.1 <a href="#rfc.section.E.1">Since RFC2616</a></li> 605 <li>E.2 <a href="#rfc.section.E.2">Since draft-ietf-httpbis-p1-messaging-00</a></li> 615 606 </ul> 616 607 </li> 617 <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>618 <li class="tocline0"><a href="#rfc.index">Index</a></li>608 <li><a href="#rfc.index">Index</a></li> 609 <li><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li> 619 610 </ul> 620 611 <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> <a id="introduction" href="#introduction">Introduction</a></h1> … … 657 648 <p id="rfc.section.1.3.p.2"> <span id="rfc.iref.c.1"></span> <dfn>connection</dfn> 658 649 </p> 659 < dl class="empty">660 < dd>A transport layer virtual circuit established between two programs for the purpose of communication.</dd>661 </ dl>650 <ul class="empty"> 651 <li>A transport layer virtual circuit established between two programs for the purpose of communication.</li> 652 </ul> 662 653 <p id="rfc.section.1.3.p.3"> <span id="rfc.iref.m.1"></span> <dfn>message</dfn> 663 654 </p> 664 < dl class="empty">665 < 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.666 </ dd>667 </ dl>655 <ul class="empty"> 656 <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. 657 </li> 658 </ul> 668 659 <p id="rfc.section.1.3.p.4"> <span id="rfc.iref.r.1"></span> <dfn>request</dfn> 669 660 </p> 670 < dl class="empty">671 < dd>An HTTP request message, as defined in <a href="#request" title="Request">Section 5</a>.672 </ dd>673 </ dl>661 <ul class="empty"> 662 <li>An HTTP request message, as defined in <a href="#request" title="Request">Section 5</a>. 663 </li> 664 </ul> 674 665 <p id="rfc.section.1.3.p.5"> <span id="rfc.iref.r.2"></span> <dfn>response</dfn> 675 666 </p> 676 < dl class="empty">677 < dd>An HTTP response message, as defined in <a href="#response" title="Response">Section 6</a>.678 </ dd>679 </ dl>667 <ul class="empty"> 668 <li>An HTTP response message, as defined in <a href="#response" title="Response">Section 6</a>. 669 </li> 670 </ul> 680 671 <p id="rfc.section.1.3.p.6"> <span id="rfc.iref.r.3"></span> <dfn>resource</dfn> 681 672 </p> 682 < dl class="empty">683 < 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) or673 <ul class="empty"> 674 <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 684 675 vary in other ways. 685 </ dd>686 </ dl>676 </li> 677 </ul> 687 678 <p id="rfc.section.1.3.p.7"> <span id="rfc.iref.e.1"></span> <dfn>entity</dfn> 688 679 </p> 689 < dl class="empty">690 < dd>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of680 <ul class="empty"> 681 <li>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of 691 682 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>. 692 </ dd>693 </ dl>683 </li> 684 </ul> 694 685 <p id="rfc.section.1.3.p.8"> <span id="rfc.iref.r.4"></span> <dfn>representation</dfn> 695 686 </p> 696 < dl class="empty">697 < 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.698 </ dd>699 </ dl>687 <ul class="empty"> 688 <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. 689 </li> 690 </ul> 700 691 <p id="rfc.section.1.3.p.9"> <span id="rfc.iref.c.2"></span> <dfn>content negotiation</dfn> 701 692 </p> 702 < dl class="empty">703 < 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).704 </ dd>705 </ dl>693 <ul class="empty"> 694 <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). 695 </li> 696 </ul> 706 697 <p id="rfc.section.1.3.p.10"> <span id="rfc.iref.v.1"></span> <dfn>variant</dfn> 707 698 </p> 708 < dl class="empty">709 < dd>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations699 <ul class="empty"> 700 <li>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations 710 701 is termed a `variant'. Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation. 711 </ dd>712 </ dl>702 </li> 703 </ul> 713 704 <p id="rfc.section.1.3.p.11"> <span id="rfc.iref.c.3"></span> <dfn>client</dfn> 714 705 </p> 715 < dl class="empty">716 < dd>A program that establishes connections for the purpose of sending requests.</dd>717 </ dl>706 <ul class="empty"> 707 <li>A program that establishes connections for the purpose of sending requests.</li> 708 </ul> 718 709 <p id="rfc.section.1.3.p.12"> <span id="rfc.iref.u.1"></span> <dfn>user agent</dfn> 719 710 </p> 720 < dl class="empty">721 < dd>The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user711 <ul class="empty"> 712 <li>The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user 722 713 tools. 723 </ dd>724 </ dl>714 </li> 715 </ul> 725 716 <p id="rfc.section.1.3.p.13"> <span id="rfc.iref.s.1"></span> <dfn>server</dfn> 726 717 </p> 727 < dl class="empty">728 < dd>An application program that accepts connections in order to service requests by sending back responses. Any given program718 <ul class="empty"> 719 <li>An application program that accepts connections in order to service requests by sending back responses. Any given program 729 720 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 730 721 program for a particular connection, rather than to the program's capabilities in general. Likewise, any server may act as 731 722 an origin server, proxy, gateway, or tunnel, switching behavior based on the nature of each request. 732 </ dd>733 </ dl>723 </li> 724 </ul> 734 725 <p id="rfc.section.1.3.p.14"> <span id="rfc.iref.o.1"></span> <dfn>origin server</dfn> 735 726 </p> 736 < dl class="empty">737 < dd>The server on which a given resource resides or is to be created.</dd>738 </ dl>727 <ul class="empty"> 728 <li>The server on which a given resource resides or is to be created.</li> 729 </ul> 739 730 <p id="rfc.section.1.3.p.15"> <span id="rfc.iref.p.1"></span> <dfn>proxy</dfn> 740 731 </p> 741 < dl class="empty">742 < dd>An intermediary program which acts as both a server and a client for the purpose of making requests on behalf of other clients.732 <ul class="empty"> 733 <li>An intermediary program which acts as both a server and a client for the purpose of making requests on behalf of other clients. 743 734 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 744 735 the request or response beyond what is required for proxy authentication and identification. A "non-transparent proxy" is … … 746 737 services, media type transformation, protocol reduction, or anonymity filtering. Except where either transparent or non-transparent 747 738 behavior is explicitly stated, the HTTP proxy requirements apply to both types of proxies. 748 </ dd>749 </ dl>739 </li> 740 </ul> 750 741 <p id="rfc.section.1.3.p.16"> <span id="rfc.iref.g.1"></span> <dfn>gateway</dfn> 751 742 </p> 752 < dl class="empty">753 < dd>A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the743 <ul class="empty"> 744 <li>A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the 754 745 origin server for the requested resource; the requesting client may not be aware that it is communicating with a gateway. 755 </ dd>756 </ dl>746 </li> 747 </ul> 757 748 <p id="rfc.section.1.3.p.17"> <span id="rfc.iref.t.1"></span> <dfn>tunnel</dfn> 758 749 </p> 759 < dl class="empty">760 < dd>An intermediary program which is acting as a blind relay between two connections. Once active, a tunnel is not considered750 <ul class="empty"> 751 <li>An intermediary program which is acting as a blind relay between two connections. Once active, a tunnel is not considered 761 752 a party to the HTTP communication, though the tunnel may have been initiated by an HTTP request. The tunnel ceases to exist 762 753 when both ends of the relayed connections are closed. 763 </ dd>764 </ dl>754 </li> 755 </ul> 765 756 <p id="rfc.section.1.3.p.18"> <span id="rfc.iref.c.4"></span> <dfn>cache</dfn> 766 757 </p> 767 < dl class="empty">768 < dd>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion.758 <ul class="empty"> 759 <li>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion. 769 760 A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent 770 761 requests. Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel. 771 </ dd>772 </ dl>762 </li> 763 </ul> 773 764 <p id="rfc.section.1.3.p.19"> <span id="rfc.iref.c.5"></span> <dfn>cacheable</dfn> 774 765 </p> 775 < dl class="empty">776 < dd>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.766 <ul class="empty"> 767 <li>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests. 777 768 The rules for determining the cacheability of HTTP responses are defined in <a href="p6-cache.html#caching" title="Introduction">Section 1</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. Even if a resource is cacheable, there may be additional constraints on whether a cache can use the cached copy for a particular 778 769 request. 779 </ dd>780 </ dl>770 </li> 771 </ul> 781 772 <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> 782 773 </p> 783 < dl class="empty">784 < dd>Upstream and downstream describe the flow of a message: all messages flow from upstream to downstream.</dd>785 </ dl>774 <ul class="empty"> 775 <li>Upstream and downstream describe the flow of a message: all messages flow from upstream to downstream.</li> 776 </ul> 786 777 <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> 787 778 </p> 788 < dl class="empty">789 < dd>Inbound and outbound refer to the request and response paths for messages: "inbound" means "traveling toward the origin server",779 <ul class="empty"> 780 <li>Inbound and outbound refer to the request and response paths for messages: "inbound" means "traveling toward the origin server", 790 781 and "outbound" means "traveling toward the user agent" 791 </ dd>792 </ dl>782 </li> 783 </ul> 793 784 <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> 794 785 <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, … … 857 848 </p> 858 849 <p id="rfc.section.2.1.p.2">name = definition </p> 859 < dl class="empty">860 < dd>The name of a rule is simply the name itself (without any enclosing "<" and ">") and is separated from its definition by the850 <ul class="empty"> 851 <li>The name of a rule is simply the name itself (without any enclosing "<" and ">") and is separated from its definition by the 861 852 equal "=" character. White space is only significant in that indentation of continuation lines is used to indicate a rule 862 853 definition that spans more than one line. Certain basic rules are in uppercase, such as SP, LWS, HTAB, CRLF, DIGIT, ALPHA, 863 854 etc. Angle brackets are used within definitions whenever their presence will facilitate discerning the use of rule names. 864 </ dd>865 </ dl>855 </li> 856 </ul> 866 857 <p id="rfc.section.2.1.p.3">"literal" </p> 867 < dl class="empty">868 < dd>Quotation marks surround literal text. Unless stated otherwise, the text is case-insensitive.</dd>869 </ dl>858 <ul class="empty"> 859 <li>Quotation marks surround literal text. Unless stated otherwise, the text is case-insensitive.</li> 860 </ul> 870 861 <p id="rfc.section.2.1.p.4">rule1 | rule2 </p> 871 < dl class="empty">872 < dd>Elements separated by a bar ("|") are alternatives, e.g., "yes | no" will accept yes or no.</dd>873 </ dl>862 <ul class="empty"> 863 <li>Elements separated by a bar ("|") are alternatives, e.g., "yes | no" will accept yes or no.</li> 864 </ul> 874 865 <p id="rfc.section.2.1.p.5">(rule1 rule2) </p> 875 < dl class="empty">876 < dd>Elements enclosed in parentheses are treated as a single element. Thus, "(elem (foo | bar) elem)" allows the token sequences866 <ul class="empty"> 867 <li>Elements enclosed in parentheses are treated as a single element. Thus, "(elem (foo | bar) elem)" allows the token sequences 877 868 "elem foo elem" and "elem bar elem". 878 </ dd>879 </ dl>869 </li> 870 </ul> 880 871 <p id="rfc.section.2.1.p.6">*rule </p> 881 < dl class="empty">882 < dd>The character "*" preceding an element indicates repetition. The full form is "<n>*<m>element" indicating at least <n> and872 <ul class="empty"> 873 <li>The character "*" preceding an element indicates repetition. The full form is "<n>*<m>element" indicating at least <n> and 883 874 at most <m> occurrences of element. Default values are 0 and infinity so that "*(element)" allows any number, including zero; 884 875 "1*element" requires at least one; and "1*2element" allows one or two. 885 </ dd>886 </ dl>876 </li> 877 </ul> 887 878 <p id="rfc.section.2.1.p.7">[rule] </p> 888 < dl class="empty">889 < dd>Square brackets enclose optional elements; "[foo bar]" is equivalent to "*1(foo bar)".</dd>890 </ dl>879 <ul class="empty"> 880 <li>Square brackets enclose optional elements; "[foo bar]" is equivalent to "*1(foo bar)".</li> 881 </ul> 891 882 <p id="rfc.section.2.1.p.8">N rule </p> 892 < dl class="empty">893 < dd>Specific repetition: "<n>(element)" is equivalent to "<n>*<n>(element)"; that is, exactly <n> occurrences of (element). Thus883 <ul class="empty"> 884 <li>Specific repetition: "<n>(element)" is equivalent to "<n>*<n>(element)"; that is, exactly <n> occurrences of (element). Thus 894 885 2DIGIT is a 2-digit number, and 3ALPHA is a string of three alphabetic characters. 895 </ dd>896 </ dl>886 </li> 887 </ul> 897 888 <p id="rfc.section.2.1.p.9">#rule </p> 898 < dl class="empty">899 < dd>A construct "#" is defined, similar to "*", for defining lists of elements. The full form is "<n>#<m>element" indicating at889 <ul class="empty"> 890 <li>A construct "#" is defined, similar to "*", for defining lists of elements. The full form is "<n>#<m>element" indicating at 900 891 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 901 </ dd>902 < dd>( *LWS element *( *LWS "," *LWS element ))</dd>903 < dd>can be shown as</dd>904 < dd>1#element</dd>905 < dd>Wherever this construct is used, null elements are allowed, but do not contribute to the count of elements present. That is,892 </li> 893 <li>( *LWS element *( *LWS "," *LWS element ))</li> 894 <li>can be shown as</li> 895 <li>1#element</li> 896 <li>Wherever this construct is used, null elements are allowed, but do not contribute to the count of elements present. That is, 906 897 "(element), , (element) " is permitted, but counts as only two elements. Therefore, where at least one element is required, 907 898 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 908 899 least one; and "1#2element" allows one or two. 909 </ dd>910 </ dl>900 </li> 901 </ul> 911 902 <p id="rfc.section.2.1.p.10">; comment </p> 912 < dl class="empty">913 < 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 is903 <ul class="empty"> 904 <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 914 905 a simple way of including useful notes in parallel with the specifications. 915 </ dd>916 </ dl>906 </li> 907 </ul> 917 908 <p id="rfc.section.2.1.p.11">implied *LWS </p> 918 < dl class="empty">919 < dd>The grammar described by this specification is word-based. Except where noted otherwise, linear white space (LWS) can be included909 <ul class="empty"> 910 <li>The grammar described by this specification is word-based. Except where noted otherwise, linear white space (LWS) can be included 920 911 between any two adjacent words (token or quoted-string), and between adjacent words and separators, without changing the interpretation 921 912 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 922 913 token. 923 </ dd>924 </ dl>914 </li> 915 </ul> 925 916 <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> 926 917 <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 … … 1005 996 </p> 1006 997 <p id="rfc.section.3.1.p.9"> </p> 1007 < dl class="empty">1008 < dd> <b>Note:</b> Converting between versions of HTTP may involve modification of header fields required or forbidden by the versions involved.1009 </ dd>1010 </ dl>998 <ul class="empty"> 999 <li> <b>Note:</b> Converting between versions of HTTP may involve modification of header fields required or forbidden by the versions involved. 1000 </li> 1001 </ul> 1011 1002 <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> 1012 1003 <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, … … 1022 1013 </p> 1023 1014 <p id="rfc.section.3.2.1.p.3"> </p> 1024 < dl class="empty">1025 < dd> <b>Note:</b> Servers ought to be cautious about depending on URI lengths above 255 bytes, because some older client or proxy implementations1015 <ul class="empty"> 1016 <li> <b>Note:</b> Servers ought to be cautious about depending on URI lengths above 255 bytes, because some older client or proxy implementations 1026 1017 might not properly support these lengths. 1027 </ dd>1028 </ dl>1018 </li> 1019 </ul> 1029 1020 <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> 1030 1021 <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 … … 1061 1052 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. 1062 1053 </p> 1063 < dl class="empty">1064 < 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,1054 <ul class="empty"> 1055 <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, 1065 1056 as is sometimes the case when retrieving or posting messages via proxies/gateways to SMTP or NNTP. 1066 </ dd>1067 </ dl>1057 </li> 1058 </ul> 1068 1059 <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 1069 1060 Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as the three-letter abbreviation for … … 1270 1261 byte-range specifiers from a 1.1 client implies that the client can parse multipart/byteranges responses. 1271 1262 </p> 1272 < dl class="empty">1273 < 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.1274 </ dd>1275 </ dl>1263 <ul class="empty"> 1264 <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. 1265 </li> 1266 </ul> 1276 1267 </li> 1277 1268 <li> … … 1363 1354 </p> 1364 1355 <p id="rfc.section.5.1.2.p.14"> </p> 1365 < dl class="empty">1366 < dd> <b>Note:</b> The "no rewrite" rule prevents the proxy from changing the meaning of the request when the origin server is improperly using1356 <ul class="empty"> 1357 <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 1367 1358 a non-reserved URI character for a reserved purpose. Implementors should be aware that some pre-HTTP/1.1 proxies have been 1368 1359 known to rewrite the Request-URI. 1369 </ dd>1370 </ dl>1360 </li> 1361 </ul> 1371 1362 <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> 1372 1363 <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> … … 1954 1945 <h2 id="rfc.references.1"><a href="#rfc.section.12.1" id="rfc.section.12.1">12.1</a> Normative References 1955 1946 </h2> 1956 <table summary="Normative References">1947 <table> 1957 1948 <tr> 1958 1949 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> 1959 <td class="top">International Organization for Standardization, “ 1960 Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1 1961 ”, ISO/IEC 8859-1:1998, 1998. 1962 </td> 1950 <td class="top">International Organization for Standardization, “Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1”, ISO/IEC 8859-1:1998, 1998.</td> 1963 1951 </tr> 1964 1952 <tr> 1965 1953 <td class="reference"><b id="Part2">[Part2]</b></td> 1966 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-01">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-01 (work in progress), January 2008.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>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-01">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-01 (work in progress), January 2008. 1967 1955 </td> 1968 1956 </tr> 1969 1957 <tr> 1970 1958 <td class="reference"><b id="Part3">[Part3]</b></td> 1971 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-01">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-01 (work in progress), January 2008.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>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-01">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-01 (work in progress), January 2008. 1972 1960 </td> 1973 1961 </tr> 1974 1962 <tr> 1975 1963 <td class="reference"><b id="Part5">[Part5]</b></td> 1976 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-01">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-01 (work in progress), January 2008.1964 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-01">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft draft-ietf-httpbis-p5-range-01 (work in progress), January 2008. 1977 1965 </td> 1978 1966 </tr> 1979 1967 <tr> 1980 1968 <td class="reference"><b id="Part6">[Part6]</b></td> 1981 <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-01">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-01 (work in progress), January 2008.1969 <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-01">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-01 (work in progress), January 2008. 1982 1970 </td> 1983 1971 </tr> 1984 1972 <tr> 1985 1973 <td class="reference"><b id="RFC2045">[RFC2045]</b></td> 1986 <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.1974 <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. 1987 1975 </td> 1988 1976 </tr> 1989 1977 <tr> 1990 1978 <td class="reference"><b id="RFC2047">[RFC2047]</b></td> 1991 <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.1979 <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. 1992 1980 </td> 1993 1981 </tr> 1994 1982 <tr> 1995 1983 <td class="reference"><b id="RFC2119">[RFC2119]</b></td> 1996 <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.1984 <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP 14, RFC 2119, March 1997. 1997 1985 </td> 1998 1986 </tr> 1999 1987 <tr> 2000 1988 <td class="reference"><b id="RFC2396">[RFC2396]</b></td> 2001 <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.1989 <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. 2002 1990 </td> 2003 1991 </tr> 2004 1992 <tr> 2005 1993 <td class="reference"><b id="RFC4288">[RFC4288]</b></td> 2006 <td class="top"><a title="Sun Microsystems">Freed, N.</a> and <a>J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP 13, RFC 4288, December 2005.1994 <td class="top"><a href="mailto:ned.freed@mrochek.com" title="Sun Microsystems">Freed, N.</a> and <a href="mailto:klensin+ietf@jck.com">J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP 13, RFC 4288, December 2005. 2007 1995 </td> 2008 1996 </tr> 2009 1997 <tr> 2010 1998 <td class="reference"><b id="RFC822ABNF">[RFC822ABNF]</b></td> 2011 <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.1999 <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. 2012 2000 </td> 2013 2001 </tr> … … 2019 2007 <h2 id="rfc.references.2"><a href="#rfc.section.12.2" id="rfc.section.12.2">12.2</a> Informative References 2020 2008 </h2> 2021 <table summary="Informative References">2009 <table> 2022 2010 <tr> 2023 2011 <td class="reference"><b id="Nie1997">[Nie1997]</b></td> 2024 <td class="top">Nielsen, H. F.., Gettys, J., Prud'hommeaux, E., Lie, H., and C. Lilley, “<a href="http://doi.acm.org/10.1145/263105.263157">Network Performance Effects of HTTP/1.1, CSS1, and PNG</a>”, ACM Proceedings of the ACM SIGCOMM '97 conference on Applications, technologies, architectures, and protocols for computer communication2012 <td class="top">Nielsen, H., Gettys, J., Prud'hommeaux, E., Lie, H., and C. Lilley, “<a href="http://doi.acm.org/10.1145/263105.263157">Network Performance Effects of HTTP/1.1, CSS1, and PNG</a>”, ACM Proceedings of the ACM SIGCOMM '97 conference on Applications, technologies, architectures, and protocols for computer communication 2025 2013 SIGCOMM '97, September 1997, <<a href="http://doi.acm.org/10.1145/263105.263157">http://doi.acm.org/10.1145/263105.263157</a>>. 2026 2014 </td> … … 2028 2016 <tr> 2029 2017 <td class="reference"><b id="Pad1995">[Pad1995]</b></td> 2030 <td class="top">Padmanabhan, V. N. and J.C. Mogul, “Improving HTTP Latency”, Computer Networks and ISDN Systems v. 28, pp. 25-35, December 1995.<br>Slightly revised version of paper in Proc. 2nd International WWW Conference '94: Mosaic and the Web, Oct. 1994, which is available2018 <td class="top">Padmanabhan, V. and J. Mogul, “Improving HTTP Latency”, Computer Networks and ISDN Systems v. 28, pp. 25-35, December 1995.<br>Slightly revised version of paper in Proc. 2nd International WWW Conference '94: Mosaic and the Web, Oct. 1994, which is available 2031 2019 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>>. 2032 2020 </td> … … 2034 2022 <tr> 2035 2023 <td class="reference"><b id="RFC1123">[RFC1123]</b></td> 2036 <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.2024 <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. 2037 2025 </td> 2038 2026 </tr> 2039 2027 <tr> 2040 2028 <td class="reference"><b id="RFC1305">[RFC1305]</b></td> 2041 <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.2029 <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. 2042 2030 </td> 2043 2031 </tr> 2044 2032 <tr> 2045 2033 <td class="reference"><b id="RFC1436">[RFC1436]</b></td> 2046 <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.2034 <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. 2047 2035 </td> 2048 2036 </tr> 2049 2037 <tr> 2050 2038 <td class="reference"><b id="RFC1630">[RFC1630]</b></td> 2051 <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 Network2039 <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 2052 2040 as used in the World-Wide Web</a>”, RFC 1630, June 1994. 2053 2041 </td> … … 2055 2043 <tr> 2056 2044 <td class="reference"><b id="RFC1737">[RFC1737]</b></td> 2057 <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.2045 <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. 2058 2046 </td> 2059 2047 </tr> 2060 2048 <tr> 2061 2049 <td class="reference"><b id="RFC1738">[RFC1738]</b></td> 2062 <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.2050 <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. 2063 2051 </td> 2064 2052 </tr> 2065 2053 <tr> 2066 2054 <td class="reference"><b id="RFC1808">[RFC1808]</b></td> 2067 <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.2055 <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. 2068 2056 </td> 2069 2057 </tr> 2070 2058 <tr> 2071 2059 <td class="reference"><b id="RFC1900">[RFC1900]</b></td> 2072 <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.2060 <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. 2073 2061 </td> 2074 2062 </tr> 2075 2063 <tr> 2076 2064 <td class="reference"><b id="RFC1945">[RFC1945]</b></td> 2077 <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.2065 <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. 2078 2066 </td> 2079 2067 </tr> 2080 2068 <tr> 2081 2069 <td class="reference"><b id="RFC2068">[RFC2068]</b></td> 2082 <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.2070 <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. 2083 2071 </td> 2084 2072 </tr> 2085 2073 <tr> 2086 2074 <td class="reference"><b id="RFC2145">[RFC2145]</b></td> 2087 <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.2075 <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. 2088 2076 </td> 2089 2077 </tr> 2090 2078 <tr> 2091 2079 <td class="reference"><b id="RFC2324">[RFC2324]</b></td> 2092 <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.2080 <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. 2093 2081 </td> 2094 2082 </tr> 2095 2083 <tr> 2096 2084 <td class="reference"><b id="RFC2616">[RFC2616]</b></td> 2097 <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.2085 <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. 2098 2086 </td> 2099 2087 </tr> 2100 2088 <tr> 2101 2089 <td class="reference"><b id="RFC2821">[RFC2821]</b></td> 2102 <td class="top"><a title="AT&T Laboratories">Klensin, J.</a>, “<a href="http://tools.ietf.org/html/rfc2821">Simple Mail Transfer Protocol</a>”, RFC 2821, April 2001.2090 <td class="top"><a href="mailto:klensin@research.att.com" title="AT&T Laboratories">Klensin, J.</a>, “<a href="http://tools.ietf.org/html/rfc2821">Simple Mail Transfer Protocol</a>”, RFC 2821, April 2001. 2103 2091 </td> 2104 2092 </tr> … … 2110 2098 <tr> 2111 2099 <td class="reference"><b id="RFC3977">[RFC3977]</b></td> 2112 <td class="top"><a title="THUS plc">Feather, C.</a>, “<a href="http://tools.ietf.org/html/rfc3977">Network News Transfer Protocol (NNTP)</a>”, RFC 3977, October 2006.2100 <td class="top"><a href="mailto:clive@demon.net" title="THUS plc">Feather, C.</a>, “<a href="http://tools.ietf.org/html/rfc3977">Network News Transfer Protocol (NNTP)</a>”, RFC 3977, October 2006. 2113 2101 </td> 2114 2102 </tr> 2115 2103 <tr> 2116 2104 <td class="reference"><b id="RFC822">[RFC822]</b></td> 2117 <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.2105 <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. 2118 2106 </td> 2119 2107 </tr> … … 2130 2118 <tr> 2131 2119 <td class="reference"><b id="Tou1998">[Tou1998]</b></td> 2132 <td class="top"><a title="USC/Information Sciences Institute">Touch, J.</a>, <a title="USC/Information Sciences Institute">Heidemann, J.</a>, and <atitle="USC/Information Sciences Institute">K. Obraczka</a>, “<a href="http://www.isi.edu/touch/pubs/http-perf96/">Analysis of HTTP Performance</a>”, ISI Research Report ISI/RR-98-463, Aug 1998, <<a href="http://www.isi.edu/touch/pubs/http-perf96/">http://www.isi.edu/touch/pubs/http-perf96/</a>>.<br>(original report dated Aug. 1996)2120 <td class="top"><a href="mailto:touch@isi.edu" title="USC/Information Sciences Institute">Touch, J.</a>, <a href="mailto:johnh@isi.edu" title="USC/Information Sciences Institute">Heidemann, J.</a>, and <a href="mailto:katia@isi.edu" title="USC/Information Sciences Institute">K. Obraczka</a>, “<a href="http://www.isi.edu/touch/pubs/http-perf96/">Analysis of HTTP Performance</a>”, ISI Research Report ISI/RR-98-463, Aug 1998, <<a href="http://www.isi.edu/touch/pubs/http-perf96/">http://www.isi.edu/touch/pubs/http-perf96/</a>>.<br>(original report dated Aug. 1996) 2133 2121 </td> 2134 2122 </tr> … … 2138 2126 </tr> 2139 2127 </table> 2140 <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1> 2141 <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span> 2142 (editor) 2143 <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> 2144 <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> 2145 <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> 2146 <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> 2147 <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> 2148 <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> 2149 <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> 2150 <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span> 2151 (editor) 2152 <span class="n hidden"><span class="family-name">Lafon</span><span class="given-name">Yves</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">W3C / ERCIM</span><span class="street-address vcardline">2004, rte des Lucioles</span><span class="vcardline"><span class="locality">Sophia-Antipolis</span>, <span class="region">AM</span> <span class="postal-code">06902</span></span><span class="country-name vcardline">France</span></span><span class="vcardline">EMail: <a><span class="email">ylafon@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.raubacapeu.net/people/yves/" class="url">http://www.raubacapeu.net/people/yves/</a></span></address> 2153 <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span> 2154 (editor) 2155 <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span> <span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">EMail: <a><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address> 2156 <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 Types</a></h1> 2128 <div class="avoidbreak"> 2129 <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1> 2130 <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span> 2131 (editor) 2132 <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> 2133 <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> 2134 <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> 2135 <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> 2136 <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> 2137 <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> 2138 <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> 2139 <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span> 2140 (editor) 2141 <span class="n hidden"><span class="family-name">Lafon</span><span class="given-name">Yves</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">W3C / ERCIM</span><span class="street-address vcardline">2004, rte des Lucioles</span><span class="vcardline"><span class="locality">Sophia-Antipolis</span>, <span class="region">AM</span> <span class="postal-code">06902</span></span><span class="country-name vcardline">France</span></span><span class="vcardline">EMail: <a href="mailto:ylafon@w3.org"><span class="email">ylafon@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.raubacapeu.net/people/yves/" class="url">http://www.raubacapeu.net/people/yves/</a></span></address> 2142 <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span> 2143 (editor) 2144 <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span> <span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">EMail: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address> 2145 </div> 2146 <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 Types</a></h1> 2157 2147 <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" 2158 2148 and "application/http". The following is to be registered with IANA <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>. … … 2439 2429 </li> 2440 2430 </ul> 2431 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 2432 <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> 2433 </p> 2434 <div class="print2col"> 2435 <ul class="ind"> 2436 <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul> 2437 <li>application/http Media Type <a href="#rfc.iref.a.1"><b>A.2</b></a></li> 2438 </ul> 2439 </li> 2440 <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul> 2441 <li>cache <a href="#rfc.iref.c.4">1.3</a></li> 2442 <li>cacheable <a href="#rfc.iref.c.5">1.3</a></li> 2443 <li>client <a href="#rfc.iref.c.3">1.3</a></li> 2444 <li>connection <a href="#rfc.iref.c.1">1.3</a></li> 2445 <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>, <a href="#rfc.xref.header.connection.7">D.4</a></li> 2446 <li>content negotiation <a href="#rfc.iref.c.2">1.3</a></li> 2447 <li>Content-Length header <a href="#rfc.xref.header.content-length.1">4.4</a>, <a href="#rfc.iref.c.7"><b>8.2</b></a>, <a href="#rfc.xref.header.content-length.2">D.3</a></li> 2448 </ul> 2449 </li> 2450 <li><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul> 2451 <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> 2452 <li>downstream <a href="#rfc.iref.d.1">1.3</a></li> 2453 </ul> 2454 </li> 2455 <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul> 2456 <li>entity <a href="#rfc.iref.e.1">1.3</a></li> 2457 </ul> 2458 </li> 2459 <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul> 2460 <li>gateway <a href="#rfc.iref.g.1">1.3</a></li> 2461 <li><tt>Grammar</tt> 2462 <ul> 2463 <li><tt>ALPHA</tt> <a href="#rfc.iref.g.6"><b>2.2</b></a></li> 2464 <li><tt>asctime-date</tt> <a href="#rfc.iref.g.30"><b>3.3.1</b></a></li> 2465 <li><tt>attribute</tt> <a href="#rfc.iref.g.41"><b>3.4</b></a></li> 2466 <li><tt>CHAR</tt> <a href="#rfc.iref.g.3"><b>2.2</b></a></li> 2467 <li><tt>chunk</tt> <a href="#rfc.iref.g.44"><b>3.4.1</b></a></li> 2468 <li><tt>chunk-data</tt> <a href="#rfc.iref.g.50"><b>3.4.1</b></a></li> 2469 <li><tt>chunk-ext-name</tt> <a href="#rfc.iref.g.48"><b>3.4.1</b></a></li> 2470 <li><tt>chunk-ext-val</tt> <a href="#rfc.iref.g.49"><b>3.4.1</b></a></li> 2471 <li><tt>chunk-extension</tt> <a href="#rfc.iref.g.47"><b>3.4.1</b></a></li> 2472 <li><tt>chunk-size</tt> <a href="#rfc.iref.g.45"><b>3.4.1</b></a></li> 2473 <li><tt>Chunked-Body</tt> <a href="#rfc.iref.g.43"><b>3.4.1</b></a></li> 2474 <li><tt>comment</tt> <a href="#rfc.iref.g.20"><b>2.2</b></a></li> 2475 <li><tt>Connection</tt> <a href="#rfc.iref.g.71"><b>8.1</b></a></li> 2476 <li><tt>connection-token</tt> <a href="#rfc.iref.g.72"><b>8.1</b></a></li> 2477 <li><tt>Content-Length</tt> <a href="#rfc.iref.g.73"><b>8.2</b></a></li> 2478 <li><tt>CR</tt> <a href="#rfc.iref.g.9"><b>2.2</b></a></li> 2479 <li><tt>CRLF</tt> <a href="#rfc.iref.g.14"><b>2.2</b></a></li> 2480 <li><tt>ctext</tt> <a href="#rfc.iref.g.21"><b>2.2</b></a></li> 2481 <li><tt>CTL</tt> <a href="#rfc.iref.g.8"><b>2.2</b></a></li> 2482 <li><tt>Date</tt> <a href="#rfc.iref.g.74"><b>8.3</b></a></li> 2483 <li><tt>date1</tt> <a href="#rfc.iref.g.31"><b>3.3.1</b></a></li> 2484 <li><tt>date2</tt> <a href="#rfc.iref.g.32"><b>3.3.1</b></a></li> 2485 <li><tt>date3</tt> <a href="#rfc.iref.g.33"><b>3.3.1</b></a></li> 2486 <li><tt>DIGIT</tt> <a href="#rfc.iref.g.7"><b>2.2</b></a></li> 2487 <li><tt>DQUOTE</tt> <a href="#rfc.iref.g.13"><b>2.2</b></a></li> 2488 <li><tt>extension-code</tt> <a href="#rfc.iref.g.69"><b>6.1.1</b></a></li> 2489 <li><tt>extension-method</tt> <a href="#rfc.iref.g.64"><b>5.1.1</b></a></li> 2490 <li><tt>field-content</tt> <a href="#rfc.iref.g.58"><b>4.2</b></a></li> 2491 <li><tt>field-name</tt> <a href="#rfc.iref.g.56"><b>4.2</b></a></li> 2492 <li><tt>field-value</tt> <a href="#rfc.iref.g.57"><b>4.2</b></a></li> 2493 <li><tt>general-header</tt> <a href="#rfc.iref.g.60"><b>4.5</b></a></li> 2494 <li><tt>generic-message</tt> <a href="#rfc.iref.g.53"><b>4.1</b></a></li> 2495 <li><tt>HEX</tt> <a href="#rfc.iref.g.17"><b>2.2</b></a></li> 2496 <li><tt>Host</tt> <a href="#rfc.iref.g.75"><b>8.4</b></a></li> 2497 <li><tt>HTAB</tt> <a href="#rfc.iref.g.12"><b>2.2</b></a></li> 2498 <li><tt>HTTP-date</tt> <a href="#rfc.iref.g.27"><b>3.3.1</b></a></li> 2499 <li><tt>HTTP-message</tt> <a href="#rfc.iref.g.52"><b>4.1</b></a></li> 2500 <li><tt>HTTP-Version</tt> <a href="#rfc.iref.g.25"><b>3.1</b></a></li> 2501 <li><tt>http_URL</tt> <a href="#rfc.iref.g.26"><b>3.2.2</b></a></li> 2502 <li><tt>last-chunk</tt> <a href="#rfc.iref.g.46"><b>3.4.1</b></a></li> 2503 <li><tt>LF</tt> <a href="#rfc.iref.g.10"><b>2.2</b></a></li> 2504 <li><tt>LOALPHA</tt> <a href="#rfc.iref.g.5"><b>2.2</b></a></li> 2505 <li><tt>LWS</tt> <a href="#rfc.iref.g.15"><b>2.2</b></a></li> 2506 <li><tt>message-body</tt> <a href="#rfc.iref.g.59"><b>4.3</b></a></li> 2507 <li><tt>message-header</tt> <a href="#rfc.iref.g.55"><b>4.2</b></a></li> 2508 <li><tt>Method</tt> <a href="#rfc.iref.g.63"><b>5.1.1</b></a></li> 2509 <li><tt>month</tt> <a href="#rfc.iref.g.37"><b>3.3.1</b></a></li> 2510 <li><tt>OCTET</tt> <a href="#rfc.iref.g.2"><b>2.2</b></a></li> 2511 <li><tt>parameter</tt> <a href="#rfc.iref.g.40"><b>3.4</b></a></li> 2512 <li><tt>protocol-name</tt> <a href="#rfc.iref.g.83"><b>8.9</b></a></li> 2513 <li><tt>protocol-version</tt> <a href="#rfc.iref.g.84"><b>8.9</b></a></li> 2514 <li><tt>pseudonym</tt> <a href="#rfc.iref.g.86"><b>8.9</b></a></li> 2515 <li><tt>qdtext</tt> <a href="#rfc.iref.g.23"><b>2.2</b></a></li> 2516 <li><tt>quoted-pair</tt> <a href="#rfc.iref.g.24"><b>2.2</b></a></li> 2517 <li><tt>quoted-string</tt> <a href="#rfc.iref.g.22"><b>2.2</b></a></li> 2518 <li><tt>Reason-Phrase</tt> <a href="#rfc.iref.g.70"><b>6.1.1</b></a></li> 2519 <li><tt>received-by</tt> <a href="#rfc.iref.g.85"><b>8.9</b></a></li> 2520 <li><tt>received-protocol</tt> <a href="#rfc.iref.g.82"><b>8.9</b></a></li> 2521 <li><tt>Request</tt> <a href="#rfc.iref.g.61"><b>5</b></a></li> 2522 <li><tt>Request-Line</tt> <a href="#rfc.iref.g.62"><b>5.1</b></a></li> 2523 <li><tt>Request-URI</tt> <a href="#rfc.iref.g.65"><b>5.1.2</b></a></li> 2524 <li><tt>Response</tt> <a href="#rfc.iref.g.66"><b>6</b></a></li> 2525 <li><tt>rfc1123-date</tt> <a href="#rfc.iref.g.28"><b>3.3.1</b></a></li> 2526 <li><tt>rfc850-date</tt> <a href="#rfc.iref.g.29"><b>3.3.1</b></a></li> 2527 <li><tt>separators</tt> <a href="#rfc.iref.g.19"><b>2.2</b></a></li> 2528 <li><tt>SP</tt> <a href="#rfc.iref.g.11"><b>2.2</b></a></li> 2529 <li><tt>start-line</tt> <a href="#rfc.iref.g.54"><b>4.1</b></a></li> 2530 <li><tt>Status-Code</tt> <a href="#rfc.iref.g.68"><b>6.1.1</b></a></li> 2531 <li><tt>Status-Line</tt> <a href="#rfc.iref.g.67"><b>6.1</b></a></li> 2532 <li><tt>t-codings</tt> <a href="#rfc.iref.g.77"><b>8.5</b></a></li> 2533 <li><tt>TE</tt> <a href="#rfc.iref.g.76"><b>8.5</b></a></li> 2534 <li><tt>TEXT</tt> <a href="#rfc.iref.g.16"><b>2.2</b></a></li> 2535 <li><tt>time</tt> <a href="#rfc.iref.g.34"><b>3.3.1</b></a></li> 2536 <li><tt>token</tt> <a href="#rfc.iref.g.18"><b>2.2</b></a></li> 2537 <li><tt>trailer</tt> <a href="#rfc.iref.g.51"><b>3.4.1</b></a></li> 2538 <li><tt>Trailer</tt> <a href="#rfc.iref.g.78"><b>8.6</b></a></li> 2539 <li><tt>transfer-coding</tt> <a href="#rfc.iref.g.38"><b>3.4</b></a></li> 2540 <li><tt>Transfer-Encoding</tt> <a href="#rfc.iref.g.79"><b>8.7</b></a></li> 2541 <li><tt>transfer-extension</tt> <a href="#rfc.iref.g.39"><b>3.4</b></a></li> 2542 <li><tt>UPALPHA</tt> <a href="#rfc.iref.g.4"><b>2.2</b></a></li> 2543 <li><tt>Upgrade</tt> <a href="#rfc.iref.g.80"><b>8.8</b></a></li> 2544 <li><tt>value</tt> <a href="#rfc.iref.g.42"><b>3.4</b></a></li> 2545 <li><tt>Via</tt> <a href="#rfc.iref.g.81"><b>8.9</b></a></li> 2546 <li><tt>weekday</tt> <a href="#rfc.iref.g.36"><b>3.3.1</b></a></li> 2547 <li><tt>wkday</tt> <a href="#rfc.iref.g.35"><b>3.3.1</b></a></li> 2548 </ul> 2549 </li> 2550 </ul> 2551 </li> 2552 <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul> 2553 <li>Headers 2554 <ul> 2555 <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>, <a href="#rfc.xref.header.connection.7">D.4</a></li> 2556 <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>, <a href="#rfc.xref.header.content-length.2">D.3</a></li> 2557 <li>Date <a href="#rfc.xref.header.date.1">4.5</a>, <a href="#rfc.iref.h.3"><b>8.3</b></a></li> 2558 <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> 2559 <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> 2560 <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> 2561 <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> 2562 <li>Upgrade <a href="#rfc.xref.header.upgrade.1">4.5</a>, <a href="#rfc.iref.h.9"><b>8.8</b></a></li> 2563 <li>Via <a href="#rfc.xref.header.via.1">4.5</a>, <a href="#rfc.iref.h.10"><b>8.9</b></a></li> 2564 </ul> 2565 </li> 2566 <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> 2567 </ul> 2568 </li> 2569 <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul> 2570 <li>inbound <a href="#rfc.iref.i.1">1.3</a></li> 2571 <li><em>ISO-8859-1</em> <a href="#rfc.xref.ISO-8859-1.1">2.2</a>, <a href="#ISO-8859-1"><b>12.1</b></a></li> 2572 </ul> 2573 </li> 2574 <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul> 2575 <li>Media Type 2576 <ul> 2577 <li>application/http <a href="#rfc.iref.m.4"><b>A.2</b></a></li> 2578 <li>message/http <a href="#rfc.iref.m.2"><b>A.1</b></a></li> 2579 </ul> 2580 </li> 2581 <li>message <a href="#rfc.iref.m.1">1.3</a></li> 2582 <li>message/http Media Type <a href="#rfc.iref.m.3"><b>A.1</b></a></li> 2583 </ul> 2584 </li> 2585 <li><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul> 2586 <li><em>Nie1997</em> <a href="#rfc.xref.Nie1997.1">7.1.1</a>, <a href="#Nie1997"><b>12.2</b></a>, <a href="#rfc.xref.Nie1997.2">D.3</a></li> 2587 </ul> 2588 </li> 2589 <li><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul> 2590 <li>origin server <a href="#rfc.iref.o.1">1.3</a></li> 2591 <li>outbound <a href="#rfc.iref.o.2">1.3</a></li> 2592 </ul> 2593 </li> 2594 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 2595 <li><em>Pad1995</em> <a href="#rfc.xref.Pad1995.1">7.1.1</a>, <a href="#Pad1995"><b>12.2</b></a></li> 2596 <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.1</b></a><ul> 2597 <li><em>Section 3</em> <a href="#rfc.xref.Part2.4">4.3</a></li> 2598 <li><em>Section 4</em> <a href="#rfc.xref.Part2.2">4.2</a>, <a href="#rfc.xref.Part2.5">5</a></li> 2599 <li><em>Section 6</em> <a href="#rfc.xref.Part2.3">4.2</a>, <a href="#rfc.xref.Part2.7">6</a></li> 2600 <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> 2601 <li><em>Section 8.9</em> <a href="#rfc.xref.Part2.6">5.1.2</a></li> 2602 <li><em>Section 9</em> <a href="#rfc.xref.Part2.8">6.1.1</a></li> 2603 <li><em>Section 9.1.1</em> <a href="#rfc.xref.Part2.11">7.2.3</a></li> 2604 <li><em>Section 9.1</em> <a href="#rfc.xref.Part2.14">7.2.3</a></li> 2605 <li><em>Section 9.4.15</em> <a href="#rfc.xref.Part2.1">3.2.1</a></li> 2606 <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> 2607 </ul> 2608 </li> 2609 <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">4.2</a>, <a href="#rfc.xref.Part3.9">5</a>, <a href="#rfc.xref.Part3.10">6</a>, <a href="#rfc.xref.Part3.11">8.5</a>, <a href="#Part3"><b>12.1</b></a>, <a href="#rfc.xref.Part3.12">B</a>, <a href="#rfc.xref.Part3.13">D.3</a><ul> 2610 <li><em>Section 2.2</em> <a href="#rfc.xref.Part3.6">3.4</a>, <a href="#rfc.xref.Part3.7">3.4</a></li> 2611 <li><em>Section 2.3</em> <a href="#rfc.xref.Part3.5">2.2</a></li> 2612 <li><em>Section 2.4</em> <a href="#rfc.xref.Part3.11">8.5</a></li> 2613 <li><em>Section 3</em> <a href="#rfc.xref.Part3.1">1.3</a></li> 2614 <li><em>Section 3.1</em> <a href="#rfc.xref.Part3.8">4.2</a>, <a href="#rfc.xref.Part3.9">5</a>, <a href="#rfc.xref.Part3.10">6</a></li> 2615 <li><em>Section 4</em> <a href="#rfc.xref.Part3.2">1.3</a>, <a href="#rfc.xref.Part3.3">1.3</a></li> 2616 <li><em>Appendix A</em> <a href="#rfc.xref.Part3.4">1.4</a></li> 2617 </ul> 2618 </li> 2619 <li><em>Part5</em> <a href="#Part5"><b>12.1</b></a>, <a href="#rfc.xref.Part5.1">D.3</a></li> 2620 <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.1</b></a>, <a href="#rfc.xref.Part6.6">D.3</a><ul> 2621 <li><em>Section 1</em> <a href="#rfc.xref.Part6.1">1.3</a>, <a href="#rfc.xref.Part6.2">1.4</a></li> 2622 <li><em>Section 15.2</em> <a href="#rfc.xref.Part6.3">4.5</a></li> 2623 <li><em>Section 15.4</em> <a href="#rfc.xref.Part6.4">4.5</a></li> 2624 <li><em>Section 15.6</em> <a href="#rfc.xref.Part6.5">4.5</a></li> 2625 </ul> 2626 </li> 2627 <li>proxy <a href="#rfc.iref.p.1">1.3</a></li> 2628 </ul> 2629 </li> 2630 <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul> 2631 <li>representation <a href="#rfc.iref.r.4">1.3</a></li> 2632 <li>request <a href="#rfc.iref.r.1">1.3</a></li> 2633 <li>resource <a href="#rfc.iref.r.3">1.3</a></li> 2634 <li>response <a href="#rfc.iref.r.2">1.3</a></li> 2635 <li><em>RFC1123</em> <a href="#rfc.xref.RFC1123.1">3.3.1</a>, <a href="#RFC1123"><b>12.2</b></a></li> 2636 <li><em>RFC1305</em> <a href="#rfc.xref.RFC1305.1">8.3</a>, <a href="#RFC1305"><b>12.2</b></a></li> 2637 <li><em>RFC1436</em> <a href="#rfc.xref.RFC1436.1">1.1</a>, <a href="#RFC1436"><b>12.2</b></a></li> 2638 <li><em>RFC1630</em> <a href="#rfc.xref.RFC1630.1">1.1</a>, <a href="#rfc.xref.RFC1630.2">3.2</a>, <a href="#RFC1630"><b>12.2</b></a></li> 2639 <li><em>RFC1737</em> <a href="#rfc.xref.RFC1737.1">1.1</a>, <a href="#rfc.xref.RFC1737.2">3.2</a>, <a href="#RFC1737"><b>12.2</b></a></li> 2640 <li><em>RFC1738</em> <a href="#rfc.xref.RFC1738.1">1.1</a>, <a href="#rfc.xref.RFC1738.2">3.2</a>, <a href="#rfc.xref.RFC1738.3">3.2.1</a>, <a href="#RFC1738"><b>12.2</b></a></li> 2641 <li><em>RFC1808</em> <a href="#rfc.xref.RFC1808.1">3.2.1</a>, <a href="#rfc.xref.RFC1808.2">3.2.1</a>, <a href="#RFC1808"><b>12.2</b></a></li> 2642 <li><em>RFC1900</em> <a href="#rfc.xref.RFC1900.1">3.2.2</a>, <a href="#rfc.xref.RFC1900.2">10.4</a>, <a href="#RFC1900"><b>12.2</b></a></li> 2643 <li><em>RFC1945</em> <a href="#rfc.xref.RFC1945.1">1</a>, <a href="#RFC1945"><b>12.2</b></a></li> 2644 <li><em>RFC2045</em> <a href="#rfc.xref.RFC2045.1">1.1</a>, <a href="#rfc.xref.RFC2045.2">3.4</a>, <a href="#rfc.xref.RFC2045.3">11</a>, <a href="#RFC2045"><b>12.1</b></a></li> 2645 <li><em>RFC2047</em> <a href="#rfc.xref.RFC2047.1">2.2</a>, <a href="#RFC2047"><b>12.1</b></a></li> 2646 <li><em>RFC2068</em> <a href="#rfc.xref.RFC2068.1">3.1</a>, <a href="#rfc.xref.RFC2068.2">7.1.1</a>, <a href="#rfc.xref.RFC2068.3">7.1.3</a>, <a href="#rfc.xref.RFC2068.4">7.2.3</a>, <a href="#rfc.xref.RFC2068.5">11</a>, <a href="#RFC2068"><b>12.2</b></a>, <a href="#rfc.xref.RFC2068.6">D</a>, <a href="#rfc.xref.RFC2068.7">D.2</a><ul> 2647 <li><em>Section 19.7.1</em> <a href="#rfc.xref.RFC2068.6">D</a></li> 2648 </ul> 2649 </li> 2650 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.2</a>, <a href="#RFC2119"><b>12.1</b></a>, <a href="#rfc.xref.RFC2119.2">D.3</a></li> 2651 <li><em>RFC2145</em> <a href="#rfc.xref.RFC2145.1">3.1</a>, <a href="#rfc.xref.RFC2145.2">3.1</a>, <a href="#RFC2145"><b>12.2</b></a>, <a href="#rfc.xref.RFC2145.3">D.3</a></li> 2652 <li><em>RFC2324</em> <a href="#rfc.xref.RFC2324.1">1.1</a>, <a href="#RFC2324"><b>12.2</b></a></li> 2653 <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.1</b></a>, <a href="#rfc.xref.RFC2396.4">D.4</a><ul> 2654 <li><em>Section 3</em> <a href="#rfc.xref.RFC2396.4">D.4</a></li> 2655 </ul> 2656 </li> 2657 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">1</a>, <a href="#rfc.xref.RFC2616.3">11</a>, <a href="#RFC2616"><b>12.2</b></a>, <a href="#rfc.xref.RFC2616.4">E.1</a></li> 2658 <li><em>RFC2821</em> <a href="#rfc.xref.RFC2821.1">1.1</a>, <a href="#RFC2821"><b>12.2</b></a></li> 2659 <li><em>RFC2822</em> <a href="#rfc.xref.RFC2822.1">1.1</a>, <a href="#rfc.xref.RFC2822.2">4.1</a>, <a href="#rfc.xref.RFC2822.3">4.2</a>, <a href="#rfc.xref.RFC2822.4">8.3</a>, <a href="#rfc.xref.RFC2822.5">8.9</a>, <a href="#RFC2822"><b>12.2</b></a><ul> 2660 <li><em>Section 2.1</em> <a href="#rfc.xref.RFC2822.3">4.2</a></li> 2661 <li><em>Section 3.6.1</em> <a href="#rfc.xref.RFC2822.4">8.3</a></li> 2662 </ul> 2663 </li> 2664 <li><em>RFC3977</em> <a href="#rfc.xref.RFC3977.1">1.1</a>, <a href="#RFC3977"><b>12.2</b></a></li> 2665 <li><em>RFC4288</em> <a href="#RFC4288"><b>12.1</b></a>, <a href="#rfc.xref.RFC4288.1">A</a></li> 2666 <li><em>RFC822</em> <a href="#rfc.xref.RFC822.1">3.3.1</a>, <a href="#RFC822"><b>12.2</b></a></li> 2667 <li><em>RFC822ABNF</em> <a href="#rfc.xref.RFC822ABNF.1">2.1</a>, <a href="#rfc.xref.RFC822ABNF.2">11</a>, <a href="#RFC822ABNF"><b>12.1</b></a></li> 2668 <li><em>RFC959</em> <a href="#rfc.xref.RFC959.1">1.1</a>, <a href="#RFC959"><b>12.2</b></a></li> 2669 </ul> 2670 </li> 2671 <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul> 2672 <li>server <a href="#rfc.iref.s.1">1.3</a></li> 2673 <li><em>Spe</em> <a href="#rfc.xref.Spe.1">7.1.1</a>, <a href="#Spe"><b>12.2</b></a></li> 2674 </ul> 2675 </li> 2676 <li><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul> 2677 <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> 2678 <li><em>Tou1998</em> <a href="#rfc.xref.Tou1998.1">7.1.1</a>, <a href="#Tou1998"><b>12.2</b></a></li> 2679 <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> 2680 <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> 2681 <li>tunnel <a href="#rfc.iref.t.1">1.3</a></li> 2682 </ul> 2683 </li> 2684 <li><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul> 2685 <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> 2686 <li>upstream <a href="#rfc.iref.u.2">1.3</a></li> 2687 <li><em>USASCII</em> <a href="#rfc.xref.USASCII.1">2.2</a>, <a href="#USASCII"><b>12.1</b></a></li> 2688 <li>user agent <a href="#rfc.iref.u.1">1.3</a></li> 2689 </ul> 2690 </li> 2691 <li><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul> 2692 <li>variant <a href="#rfc.iref.v.1">1.3</a></li> 2693 <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> 2694 </ul> 2695 </li> 2696 <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul> 2697 <li><em>WAIS</em> <a href="#rfc.xref.WAIS.1">1.1</a>, <a href="#WAIS"><b>12.2</b></a></li> 2698 </ul> 2699 </li> 2700 </ul> 2701 </div> 2441 2702 <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> 2703 <p>Copyright © The IETF Trust (2008).</p> 2442 2704 <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the 2443 2705 authors retain all their rights. … … 2457 2719 <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result 2458 2720 of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users 2459 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>>.2721 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>. 2460 2722 </p> 2461 2723 <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary … … 2463 2725 at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>. 2464 2726 </p> 2465 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>2466 <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>2467 </p>2468 <div class="print2col">2469 <ul class="ind">2470 <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind">2471 <li class="indline1">application/http Media Type <a class="iref" href="#rfc.iref.a.1"><b>A.2</b></a></li>2472 </ul>2473 </li>2474 <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">2475 <li class="indline1">cache <a class="iref" href="#rfc.iref.c.4">1.3</a></li>2476 <li class="indline1">cacheable <a class="iref" href="#rfc.iref.c.5">1.3</a></li>2477 <li class="indline1">client <a class="iref" href="#rfc.iref.c.3">1.3</a></li>2478 <li class="indline1">connection <a class="iref" href="#rfc.iref.c.1">1.3</a></li>2479 <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>, <a class="iref" href="#rfc.xref.header.connection.7">D.4</a></li>2480 <li class="indline1">content negotiation <a class="iref" href="#rfc.iref.c.2">1.3</a></li>2481 <li class="indline1">Content-Length header <a class="iref" href="#rfc.xref.header.content-length.1">4.4</a>, <a class="iref" href="#rfc.iref.c.7"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">D.3</a></li>2482 </ul>2483 </li>2484 <li class="indline0"><a id="rfc.index.D" href="#rfc.index.D"><b>D</b></a><ul class="ind">2485 <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>2486 <li class="indline1">downstream <a class="iref" href="#rfc.iref.d.1">1.3</a></li>2487 </ul>2488 </li>2489 <li class="indline0"><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul class="ind">2490 <li class="indline1">entity <a class="iref" href="#rfc.iref.e.1">1.3</a></li>2491 </ul>2492 </li>2493 <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind">2494 <li class="indline1">gateway <a class="iref" href="#rfc.iref.g.1">1.3</a></li>2495 <li class="indline1"><tt>Grammar</tt> 2496 <ul class="ind">2497 <li class="indline1"><tt>ALPHA</tt> <a class="iref" href="#rfc.iref.g.6"><b>2.2</b></a></li>2498 <li class="indline1"><tt>asctime-date</tt> <a class="iref" href="#rfc.iref.g.30"><b>3.3.1</b></a></li>2499 <li class="indline1"><tt>attribute</tt> <a class="iref" href="#rfc.iref.g.41"><b>3.4</b></a></li>2500 <li class="indline1"><tt>CHAR</tt> <a class="iref" href="#rfc.iref.g.3"><b>2.2</b></a></li>2501 <li class="indline1"><tt>chunk</tt> <a class="iref" href="#rfc.iref.g.44"><b>3.4.1</b></a></li>2502 <li class="indline1"><tt>chunk-data</tt> <a class="iref" href="#rfc.iref.g.50"><b>3.4.1</b></a></li>2503 <li class="indline1"><tt>chunk-ext-name</tt> <a class="iref" href="#rfc.iref.g.48"><b>3.4.1</b></a></li>2504 <li class="indline1"><tt>chunk-ext-val</tt> <a class="iref" href="#rfc.iref.g.49"><b>3.4.1</b></a></li>2505 <li class="indline1"><tt>chunk-extension</tt> <a class="iref" href="#rfc.iref.g.47"><b>3.4.1</b></a></li>2506 <li class="indline1"><tt>chunk-size</tt> <a class="iref" href="#rfc.iref.g.45"><b>3.4.1</b></a></li>2507 <li class="indline1"><tt>Chunked-Body</tt> <a class="iref" href="#rfc.iref.g.43"><b>3.4.1</b></a></li>2508 <li class="indline1"><tt>comment</tt> <a class="iref" href="#rfc.iref.g.20"><b>2.2</b></a></li>2509 <li class="indline1"><tt>Connection</tt> <a class="iref" href="#rfc.iref.g.71"><b>8.1</b></a></li>2510 <li class="indline1"><tt>connection-token</tt> <a class="iref" href="#rfc.iref.g.72"><b>8.1</b></a></li>2511 <li class="indline1"><tt>Content-Length</tt> <a class="iref" href="#rfc.iref.g.73"><b>8.2</b></a></li>2512 <li class="indline1"><tt>CR</tt> <a class="iref" href="#rfc.iref.g.9"><b>2.2</b></a></li>2513 <li class="indline1"><tt>CRLF</tt> <a class="iref" href="#rfc.iref.g.14"><b>2.2</b></a></li>2514 <li class="indline1"><tt>ctext</tt> <a class="iref" href="#rfc.iref.g.21"><b>2.2</b></a></li>2515 <li class="indline1"><tt>CTL</tt> <a class="iref" href="#rfc.iref.g.8"><b>2.2</b></a></li>2516 <li class="indline1"><tt>Date</tt> <a class="iref" href="#rfc.iref.g.74"><b>8.3</b></a></li>2517 <li class="indline1"><tt>date1</tt> <a class="iref" href="#rfc.iref.g.31"><b>3.3.1</b></a></li>2518 <li class="indline1"><tt>date2</tt> <a class="iref" href="#rfc.iref.g.32"><b>3.3.1</b></a></li>2519 <li class="indline1"><tt>date3</tt> <a class="iref" href="#rfc.iref.g.33"><b>3.3.1</b></a></li>2520 <li class="indline1"><tt>DIGIT</tt> <a class="iref" href="#rfc.iref.g.7"><b>2.2</b></a></li>2521 <li class="indline1"><tt>DQUOTE</tt> <a class="iref" href="#rfc.iref.g.13"><b>2.2</b></a></li>2522 <li class="indline1"><tt>extension-code</tt> <a class="iref" href="#rfc.iref.g.69"><b>6.1.1</b></a></li>2523 <li class="indline1"><tt>extension-method</tt> <a class="iref" href="#rfc.iref.g.64"><b>5.1.1</b></a></li>2524 <li class="indline1"><tt>field-content</tt> <a class="iref" href="#rfc.iref.g.58"><b>4.2</b></a></li>2525 <li class="indline1"><tt>field-name</tt> <a class="iref" href="#rfc.iref.g.56"><b>4.2</b></a></li>2526 <li class="indline1"><tt>field-value</tt> <a class="iref" href="#rfc.iref.g.57"><b>4.2</b></a></li>2527 <li class="indline1"><tt>general-header</tt> <a class="iref" href="#rfc.iref.g.60"><b>4.5</b></a></li>2528 <li class="indline1"><tt>generic-message</tt> <a class="iref" href="#rfc.iref.g.53"><b>4.1</b></a></li>2529 <li class="indline1"><tt>HEX</tt> <a class="iref" href="#rfc.iref.g.17"><b>2.2</b></a></li>2530 <li class="indline1"><tt>Host</tt> <a class="iref" href="#rfc.iref.g.75"><b>8.4</b></a></li>2531 <li class="indline1"><tt>HTAB</tt> <a class="iref" href="#rfc.iref.g.12"><b>2.2</b></a></li>2532 <li class="indline1"><tt>HTTP-date</tt> <a class="iref" href="#rfc.iref.g.27"><b>3.3.1</b></a></li>2533 <li class="indline1"><tt>HTTP-message</tt> <a class="iref" href="#rfc.iref.g.52"><b>4.1</b></a></li>2534 <li class="indline1"><tt>HTTP-Version</tt> <a class="iref" href="#rfc.iref.g.25"><b>3.1</b></a></li>2535 <li class="indline1"><tt>http_URL</tt> <a class="iref" href="#rfc.iref.g.26"><b>3.2.2</b></a></li>2536 <li class="indline1"><tt>last-chunk</tt> <a class="iref" href="#rfc.iref.g.46"><b>3.4.1</b></a></li>2537 <li class="indline1"><tt>LF</tt> <a class="iref" href="#rfc.iref.g.10"><b>2.2</b></a></li>2538 <li class="indline1"><tt>LOALPHA</tt> <a class="iref" href="#rfc.iref.g.5"><b>2.2</b></a></li>2539 <li class="indline1"><tt>LWS</tt> <a class="iref" href="#rfc.iref.g.15"><b>2.2</b></a></li>2540 <li class="indline1"><tt>message-body</tt> <a class="iref" href="#rfc.iref.g.59"><b>4.3</b></a></li>2541 <li class="indline1"><tt>message-header</tt> <a class="iref" href="#rfc.iref.g.55"><b>4.2</b></a></li>2542 <li class="indline1"><tt>Method</tt> <a class="iref" href="#rfc.iref.g.63"><b>5.1.1</b></a></li>2543 <li class="indline1"><tt>month</tt> <a class="iref" href="#rfc.iref.g.37"><b>3.3.1</b></a></li>2544 <li class="indline1"><tt>OCTET</tt> <a class="iref" href="#rfc.iref.g.2"><b>2.2</b></a></li>2545 <li class="indline1"><tt>parameter</tt> <a class="iref" href="#rfc.iref.g.40"><b>3.4</b></a></li>2546 <li class="indline1"><tt>protocol-name</tt> <a class="iref" href="#rfc.iref.g.83"><b>8.9</b></a></li>2547 <li class="indline1"><tt>protocol-version</tt> <a class="iref" href="#rfc.iref.g.84"><b>8.9</b></a></li>2548 <li class="indline1"><tt>pseudonym</tt> <a class="iref" href="#rfc.iref.g.86"><b>8.9</b></a></li>2549 <li class="indline1"><tt>qdtext</tt> <a class="iref" href="#rfc.iref.g.23"><b>2.2</b></a></li>2550 <li class="indline1"><tt>quoted-pair</tt> <a class="iref" href="#rfc.iref.g.24"><b>2.2</b></a></li>2551 <li class="indline1"><tt>quoted-string</tt> <a class="iref" href="#rfc.iref.g.22"><b>2.2</b></a></li>2552 <li class="indline1"><tt>Reason-Phrase</tt> <a class="iref" href="#rfc.iref.g.70"><b>6.1.1</b></a></li>2553 <li class="indline1"><tt>received-by</tt> <a class="iref" href="#rfc.iref.g.85"><b>8.9</b></a></li>2554 <li class="indline1"><tt>received-protocol</tt> <a class="iref" href="#rfc.iref.g.82"><b>8.9</b></a></li>2555 <li class="indline1"><tt>Request</tt> <a class="iref" href="#rfc.iref.g.61"><b>5</b></a></li>2556 <li class="indline1"><tt>Request-Line</tt> <a class="iref" href="#rfc.iref.g.62"><b>5.1</b></a></li>2557 <li class="indline1"><tt>Request-URI</tt> <a class="iref" href="#rfc.iref.g.65"><b>5.1.2</b></a></li>2558 <li class="indline1"><tt>Response</tt> <a class="iref" href="#rfc.iref.g.66"><b>6</b></a></li>2559 <li class="indline1"><tt>rfc1123-date</tt> <a class="iref" href="#rfc.iref.g.28"><b>3.3.1</b></a></li>2560 <li class="indline1"><tt>rfc850-date</tt> <a class="iref" href="#rfc.iref.g.29"><b>3.3.1</b></a></li>2561 <li class="indline1"><tt>separators</tt> <a class="iref" href="#rfc.iref.g.19"><b>2.2</b></a></li>2562 <li class="indline1"><tt>SP</tt> <a class="iref" href="#rfc.iref.g.11"><b>2.2</b></a></li>2563 <li class="indline1"><tt>start-line</tt> <a class="iref" href="#rfc.iref.g.54"><b>4.1</b></a></li>2564 <li class="indline1"><tt>Status-Code</tt> <a class="iref" href="#rfc.iref.g.68"><b>6.1.1</b></a></li>2565 <li class="indline1"><tt>Status-Line</tt> <a class="iref" href="#rfc.iref.g.67"><b>6.1</b></a></li>2566 <li class="indline1"><tt>t-codings</tt> <a class="iref" href="#rfc.iref.g.77"><b>8.5</b></a></li>2567 <li class="indline1"><tt>TE</tt> <a class="iref" href="#rfc.iref.g.76"><b>8.5</b></a></li>2568 <li class="indline1"><tt>TEXT</tt> <a class="iref" href="#rfc.iref.g.16"><b>2.2</b></a></li>2569 <li class="indline1"><tt>time</tt> <a class="iref" href="#rfc.iref.g.34"><b>3.3.1</b></a></li>2570 <li class="indline1"><tt>token</tt> <a class="iref" href="#rfc.iref.g.18"><b>2.2</b></a></li>2571 <li class="indline1"><tt>trailer</tt> <a class="iref" href="#rfc.iref.g.51"><b>3.4.1</b></a></li>2572 <li class="indline1"><tt>Trailer</tt> <a class="iref" href="#rfc.iref.g.78"><b>8.6</b></a></li>2573 <li class="indline1"><tt>transfer-coding</tt> <a class="iref" href="#rfc.iref.g.38"><b>3.4</b></a></li>2574 <li class="indline1"><tt>Transfer-Encoding</tt> <a class="iref" href="#rfc.iref.g.79"><b>8.7</b></a></li>2575 <li class="indline1"><tt>transfer-extension</tt> <a class="iref" href="#rfc.iref.g.39"><b>3.4</b></a></li>2576 <li class="indline1"><tt>UPALPHA</tt> <a class="iref" href="#rfc.iref.g.4"><b>2.2</b></a></li>2577 <li class="indline1"><tt>Upgrade</tt> <a class="iref" href="#rfc.iref.g.80"><b>8.8</b></a></li>2578 <li class="indline1"><tt>value</tt> <a class="iref" href="#rfc.iref.g.42"><b>3.4</b></a></li>2579 <li class="indline1"><tt>Via</tt> <a class="iref" href="#rfc.iref.g.81"><b>8.9</b></a></li>2580 <li class="indline1"><tt>weekday</tt> <a class="iref" href="#rfc.iref.g.36"><b>3.3.1</b></a></li>2581 <li class="indline1"><tt>wkday</tt> <a class="iref" href="#rfc.iref.g.35"><b>3.3.1</b></a></li>2582 </ul>2583 </li>2584 </ul>2585 </li>2586 <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">2587 <li class="indline1">Headers 2588 <ul class="ind">2589 <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>, <a class="iref" href="#rfc.xref.header.connection.7">D.4</a></li>2590 <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>, <a class="iref" href="#rfc.xref.header.content-length.2">D.3</a></li>2591 <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>2592 <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>2593 <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>2594 <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>2595 <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>2596 <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>2597 <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>2598 </ul>2599 </li>2600 <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>2601 </ul>2602 </li>2603 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">2604 <li class="indline1">inbound <a class="iref" href="#rfc.iref.i.1">1.3</a></li>2605 <li class="indline1"><em>ISO-8859-1</em> <a class="iref" href="#rfc.xref.ISO-8859-1.1">2.2</a>, <a class="iref" href="#ISO-8859-1"><b>12.1</b></a></li>2606 </ul>2607 </li>2608 <li class="indline0"><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul class="ind">2609 <li class="indline1">Media Type 2610 <ul class="ind">2611 <li class="indline1">application/http <a class="iref" href="#rfc.iref.m.4"><b>A.2</b></a></li>2612 <li class="indline1">message/http <a class="iref" href="#rfc.iref.m.2"><b>A.1</b></a></li>2613 </ul>2614 </li>2615 <li class="indline1">message <a class="iref" href="#rfc.iref.m.1">1.3</a></li>2616 <li class="indline1">message/http Media Type <a class="iref" href="#rfc.iref.m.3"><b>A.1</b></a></li>2617 </ul>2618 </li>2619 <li class="indline0"><a id="rfc.index.N" href="#rfc.index.N"><b>N</b></a><ul class="ind">2620 <li class="indline1"><em>Nie1997</em> <a class="iref" href="#rfc.xref.Nie1997.1">7.1.1</a>, <a class="iref" href="#Nie1997"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.Nie1997.2">D.3</a></li>2621 </ul>2622 </li>2623 <li class="indline0"><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul class="ind">2624 <li class="indline1">origin server <a class="iref" href="#rfc.iref.o.1">1.3</a></li>2625 <li class="indline1">outbound <a class="iref" href="#rfc.iref.o.2">1.3</a></li>2626 </ul>2627 </li>2628 <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">2629 <li class="indline1"><em>Pad1995</em> <a class="iref" href="#rfc.xref.Pad1995.1">7.1.1</a>, <a class="iref" href="#Pad1995"><b>12.2</b></a></li>2630 <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.1</b></a><ul class="ind">2631 <li class="indline1"><em>Section 3</em> <a class="iref" href="#rfc.xref.Part2.4">4.3</a></li>2632 <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>2633 <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>2634 <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>2635 <li class="indline1"><em>Section 8.9</em> <a class="iref" href="#rfc.xref.Part2.6">5.1.2</a></li>2636 <li class="indline1"><em>Section 9</em> <a class="iref" href="#rfc.xref.Part2.8">6.1.1</a></li>2637 <li class="indline1"><em>Section 9.1.1</em> <a class="iref" href="#rfc.xref.Part2.11">7.2.3</a></li>2638 <li class="indline1"><em>Section 9.1</em> <a class="iref" href="#rfc.xref.Part2.14">7.2.3</a></li>2639 <li class="indline1"><em>Section 9.4.15</em> <a class="iref" href="#rfc.xref.Part2.1">3.2.1</a></li>2640 <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>2641 </ul>2642 </li>2643 <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">4.2</a>, <a class="iref" href="#rfc.xref.Part3.9">5</a>, <a class="iref" href="#rfc.xref.Part3.10">6</a>, <a class="iref" href="#rfc.xref.Part3.11">8.5</a>, <a class="iref" href="#Part3"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part3.12">B</a>, <a class="iref" href="#rfc.xref.Part3.13">D.3</a><ul class="ind">2644 <li class="indline1"><em>Section 2.2</em> <a class="iref" href="#rfc.xref.Part3.6">3.4</a>, <a class="iref" href="#rfc.xref.Part3.7">3.4</a></li>2645 <li class="indline1"><em>Section 2.3</em> <a class="iref" href="#rfc.xref.Part3.5">2.2</a></li>2646 <li class="indline1"><em>Section 2.4</em> <a class="iref" href="#rfc.xref.Part3.11">8.5</a></li>2647 <li class="indline1"><em>Section 3</em> <a class="iref" href="#rfc.xref.Part3.1">1.3</a></li>2648 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part3.8">4.2</a>, <a class="iref" href="#rfc.xref.Part3.9">5</a>, <a class="iref" href="#rfc.xref.Part3.10">6</a></li>2649 <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>2650 <li class="indline1"><em>Section A</em> <a class="iref" href="#rfc.xref.Part3.4">1.4</a></li>2651 </ul>2652 </li>2653 <li class="indline1"><em>Part5</em> <a class="iref" href="#Part5"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part5.1">D.3</a></li>2654 <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.1</b></a>, <a class="iref" href="#rfc.xref.Part6.6">D.3</a><ul class="ind">2655 <li class="indline1"><em>Section 1</em> <a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a></li>2656 <li class="indline1"><em>Section 15.2</em> <a class="iref" href="#rfc.xref.Part6.3">4.5</a></li>2657 <li class="indline1"><em>Section 15.4</em> <a class="iref" href="#rfc.xref.Part6.4">4.5</a></li>2658 <li class="indline1"><em>Section 15.6</em> <a class="iref" href="#rfc.xref.Part6.5">4.5</a></li>2659 </ul>2660 </li>2661 <li class="indline1">proxy <a class="iref" href="#rfc.iref.p.1">1.3</a></li>2662 </ul>2663 </li>2664 <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">2665 <li class="indline1">representation <a class="iref" href="#rfc.iref.r.4">1.3</a></li>2666 <li class="indline1">request <a class="iref" href="#rfc.iref.r.1">1.3</a></li>2667 <li class="indline1">resource <a class="iref" href="#rfc.iref.r.3">1.3</a></li>2668 <li class="indline1">response <a class="iref" href="#rfc.iref.r.2">1.3</a></li>2669 <li class="indline1"><em>RFC1123</em> <a class="iref" href="#rfc.xref.RFC1123.1">3.3.1</a>, <a class="iref" href="#RFC1123"><b>12.2</b></a></li>2670 <li class="indline1"><em>RFC1305</em> <a class="iref" href="#rfc.xref.RFC1305.1">8.3</a>, <a class="iref" href="#RFC1305"><b>12.2</b></a></li>2671 <li class="indline1"><em>RFC1436</em> <a class="iref" href="#rfc.xref.RFC1436.1">1.1</a>, <a class="iref" href="#RFC1436"><b>12.2</b></a></li>2672 <li class="indline1"><em>RFC1630</em> <a class="iref" href="#rfc.xref.RFC1630.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC1630.2">3.2</a>, <a class="iref" href="#RFC1630"><b>12.2</b></a></li>2673 <li class="indline1"><em>RFC1737</em> <a class="iref" href="#rfc.xref.RFC1737.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC1737.2">3.2</a>, <a class="iref" href="#RFC1737"><b>12.2</b></a></li>2674 <li class="indline1"><em>RFC1738</em> <a class="iref" href="#rfc.xref.RFC1738.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC1738.2">3.2</a>, <a class="iref" href="#rfc.xref.RFC1738.3">3.2.1</a>, <a class="iref" href="#RFC1738"><b>12.2</b></a></li>2675 <li class="indline1"><em>RFC1808</em> <a class="iref" href="#rfc.xref.RFC1808.1">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC1808.2">3.2.1</a>, <a class="iref" href="#RFC1808"><b>12.2</b></a></li>2676 <li class="indline1"><em>RFC1900</em> <a class="iref" href="#rfc.xref.RFC1900.1">3.2.2</a>, <a class="iref" href="#rfc.xref.RFC1900.2">10.4</a>, <a class="iref" href="#RFC1900"><b>12.2</b></a></li>2677 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#rfc.xref.RFC1945.1">1</a>, <a class="iref" href="#RFC1945"><b>12.2</b></a></li>2678 <li class="indline1"><em>RFC2045</em> <a class="iref" href="#rfc.xref.RFC2045.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC2045.2">3.4</a>, <a class="iref" href="#rfc.xref.RFC2045.3">11</a>, <a class="iref" href="#RFC2045"><b>12.1</b></a></li>2679 <li class="indline1"><em>RFC2047</em> <a class="iref" href="#rfc.xref.RFC2047.1">2.2</a>, <a class="iref" href="#RFC2047"><b>12.1</b></a></li>2680 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC2068.2">7.1.1</a>, <a class="iref" href="#rfc.xref.RFC2068.3">7.1.3</a>, <a class="iref" href="#rfc.xref.RFC2068.4">7.2.3</a>, <a class="iref" href="#rfc.xref.RFC2068.5">11</a>, <a class="iref" href="#RFC2068"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.6">D</a>, <a class="iref" href="#rfc.xref.RFC2068.7">D.2</a><ul class="ind">2681 <li class="indline1"><em>Section 19.7.1</em> <a class="iref" href="#rfc.xref.RFC2068.6">D</a></li>2682 </ul>2683 </li>2684 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.2</a>, <a class="iref" href="#RFC2119"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.RFC2119.2">D.3</a></li>2685 <li class="indline1"><em>RFC2145</em> <a class="iref" href="#rfc.xref.RFC2145.1">3.1</a>, <a class="iref" href="#rfc.xref.RFC2145.2">3.1</a>, <a class="iref" href="#RFC2145"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2145.3">D.3</a></li>2686 <li class="indline1"><em>RFC2324</em> <a class="iref" href="#rfc.xref.RFC2324.1">1.1</a>, <a class="iref" href="#RFC2324"><b>12.2</b></a></li>2687 <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.1</b></a>, <a class="iref" href="#rfc.xref.RFC2396.4">D.4</a><ul class="ind">2688 <li class="indline1"><em>Section 3</em> <a class="iref" href="#rfc.xref.RFC2396.4">D.4</a></li>2689 </ul>2690 </li>2691 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">1</a>, <a class="iref" href="#rfc.xref.RFC2616.3">11</a>, <a class="iref" href="#RFC2616"><b>12.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.4">E.1</a></li>2692 <li class="indline1"><em>RFC2821</em> <a class="iref" href="#rfc.xref.RFC2821.1">1.1</a>, <a class="iref" href="#RFC2821"><b>12.2</b></a></li>2693 <li class="indline1"><em>RFC2822</em> <a class="iref" href="#rfc.xref.RFC2822.1">1.1</a>, <a class="iref" href="#rfc.xref.RFC2822.2">4.1</a>, <a class="iref" href="#rfc.xref.RFC2822.3">4.2</a>, <a class="iref" href="#rfc.xref.RFC2822.4">8.3</a>, <a class="iref" href="#rfc.xref.RFC2822.5">8.9</a>, <a class="iref" href="#RFC2822"><b>12.2</b></a><ul class="ind">2694 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.RFC2822.3">4.2</a></li>2695 <li class="indline1"><em>Section 3.6.1</em> <a class="iref" href="#rfc.xref.RFC2822.4">8.3</a></li>2696 </ul>2697 </li>2698 <li class="indline1"><em>RFC3977</em> <a class="iref" href="#rfc.xref.RFC3977.1">1.1</a>, <a class="iref" href="#RFC3977"><b>12.2</b></a></li>2699 <li class="indline1"><em>RFC4288</em> <a class="iref" href="#RFC4288"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.RFC4288.1">A</a></li>2700 <li class="indline1"><em>RFC822</em> <a class="iref" href="#rfc.xref.RFC822.1">3.3.1</a>, <a class="iref" href="#RFC822"><b>12.2</b></a></li>2701 <li class="indline1"><em>RFC822ABNF</em> <a class="iref" href="#rfc.xref.RFC822ABNF.1">2.1</a>, <a class="iref" href="#rfc.xref.RFC822ABNF.2">11</a>, <a class="iref" href="#RFC822ABNF"><b>12.1</b></a></li>2702 <li class="indline1"><em>RFC959</em> <a class="iref" href="#rfc.xref.RFC959.1">1.1</a>, <a class="iref" href="#RFC959"><b>12.2</b></a></li>2703 </ul>2704 </li>2705 <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind">2706 <li class="indline1">server <a class="iref" href="#rfc.iref.s.1">1.3</a></li>2707 <li class="indline1"><em>Spe</em> <a class="iref" href="#rfc.xref.Spe.1">7.1.1</a>, <a class="iref" href="#Spe"><b>12.2</b></a></li>2708 </ul>2709 </li>2710 <li class="indline0"><a id="rfc.index.T" href="#rfc.index.T"><b>T</b></a><ul class="ind">2711 <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>2712 <li class="indline1"><em>Tou1998</em> <a class="iref" href="#rfc.xref.Tou1998.1">7.1.1</a>, <a class="iref" href="#Tou1998"><b>12.2</b></a></li>2713 <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>2714 <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>2715 <li class="indline1">tunnel <a class="iref" href="#rfc.iref.t.1">1.3</a></li>2716 </ul>2717 </li>2718 <li class="indline0"><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul class="ind">2719 <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>2720 <li class="indline1">upstream <a class="iref" href="#rfc.iref.u.2">1.3</a></li>2721 <li class="indline1"><em>USASCII</em> <a class="iref" href="#rfc.xref.USASCII.1">2.2</a>, <a class="iref" href="#USASCII"><b>12.1</b></a></li>2722 <li class="indline1">user agent <a class="iref" href="#rfc.iref.u.1">1.3</a></li>2723 </ul>2724 </li>2725 <li class="indline0"><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul class="ind">2726 <li class="indline1">variant <a class="iref" href="#rfc.iref.v.1">1.3</a></li>2727 <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>2728 </ul>2729 </li>2730 <li class="indline0"><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul class="ind">2731 <li class="indline1"><em>WAIS</em> <a class="iref" href="#rfc.xref.WAIS.1">1.1</a>, <a class="iref" href="#WAIS"><b>12.2</b></a></li>2732 </ul>2733 </li>2734 </ul>2735 </div>2736 2727 </body> 2737 2728 </html>
Note: See TracChangeset
for help on using the changeset viewer.
