Changeset 1145 for draft-ietf-httpbis/latest/p1-messaging.html
- Timestamp:
- 01/03/11 09:24:49 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1127 r1145 85 85 margin-left: 2em; 86 86 margin-right: 2em; 87 } 88 ol.la { 89 list-style-type: lower-alpha; 90 } 91 ol.ua { 92 list-style-type: upper-alpha; 87 93 } 88 94 ol p { … … 344 350 } 345 351 @top-right { 346 content: " February2011";352 content: "March 2011"; 347 353 } 348 354 @top-center { … … 353 359 } 354 360 @bottom-center { 355 content: "Expires August 23, 2011";361 content: "Expires September 2, 2011"; 356 362 } 357 363 @bottom-right { … … 392 398 <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C"> 393 399 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 394 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.54 0, 2011-01-10 09:27:20, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">400 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.543, 2011-02-18 21:03:40, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 395 401 <link rel="schema.dct" href="http://purl.org/dc/terms/"> 396 402 <meta name="dct.creator" content="Fielding, R."> … … 404 410 <meta name="dct.creator" content="Reschke, J. F."> 405 411 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2011-0 2-19">412 <meta name="dct.issued" scheme="ISO8601" content="2011-03-01"> 407 413 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 408 414 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext 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."> … … 435 441 </tr> 436 442 <tr> 437 <td class="left">Expires: August 23, 2011</td>443 <td class="left">Expires: September 2, 2011</td> 438 444 <td class="right">HP</td> 439 445 </tr> … … 488 494 <tr> 489 495 <td class="left"></td> 490 <td class="right"> February 19, 2011</td>496 <td class="right">March 1, 2011</td> 491 497 </tr> 492 498 </tbody> … … 516 522 in progress”. 517 523 </p> 518 <p>This Internet-Draft will expire on August 23, 2011.</p>524 <p>This Internet-Draft will expire on September 2, 2011.</p> 519 525 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 520 526 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1320 1326 to the payload being transferred. These header fields apply only to the message being transmitted. 1321 1327 </p> 1322 <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.45"></span> <a href="#general.header.fields" class="smpl">general-header</a> = <a href="#abnf.dependencies" class="smpl">Cache-Control</a> ; <a href="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 3.2</a> 1323 / <a href="#header.connection" class="smpl">Connection</a> ; <a href="#header.connection" id="rfc.xref.header.connection.1" title="Connection">Section 9.1</a> 1324 / <a href="#header.date" class="smpl">Date</a> ; <a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section 9.3</a> 1325 / <a href="#abnf.dependencies" class="smpl">Pragma</a> ; <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 3.4</a> 1326 / <a href="#header.trailer" class="smpl">Trailer</a> ; <a href="#header.trailer" id="rfc.xref.header.trailer.1" title="Trailer">Section 9.6</a> 1327 / <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> ; <a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.3" title="Transfer-Encoding">Section 9.7</a> 1328 / <a href="#header.upgrade" class="smpl">Upgrade</a> ; <a href="#header.upgrade" id="rfc.xref.header.upgrade.1" title="Upgrade">Section 9.8</a> 1329 / <a href="#header.via" class="smpl">Via</a> ; <a href="#header.via" id="rfc.xref.header.via.1" title="Via">Section 9.9</a> 1330 / <a href="#abnf.dependencies" class="smpl">Warning</a> ; <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.warning" title="Warning">Section 3.6</a> 1331 / <a href="#abnf.dependencies" class="smpl">MIME-Version</a> ; <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#mime-version" title="MIME-Version">Appendix A.1</a> 1332 </pre><p id="rfc.section.3.4.p.3">General-header field names can be extended reliably only in combination with a change in the protocol version. However, new 1328 <div id="rfc.table.u.1"> 1329 <table class="tt full left" cellpadding="3" cellspacing="0"> 1330 <thead> 1331 <tr> 1332 <th>Header Field Name</th> 1333 <th>Defined in...</th> 1334 </tr> 1335 </thead> 1336 <tbody> 1337 <tr> 1338 <td class="left">Connection</td> 1339 <td class="left"><a href="#header.connection" id="rfc.xref.header.connection.1" title="Connection">Section 9.1</a></td> 1340 </tr> 1341 <tr> 1342 <td class="left">Date</td> 1343 <td class="left"><a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section 9.3</a></td> 1344 </tr> 1345 <tr> 1346 <td class="left">Pragma</td> 1347 <td class="left"><a href="p6-cache.html#header.pragma" title="Pragma">Section 3.4</a> of <a href="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td> 1348 </tr> 1349 <tr> 1350 <td class="left">Trailer</td> 1351 <td class="left"><a href="#header.trailer" id="rfc.xref.header.trailer.1" title="Trailer">Section 9.6</a></td> 1352 </tr> 1353 <tr> 1354 <td class="left">Transfer-Encoding</td> 1355 <td class="left"><a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.3" title="Transfer-Encoding">Section 9.7</a></td> 1356 </tr> 1357 <tr> 1358 <td class="left">Upgrade</td> 1359 <td class="left"><a href="#header.upgrade" id="rfc.xref.header.upgrade.1" title="Upgrade">Section 9.8</a></td> 1360 </tr> 1361 <tr> 1362 <td class="left">Via</td> 1363 <td class="left"><a href="#header.via" id="rfc.xref.header.via.1" title="Via">Section 9.9</a></td> 1364 </tr> 1365 <tr> 1366 <td class="left">Warning</td> 1367 <td class="left"><a href="p6-cache.html#header.warning" title="Warning">Section 3.6</a> of <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td> 1368 </tr> 1369 <tr> 1370 <td class="left">MIME-Version</td> 1371 <td class="left"><a href="p3-payload.html#mime-version" title="MIME-Version">Appendix A.1</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></td> 1372 </tr> 1373 </tbody> 1374 </table> 1375 </div> 1376 <p id="rfc.section.3.4.p.2">General-header field names can be extended reliably only in combination with a change in the protocol version. However, new 1333 1377 or experimental header fields might be given the semantics of general header fields if all parties in the communication recognize 1334 1378 them to be general-header fields. … … 1338 1382 resource, the identifier of the resource, and the protocol version in use. 1339 1383 </p> 1340 <div id="rfc.figure.u.3 1"></div><pre class="inline"><span id="rfc.iref.g.46"></span> <a href="#request" class="smpl">Request</a> = <a href="#request-line" class="smpl">Request-Line</a> ; <a href="#request-line" title="Request-Line">Section 4.1</a>1384 <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.45"></span> <a href="#request" class="smpl">Request</a> = <a href="#request-line" class="smpl">Request-Line</a> ; <a href="#request-line" title="Request-Line">Section 4.1</a> 1341 1385 *( <a href="#header.fields" class="smpl">header-field</a> <a href="#core.rules" class="smpl">CRLF</a> ) ; <a href="#header.fields" title="Header Fields">Section 3.2</a> 1342 1386 <a href="#core.rules" class="smpl">CRLF</a> … … 1346 1390 The elements are separated by SP characters. No CR or LF is allowed except in the final CRLF sequence. 1347 1391 </p> 1348 <div id="rfc.figure.u.3 2"></div><pre class="inline"><span id="rfc.iref.g.47"></span> <a href="#request-line" class="smpl">Request-Line</a> = <a href="#method" class="smpl">Method</a> <a href="#core.rules" class="smpl">SP</a> <a href="#request-target" class="smpl">request-target</a> <a href="#core.rules" class="smpl">SP</a> <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">CRLF</a>1392 <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.46"></span> <a href="#request-line" class="smpl">Request-Line</a> = <a href="#method" class="smpl">Method</a> <a href="#core.rules" class="smpl">SP</a> <a href="#request-target" class="smpl">request-target</a> <a href="#core.rules" class="smpl">SP</a> <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">CRLF</a> 1349 1393 </pre><h3 id="rfc.section.4.1.1"><a href="#rfc.section.4.1.1">4.1.1</a> <a id="method" href="#method">Method</a></h3> 1350 1394 <p id="rfc.section.4.1.1.p.1">The Method token indicates the method to be performed on the resource identified by the request-target. The method is case-sensitive.</p> 1351 <div id="rfc.figure.u.3 3"></div><pre class="inline"><span id="rfc.iref.g.48"></span> <a href="#method" class="smpl">Method</a> = <a href="#rule.token.separators" class="smpl">token</a>1395 <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.47"></span> <a href="#method" class="smpl">Method</a> = <a href="#rule.token.separators" class="smpl">token</a> 1352 1396 </pre><h3 id="rfc.section.4.1.2"><a href="#rfc.section.4.1.2">4.1.2</a> <a id="request-target" href="#request-target">request-target</a></h3> 1353 1397 <p id="rfc.section.4.1.2.p.1">The request-target identifies the resource upon which to apply the request.</p> 1354 <div id="rfc.figure.u.3 4"></div><pre class="inline"><span id="rfc.iref.g.49"></span> <a href="#request-target" class="smpl">request-target</a> = "*"1398 <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.48"></span> <a href="#request-target" class="smpl">request-target</a> = "*" 1355 1399 / <a href="#uri" class="smpl">absolute-URI</a> 1356 1400 / ( <a href="#uri" class="smpl">path-absolute</a> [ "?" <a href="#uri" class="smpl">query</a> ] ) … … 1360 1404 This is only allowed for the OPTIONS method. Thus, the only valid example is 1361 1405 </p> 1362 <div id="rfc.figure.u.3 5"></div><pre class="text2">OPTIONS * HTTP/1.11406 <div id="rfc.figure.u.34"></div><pre class="text2">OPTIONS * HTTP/1.1 1363 1407 </pre><p id="rfc.section.4.1.2.p.6"><span id="rfc.iref.a.2"></span> The "absolute-URI" form is <em class="bcp14">REQUIRED</em> when the request is being made to a proxy. The proxy is requested to forward the request or service it from a valid cache, 1364 1408 and return the response. Note that the proxy <em class="bcp14">MAY</em> forward the request on to another proxy or directly to the server specified by the absolute-URI. In order to avoid request … … 1366 1410 Request-Line would be: 1367 1411 </p> 1368 <div id="rfc.figure.u.3 6"></div><pre class="text2">GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.11412 <div id="rfc.figure.u.35"></div><pre class="text2">GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1 1369 1413 </pre><p id="rfc.section.4.1.2.p.8">To allow for transition to absolute-URIs in all requests in future versions of HTTP, all HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absolute-URI form in requests, even though HTTP/1.1 clients will only generate them in requests to proxies. 1370 1414 </p> … … 1375 1419 server would create a TCP connection to port 80 of the host "www.example.org" and send the lines: 1376 1420 </p> 1377 <div id="rfc.figure.u.3 7"></div><pre class="text2">GET /pub/WWW/TheProject.html HTTP/1.11421 <div id="rfc.figure.u.36"></div><pre class="text2">GET /pub/WWW/TheProject.html HTTP/1.1 1378 1422 Host: www.example.org 1379 1423 </pre><p id="rfc.section.4.1.2.p.12">followed by the remainder of the Request. Note that the absolute path cannot be empty; if none is present in the original … … 1383 1427 asterisk form of request-target, then the last proxy on the request chain <em class="bcp14">MUST</em> forward the request with "*" as the final request-target. 1384 1428 </p> 1385 <div id="rfc.figure.u.3 8"></div>1429 <div id="rfc.figure.u.37"></div> 1386 1430 <p>For example, the request</p><pre class="text2">OPTIONS http://www.example.org:8001 HTTP/1.1 1387 </pre><div id="rfc.figure.u.3 9"></div>1431 </pre><div id="rfc.figure.u.38"></div> 1388 1432 <p>would be forwarded by the proxy as</p><pre class="text2">OPTIONS * HTTP/1.1 1389 1433 Host: www.example.org:8001 … … 1455 1499 </p> 1456 1500 <p id="rfc.section.4.3.p.6">Otherwise, when request-target uses the authority form, the effective request URI is undefined.</p> 1457 <div id="rfc.figure.u. 40"></div>1501 <div id="rfc.figure.u.39"></div> 1458 1502 <p>Example 1: the effective request URI for the message</p> <pre class="text">GET /pub/WWW/TheProject.html HTTP/1.1 1459 1503 Host: www.example.org:8080 … … 1461 1505 the request-target "/pub/WWW/TheProject.html", thus "http://www.example.org:8080/pub/WWW/TheProject.html". 1462 1506 </p> 1463 <div id="rfc.figure.u.4 1"></div>1507 <div id="rfc.figure.u.40"></div> 1464 1508 <p>Example 2: the effective request URI for the message</p> <pre class="text">GET * HTTP/1.1 1465 1509 Host: www.example.org … … 1471 1515 <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="response" href="#response">Response</a></h1> 1472 1516 <p id="rfc.section.5.p.1">After receiving and interpreting a request message, a server responds with an HTTP response message.</p> 1473 <div id="rfc.figure.u.4 2"></div><pre class="inline"><span id="rfc.iref.g.50"></span> <a href="#response" class="smpl">Response</a> = <a href="#status-line" class="smpl">Status-Line</a> ; <a href="#status-line" title="Status-Line">Section 5.1</a>1517 <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.49"></span> <a href="#response" class="smpl">Response</a> = <a href="#status-line" class="smpl">Status-Line</a> ; <a href="#status-line" title="Status-Line">Section 5.1</a> 1474 1518 *( <a href="#header.fields" class="smpl">header-field</a> <a href="#core.rules" class="smpl">CRLF</a> ) ; <a href="#header.fields" title="Header Fields">Section 3.2</a> 1475 1519 <a href="#core.rules" class="smpl">CRLF</a> … … 1480 1524 CRLF sequence. 1481 1525 </p> 1482 <div id="rfc.figure.u.4 3"></div><pre class="inline"><span id="rfc.iref.g.51"></span> <a href="#status-line" class="smpl">Status-Line</a> = <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> <a href="#core.rules" class="smpl">CRLF</a>1526 <div id="rfc.figure.u.42"></div><pre class="inline"><span id="rfc.iref.g.50"></span> <a href="#status-line" class="smpl">Status-Line</a> = <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> <a href="#core.rules" class="smpl">CRLF</a> 1483 1527 </pre><h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a> <a id="status.code.and.reason.phrase" href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h3> 1484 1528 <p id="rfc.section.5.1.1.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. These codes … … 1497 1541 <li>5xx: Server Error - The server failed to fulfill an apparently valid request</li> 1498 1542 </ul> 1499 <div id="rfc.figure.u.4 4"></div><pre class="inline"><span id="rfc.iref.g.52"></span><span id="rfc.iref.g.53"></span> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> = 3<a href="#core.rules" class="smpl">DIGIT</a>1543 <div id="rfc.figure.u.43"></div><pre class="inline"><span id="rfc.iref.g.51"></span><span id="rfc.iref.g.52"></span> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> = 3<a href="#core.rules" class="smpl">DIGIT</a> 1500 1544 <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> = *( <a href="#core.rules" class="smpl">WSP</a> / <a href="#core.rules" class="smpl">VCHAR</a> / <a href="#rule.quoted-string" class="smpl">obs-text</a> ) 1501 1545 </pre><h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1> … … 1504 1548 a fixed-length subset of that defined by <a href="#RFC1123" id="rfc.xref.RFC1123.1"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a>: 1505 1549 </p> 1506 <div id="rfc.figure.u.4 5"></div><pre class="text">Sun, 06 Nov 1994 08:49:37 GMT ; RFC 11231550 <div id="rfc.figure.u.44"></div><pre class="text">Sun, 06 Nov 1994 08:49:37 GMT ; RFC 1123 1507 1551 </pre><p id="rfc.section.6.1.p.3">The other formats are described here only for compatibility with obsolete implementations.</p> 1508 <div id="rfc.figure.u.4 6"></div><pre class="text">Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format1552 <div id="rfc.figure.u.45"></div><pre class="text">Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format 1509 1553 Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() format 1510 1554 </pre><p id="rfc.section.6.1.p.5">HTTP/1.1 clients and servers that parse a date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields. See <a href="#tolerant.applications" title="Tolerant Applications">Appendix A</a> for further information. … … 1514 1558 time zone, and <em class="bcp14">MUST</em> be assumed when reading the asctime format. HTTP-date is case sensitive and <em class="bcp14">MUST NOT</em> include additional whitespace beyond that specifically included as SP in the grammar. 1515 1559 </p> 1516 <div id="rfc.figure.u.4 7"></div><pre class="inline"><span id="rfc.iref.g.54"></span> <a href="#date.time.formats.full.date" class="smpl">HTTP-date</a> = <a href="#preferred.date.format" class="smpl">rfc1123-date</a> / <a href="#obsolete.date.formats" class="smpl">obs-date</a>1560 <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.53"></span> <a href="#date.time.formats.full.date" class="smpl">HTTP-date</a> = <a href="#preferred.date.format" class="smpl">rfc1123-date</a> / <a href="#obsolete.date.formats" class="smpl">obs-date</a> 1517 1561 </pre><div id="preferred.date.format"> 1518 1562 <p id="rfc.section.6.1.p.8"> Preferred format:</p> 1519 1563 </div> 1520 <div id="rfc.figure.u.4 8"></div><pre class="inline"><span id="rfc.iref.g.55"></span><span id="rfc.iref.g.56"></span><span id="rfc.iref.g.57"></span><span id="rfc.iref.g.58"></span><span id="rfc.iref.g.59"></span><span id="rfc.iref.g.60"></span><span id="rfc.iref.g.61"></span><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></span><span id="rfc.iref.g.64"></span><span id="rfc.iref.g.65"></span><span id="rfc.iref.g.66"></span> <a href="#preferred.date.format" class="smpl">rfc1123-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#core.rules" class="smpl">SP</a> date1 <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>1564 <div id="rfc.figure.u.47"></div><pre class="inline"><span id="rfc.iref.g.54"></span><span id="rfc.iref.g.55"></span><span id="rfc.iref.g.56"></span><span id="rfc.iref.g.57"></span><span id="rfc.iref.g.58"></span><span id="rfc.iref.g.59"></span><span id="rfc.iref.g.60"></span><span id="rfc.iref.g.61"></span><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></span><span id="rfc.iref.g.64"></span><span id="rfc.iref.g.65"></span> <a href="#preferred.date.format" class="smpl">rfc1123-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#core.rules" class="smpl">SP</a> date1 <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a> 1521 1565 ; fixed length subset of the format defined in 1522 1566 ; <a href="http://tools.ietf.org/html/rfc1123#section-5.2.14">Section 5.2.14</a> of <a href="#RFC1123" id="rfc.xref.RFC1123.2"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a> … … 1561 1605 <p id="rfc.section.6.1.p.11"> Obsolete formats:</p> 1562 1606 </div> 1563 <div id="rfc.figure.u.4 9"></div><pre class="inline"><span id="rfc.iref.g.67"></span> <a href="#obsolete.date.formats" class="smpl">obs-date</a> = <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> / <a href="#obsolete.date.formats" class="smpl">asctime-date</a>1564 </pre><div id="rfc.figure.u. 50"></div><pre class="inline"><span id="rfc.iref.g.68"></span> <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> = <a href="#obsolete.date.formats" class="smpl">day-name-l</a> "," <a href="#core.rules" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date2</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>1607 <div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.66"></span> <a href="#obsolete.date.formats" class="smpl">obs-date</a> = <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> / <a href="#obsolete.date.formats" class="smpl">asctime-date</a> 1608 </pre><div id="rfc.figure.u.49"></div><pre class="inline"><span id="rfc.iref.g.67"></span> <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> = <a href="#obsolete.date.formats" class="smpl">day-name-l</a> "," <a href="#core.rules" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date2</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a> 1565 1609 <a href="#obsolete.date.formats" class="smpl">date2</a> = <a href="#preferred.date.format" class="smpl">day</a> "-" <a href="#preferred.date.format" class="smpl">month</a> "-" 2<a href="#core.rules" class="smpl">DIGIT</a> 1566 1610 ; day-month-year (e.g., 02-Jun-82) … … 1573 1617 / %x53.61.74.75.72.64.61.79 ; "Saturday", case-sensitive 1574 1618 / %x53.75.6E.64.61.79 ; "Sunday", case-sensitive 1575 </pre><div id="rfc.figure.u.5 1"></div><pre class="inline"><span id="rfc.iref.g.69"></span> <a href="#obsolete.date.formats" class="smpl">asctime-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> <a href="#core.rules" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date3</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">year</a>1619 </pre><div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.68"></span> <a href="#obsolete.date.formats" class="smpl">asctime-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> <a href="#core.rules" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date3</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">year</a> 1576 1620 <a href="#obsolete.date.formats" class="smpl">date3</a> = <a href="#preferred.date.format" class="smpl">month</a> <a href="#core.rules" class="smpl">SP</a> ( 2<a href="#core.rules" class="smpl">DIGIT</a> / ( <a href="#core.rules" class="smpl">SP</a> 1<a href="#core.rules" class="smpl">DIGIT</a> )) 1577 1621 ; month day (e.g., Jun 2) … … 1591 1635 transfer-coding is a property of the message rather than a property of the representation that is being transferred. 1592 1636 </p> 1593 <div id="rfc.figure.u.5 2"></div><pre class="inline"><span id="rfc.iref.g.70"></span><span id="rfc.iref.g.71"></span> <a href="#transfer.codings" class="smpl">transfer-coding</a> = "chunked" ; <a href="#chunked.encoding" title="Chunked Transfer Coding">Section 6.2.1</a>1637 <div id="rfc.figure.u.51"></div><pre class="inline"><span id="rfc.iref.g.69"></span><span id="rfc.iref.g.70"></span> <a href="#transfer.codings" class="smpl">transfer-coding</a> = "chunked" ; <a href="#chunked.encoding" title="Chunked Transfer Coding">Section 6.2.1</a> 1594 1638 / "compress" ; <a href="#compress.coding" title="Compress Coding">Section 6.2.2.1</a> 1595 1639 / "deflate" ; <a href="#deflate.coding" title="Deflate Coding">Section 6.2.2.2</a> … … 1600 1644 <p id="rfc.section.6.2.p.3"> Parameters are in the form of attribute/value pairs.</p> 1601 1645 </div> 1602 <div id="rfc.figure.u.5 3"></div><pre class="inline"><span id="rfc.iref.g.72"></span><span id="rfc.iref.g.73"></span><span id="rfc.iref.g.74"></span><span id="rfc.iref.g.75"></span><span id="rfc.iref.g.76"></span> <a href="#rule.parameter" class="smpl">transfer-parameter</a> = <a href="#rule.parameter" class="smpl">attribute</a> <a href="#rule.whitespace" class="smpl">BWS</a> "=" <a href="#rule.whitespace" class="smpl">BWS</a> <a href="#rule.parameter" class="smpl">value</a>1646 <div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.71"></span><span id="rfc.iref.g.72"></span><span id="rfc.iref.g.73"></span><span id="rfc.iref.g.74"></span><span id="rfc.iref.g.75"></span> <a href="#rule.parameter" class="smpl">transfer-parameter</a> = <a href="#rule.parameter" class="smpl">attribute</a> <a href="#rule.whitespace" class="smpl">BWS</a> "=" <a href="#rule.whitespace" class="smpl">BWS</a> <a href="#rule.parameter" class="smpl">value</a> 1603 1647 <a href="#rule.parameter" class="smpl">attribute</a> = <a href="#rule.token.separators" class="smpl">token</a> 1604 1648 <a href="#rule.parameter" class="smpl">value</a> = <a href="#rule.token.separators" class="smpl">word</a> … … 1618 1662 for the recipient to verify that it has received the full message. 1619 1663 </p> 1620 <div id="rfc.figure.u.5 4"></div><pre class="inline"><span id="rfc.iref.g.77"></span><span id="rfc.iref.g.78"></span><span id="rfc.iref.g.79"></span><span id="rfc.iref.g.80"></span><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span><span id="rfc.iref.g.83"></span><span id="rfc.iref.g.84"></span><span id="rfc.iref.g.85"></span><span id="rfc.iref.g.86"></span><span id="rfc.iref.g.87"></span> <a href="#chunked.encoding" class="smpl">Chunked-Body</a> = *<a href="#chunked.encoding" class="smpl">chunk</a>1664 <div id="rfc.figure.u.53"></div><pre class="inline"><span id="rfc.iref.g.76"></span><span id="rfc.iref.g.77"></span><span id="rfc.iref.g.78"></span><span id="rfc.iref.g.79"></span><span id="rfc.iref.g.80"></span><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span><span id="rfc.iref.g.83"></span><span id="rfc.iref.g.84"></span><span id="rfc.iref.g.85"></span><span id="rfc.iref.g.86"></span> <a href="#chunked.encoding" class="smpl">Chunked-Body</a> = *<a href="#chunked.encoding" class="smpl">chunk</a> 1621 1665 <a href="#chunked.encoding" class="smpl">last-chunk</a> 1622 1666 <a href="#chunked.encoding" class="smpl">trailer-part</a> … … 1662 1706 </p> 1663 1707 <p id="rfc.section.6.2.1.p.7">A process for decoding the "chunked" transfer-coding can be represented in pseudo-code as:</p> 1664 <div id="rfc.figure.u.5 5"></div><pre class="text"> length := 01708 <div id="rfc.figure.u.54"></div><pre class="text"> length := 0 1665 1709 read chunk-size, chunk-ext (if any) and CRLF 1666 1710 while (chunk-size > 0) { … … 1709 1753 </p> 1710 1754 </div> 1711 <div id="rfc.iref.g.8 8"></div>1755 <div id="rfc.iref.g.87"></div> 1712 1756 <div id="rfc.iref.c.10"></div> 1713 1757 <h4 id="rfc.section.6.2.2.3"><a href="#rfc.section.6.2.2.3">6.2.2.3</a> <a id="gzip.coding" href="#gzip.coding">Gzip Coding</a></h4> … … 1734 1778 By convention, the products are listed in order of their significance for identifying the application. 1735 1779 </p> 1736 <div id="rfc.figure.u.5 6"></div><pre class="inline"><span id="rfc.iref.g.89"></span><span id="rfc.iref.g.90"></span> <a href="#product.tokens" class="smpl">product</a> = <a href="#rule.token.separators" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>]1780 <div id="rfc.figure.u.55"></div><pre class="inline"><span id="rfc.iref.g.88"></span><span id="rfc.iref.g.89"></span> <a href="#product.tokens" class="smpl">product</a> = <a href="#rule.token.separators" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>] 1737 1781 <a href="#product.tokens" class="smpl">product-version</a> = <a href="#rule.token.separators" class="smpl">token</a> 1738 1782 </pre><p id="rfc.section.6.3.p.3">Examples:</p> 1739 <div id="rfc.figure.u.5 7"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b31783 <div id="rfc.figure.u.56"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b3 1740 1784 Server: Apache/0.8.4 1741 1785 </pre><p id="rfc.section.6.3.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token character <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value). … … 1746 1790 a quality value of 0, then content with this parameter is "not acceptable" for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion. 1747 1791 </p> 1748 <div id="rfc.figure.u.5 8"></div><pre class="inline"><span id="rfc.iref.g.91"></span> <a href="#quality.values" class="smpl">qvalue</a> = ( "0" [ "." 0*3<a href="#core.rules" class="smpl">DIGIT</a> ] )1792 <div id="rfc.figure.u.57"></div><pre class="inline"><span id="rfc.iref.g.90"></span> <a href="#quality.values" class="smpl">qvalue</a> = ( "0" [ "." 0*3<a href="#core.rules" class="smpl">DIGIT</a> ] ) 1749 1793 / ( "1" [ "." 0*3("0") ] ) 1750 1794 </pre><div class="note" id="rfc.section.6.4.p.3"> … … 1867 1911 <li>Content-Type</li> 1868 1912 </ul> 1869 <p id="rfc.section.7.1.3.2.p.6">A transforming proxy <em class="bcp14">MAY</em> modify or add these fields to a message that does not include no-transform, but if it does so, it <em class="bcp14">MUST</em> add a Warning 214 (Transformation applied) if one does not already appear in the message (see <a href="p6-cache.html#header.warning" title="Warning">Section 3.6</a> of <a href="#Part6" id="rfc.xref.Part6. 9"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).1913 <p id="rfc.section.7.1.3.2.p.6">A transforming proxy <em class="bcp14">MAY</em> modify or add these fields to a message that does not include no-transform, but if it does so, it <em class="bcp14">MUST</em> add a Warning 214 (Transformation applied) if one does not already appear in the message (see <a href="p6-cache.html#header.warning" title="Warning">Section 3.6</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). 1870 1914 </p> 1871 1915 <div class="note" id="rfc.section.7.1.3.2.p.7"> … … 2023 2067 </p> 2024 2068 <p id="rfc.section.9.1.p.2">The Connection header field's value has the following grammar:</p> 2025 <div id="rfc.figure.u.5 9"></div><pre class="inline"><span id="rfc.iref.g.92"></span><span id="rfc.iref.g.93"></span><span id="rfc.iref.g.94"></span> <a href="#header.connection" class="smpl">Connection</a> = "Connection" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.connection" class="smpl">Connection-v</a>2069 <div id="rfc.figure.u.58"></div><pre class="inline"><span id="rfc.iref.g.91"></span><span id="rfc.iref.g.92"></span><span id="rfc.iref.g.93"></span> <a href="#header.connection" class="smpl">Connection</a> = "Connection" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.connection" class="smpl">Connection-v</a> 2026 2070 <a href="#header.connection" class="smpl">Connection-v</a> = 1#<a href="#header.connection" class="smpl">connection-token</a> 2027 2071 <a href="#header.connection" class="smpl">connection-token</a> = <a href="#rule.token.separators" class="smpl">token</a> … … 2036 2080 of the response. For example, 2037 2081 </p> 2038 <div id="rfc.figure.u. 60"></div><pre class="text"> Connection: close2082 <div id="rfc.figure.u.59"></div><pre class="text"> Connection: close 2039 2083 </pre><p id="rfc.section.9.1.p.8">in either the request or the response header fields indicates that the connection <em class="bcp14">SHOULD NOT</em> be considered "persistent" (<a href="#persistent.connections" title="Persistent Connections">Section 7.1</a>) after the current request/response is complete. 2040 2084 </p> … … 2055 2099 transfer-coding) that would have been sent in a 200 (OK) response. 2056 2100 </p> 2057 <div id="rfc.figure.u.6 1"></div><pre class="inline"><span id="rfc.iref.g.95"></span><span id="rfc.iref.g.96"></span> <a href="#header.content-length" class="smpl">Content-Length</a> = "Content-Length" ":" <a href="#rule.whitespace" class="smpl">OWS</a> 1*<a href="#header.content-length" class="smpl">Content-Length-v</a>2101 <div id="rfc.figure.u.60"></div><pre class="inline"><span id="rfc.iref.g.94"></span><span id="rfc.iref.g.95"></span> <a href="#header.content-length" class="smpl">Content-Length</a> = "Content-Length" ":" <a href="#rule.whitespace" class="smpl">OWS</a> 1*<a href="#header.content-length" class="smpl">Content-Length-v</a> 2058 2102 <a href="#header.content-length" class="smpl">Content-Length-v</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a> 2059 2103 </pre><p id="rfc.section.9.2.p.3">An example is</p> 2060 <div id="rfc.figure.u.6 2"></div><pre class="text"> Content-Length: 34952104 <div id="rfc.figure.u.61"></div><pre class="text"> Content-Length: 3495 2061 2105 </pre><p id="rfc.section.9.2.p.5">Implementations <em class="bcp14">SHOULD</em> use this field to indicate the message-body length when no transfer-coding is being applied and the payload's body length 2062 2106 can be determined prior to being transferred. <a href="#message.body" title="Message Body">Section 3.3</a> describes how recipients determine the length of a message-body. … … 2072 2116 as the Origination Date Field (orig-date) defined in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.4"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as described in <a href="#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 6.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format. 2073 2117 </p> 2074 <div id="rfc.figure.u.6 3"></div><pre class="inline"><span id="rfc.iref.g.97"></span><span id="rfc.iref.g.98"></span> <a href="#header.date" class="smpl">Date</a> = "Date" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.date" class="smpl">Date-v</a>2118 <div id="rfc.figure.u.62"></div><pre class="inline"><span id="rfc.iref.g.96"></span><span id="rfc.iref.g.97"></span> <a href="#header.date" class="smpl">Date</a> = "Date" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.date" class="smpl">Date-v</a> 2075 2119 <a href="#header.date" class="smpl">Date-v</a> = <a href="#date.time.formats.full.date" class="smpl">HTTP-date</a> 2076 2120 </pre><p id="rfc.section.9.3.p.3">An example is</p> 2077 <div id="rfc.figure.u.6 4"></div><pre class="text"> Date: Tue, 15 Nov 1994 08:12:31 GMT2121 <div id="rfc.figure.u.63"></div><pre class="text"> Date: Tue, 15 Nov 1994 08:12:31 GMT 2078 2122 </pre><p id="rfc.section.9.3.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases: 2079 2123 </p> … … 2113 2157 resource (generally an http URI, as described in <a href="#http.uri" title="http URI scheme">Section 2.6.1</a>). 2114 2158 </p> 2115 <div id="rfc.figure.u.6 5"></div><pre class="inline"><span id="rfc.iref.g.99"></span><span id="rfc.iref.g.100"></span> <a href="#header.host" class="smpl">Host</a> = "Host" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.host" class="smpl">Host-v</a>2159 <div id="rfc.figure.u.64"></div><pre class="inline"><span id="rfc.iref.g.98"></span><span id="rfc.iref.g.99"></span> <a href="#header.host" class="smpl">Host</a> = "Host" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.host" class="smpl">Host-v</a> 2116 2160 <a href="#header.host" class="smpl">Host-v</a> = <a href="#uri" class="smpl">uri-host</a> [ ":" <a href="#uri" class="smpl">port</a> ] ; <a href="#http.uri" title="http URI scheme">Section 2.6.1</a> 2117 2161 </pre><p id="rfc.section.9.4.p.4">A "host" without any trailing port information implies the default port for the service requested (e.g., "80" for an HTTP 2118 2162 URL). For example, a request on the origin server for <http://www.example.org/pub/WWW/> would properly include: 2119 2163 </p> 2120 <div id="rfc.figure.u.6 6"></div><pre class="text2">GET /pub/WWW/ HTTP/1.12164 <div id="rfc.figure.u.65"></div><pre class="text2">GET /pub/WWW/ HTTP/1.1 2121 2165 Host: www.example.org 2122 2166 </pre><p id="rfc.section.9.4.p.6">A client <em class="bcp14">MUST</em> include a Host header field in all HTTP/1.1 request messages. If the requested URI does not include an Internet host name … … 2135 2179 accept parameters (as described in <a href="#transfer.codings" title="Transfer Codings">Section 6.2</a>). 2136 2180 </p> 2137 <div id="rfc.figure.u.6 7"></div><pre class="inline"><span id="rfc.iref.g.101"></span><span id="rfc.iref.g.102"></span><span id="rfc.iref.g.103"></span><span id="rfc.iref.g.104"></span><span id="rfc.iref.g.105"></span> <a href="#header.te" class="smpl">TE</a> = "TE" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.te" class="smpl">TE-v</a>2181 <div id="rfc.figure.u.66"></div><pre class="inline"><span id="rfc.iref.g.100"></span><span id="rfc.iref.g.101"></span><span id="rfc.iref.g.102"></span><span id="rfc.iref.g.103"></span><span id="rfc.iref.g.104"></span> <a href="#header.te" class="smpl">TE</a> = "TE" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.te" class="smpl">TE-v</a> 2138 2182 <a href="#header.te" class="smpl">TE-v</a> = #<a href="#header.te" class="smpl">t-codings</a> 2139 2183 <a href="#header.te" class="smpl">t-codings</a> = "trailers" / ( <a href="#transfer.codings" class="smpl">transfer-extension</a> [ <a href="#header.te" class="smpl">te-params</a> ] ) … … 2144 2188 </p> 2145 2189 <p id="rfc.section.9.5.p.5">Examples of its use are:</p> 2146 <div id="rfc.figure.u.6 8"></div><pre class="text"> TE: deflate2190 <div id="rfc.figure.u.67"></div><pre class="text"> TE: deflate 2147 2191 TE: 2148 2192 TE: trailers, deflate;q=0.5 … … 2181 2225 with chunked transfer-coding. 2182 2226 </p> 2183 <div id="rfc.figure.u.6 9"></div><pre class="inline"><span id="rfc.iref.g.106"></span><span id="rfc.iref.g.107"></span> <a href="#header.trailer" class="smpl">Trailer</a> = "Trailer" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.trailer" class="smpl">Trailer-v</a>2227 <div id="rfc.figure.u.68"></div><pre class="inline"><span id="rfc.iref.g.105"></span><span id="rfc.iref.g.106"></span> <a href="#header.trailer" class="smpl">Trailer</a> = "Trailer" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.trailer" class="smpl">Trailer-v</a> 2184 2228 <a href="#header.trailer" class="smpl">Trailer-v</a> = 1#<a href="#header.fields" class="smpl">field-name</a> 2185 2229 </pre><p id="rfc.section.9.6.p.3">An HTTP/1.1 message <em class="bcp14">SHOULD</em> include a Trailer header field in a message using chunked transfer-coding with a non-empty trailer. Doing so allows the recipient … … 2202 2246 are not. 2203 2247 </p> 2204 <div id="rfc.figure.u. 70"></div><pre class="inline"><span id="rfc.iref.g.108"></span><span id="rfc.iref.g.109"></span> <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> = "Transfer-Encoding" ":" <a href="#rule.whitespace" class="smpl">OWS</a>2248 <div id="rfc.figure.u.69"></div><pre class="inline"><span id="rfc.iref.g.107"></span><span id="rfc.iref.g.108"></span> <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> = "Transfer-Encoding" ":" <a href="#rule.whitespace" class="smpl">OWS</a> 2205 2249 <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding-v</a> 2206 2250 <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding-v</a> = 1#<a href="#transfer.codings" class="smpl">transfer-coding</a> 2207 2251 </pre><p id="rfc.section.9.7.p.3">Transfer-codings are defined in <a href="#transfer.codings" title="Transfer Codings">Section 6.2</a>. An example is: 2208 2252 </p> 2209 <div id="rfc.figure.u.7 1"></div><pre class="text"> Transfer-Encoding: chunked2253 <div id="rfc.figure.u.70"></div><pre class="text"> Transfer-Encoding: chunked 2210 2254 </pre><p id="rfc.section.9.7.p.5">If multiple encodings have been applied to a representation, the transfer-codings <em class="bcp14">MUST</em> be listed in the order in which they were applied. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other header fields not defined by this specification. 2211 2255 </p> … … 2217 2261 if the server chooses to switch protocols. Servers can use it to indicate what protocols they are willing to switch to. 2218 2262 </p> 2219 <div id="rfc.figure.u.7 2"></div><pre class="inline"><span id="rfc.iref.g.110"></span><span id="rfc.iref.g.111"></span> <a href="#header.upgrade" class="smpl">Upgrade</a> = "Upgrade" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.upgrade" class="smpl">Upgrade-v</a>2263 <div id="rfc.figure.u.71"></div><pre class="inline"><span id="rfc.iref.g.109"></span><span id="rfc.iref.g.110"></span> <a href="#header.upgrade" class="smpl">Upgrade</a> = "Upgrade" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.upgrade" class="smpl">Upgrade-v</a> 2220 2264 <a href="#header.upgrade" class="smpl">Upgrade-v</a> = 1#<a href="#product.tokens" class="smpl">product</a> 2221 2265 </pre><p id="rfc.section.9.8.p.3">For example,</p> 2222 <div id="rfc.figure.u.7 3"></div><pre class="text"> Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x112266 <div id="rfc.figure.u.72"></div><pre class="text"> Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11 2223 2267 </pre><p id="rfc.section.9.8.p.5">The Upgrade header field is intended to provide a simple mechanism for transition from HTTP/1.1 to some other, incompatible 2224 2268 protocol. It does so by allowing the client to advertise its desire to use another protocol, such as a later version of HTTP … … 2274 2318 of all senders along the request/response chain. 2275 2319 </p> 2276 <div id="rfc.figure.u.7 4"></div><pre class="inline"><span id="rfc.iref.g.112"></span><span id="rfc.iref.g.113"></span><span id="rfc.iref.g.114"></span><span id="rfc.iref.g.115"></span><span id="rfc.iref.g.116"></span><span id="rfc.iref.g.117"></span><span id="rfc.iref.g.118"></span> <a href="#header.via" class="smpl">Via</a> = "Via" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.via" class="smpl">Via-v</a>2320 <div id="rfc.figure.u.73"></div><pre class="inline"><span id="rfc.iref.g.111"></span><span id="rfc.iref.g.112"></span><span id="rfc.iref.g.113"></span><span id="rfc.iref.g.114"></span><span id="rfc.iref.g.115"></span><span id="rfc.iref.g.116"></span><span id="rfc.iref.g.117"></span> <a href="#header.via" class="smpl">Via</a> = "Via" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.via" class="smpl">Via-v</a> 2277 2321 <a href="#header.via" class="smpl">Via-v</a> = 1#( <a href="#header.via" class="smpl">received-protocol</a> <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#header.via" class="smpl">received-by</a> 2278 2322 [ <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#rule.comment" class="smpl">comment</a> ] ) … … 2299 2343 server at www.example.com. The request received by www.example.com would then have the following Via header field: 2300 2344 </p> 2301 <div id="rfc.figure.u.7 5"></div><pre class="text"> Via: 1.0 fred, 1.1 p.example.net (Apache/1.1)2345 <div id="rfc.figure.u.74"></div><pre class="text"> Via: 1.0 fred, 1.1 p.example.net (Apache/1.1) 2302 2346 </pre><p id="rfc.section.9.9.p.9">Proxies and gateways used as a portal through a network firewall <em class="bcp14">SHOULD NOT</em>, by default, forward the names and ports of hosts within the firewall region. This information <em class="bcp14">SHOULD</em> only be propagated if explicitly enabled. If not enabled, the received-by host of any host behind the firewall <em class="bcp14">SHOULD</em> be replaced by an appropriate pseudonym for that host. 2303 2347 </p> … … 2305 2349 For example, 2306 2350 </p> 2307 <div id="rfc.figure.u.7 6"></div><pre class="text"> Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy2351 <div id="rfc.figure.u.75"></div><pre class="text"> Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy 2308 2352 </pre><p id="rfc.section.9.9.p.12">could be collapsed to</p> 2309 <div id="rfc.figure.u.7 7"></div><pre class="text"> Via: 1.0 ricky, 1.1 mertz, 1.0 lucy2353 <div id="rfc.figure.u.76"></div><pre class="text"> Via: 1.0 ricky, 1.1 mertz, 1.0 lucy 2310 2354 </pre><p id="rfc.section.9.9.p.14">Applications <em class="bcp14">SHOULD NOT</em> combine multiple entries unless they are all under the same organizational control and the hosts have already been replaced 2311 2355 by pseudonyms. Applications <em class="bcp14">MUST NOT</em> combine entries which have different received-protocol values. … … 2560 2604 <p id="rfc.section.10.5.p.2">The HTTP Status Code Registry located at <<a href="http://www.iana.org/assignments/http-upgrade-tokens/">http://www.iana.org/assignments/http-upgrade-tokens/</a>> shall be updated with the registration below: 2561 2605 </p> 2562 <div id="rfc.table.u. 1">2606 <div id="rfc.table.u.2"> 2563 2607 <table class="tt full left" cellpadding="3" cellspacing="0"> 2564 2608 <thead> … … 2686 2730 <tr> 2687 2731 <td class="reference"><b id="Part2">[Part2]</b></td> 2688 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), February 2011.2732 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft draft-ietf-httpbis-p2-semantics-latest (work in progress), March 2011. 2689 2733 </td> 2690 2734 </tr> 2691 2735 <tr> 2692 2736 <td class="reference"><b id="Part3">[Part3]</b></td> 2693 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), February 2011.2737 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft draft-ietf-httpbis-p3-payload-latest (work in progress), March 2011. 2694 2738 </td> 2695 2739 </tr> 2696 2740 <tr> 2697 2741 <td class="reference"><b id="Part6">[Part6]</b></td> 2698 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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>, <a href="mailto:mnot@mnot.net">Nottingham, M., 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-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), February 2011.2742 <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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>, <a href="mailto:mnot@mnot.net">Nottingham, M., 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-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft draft-ietf-httpbis-p6-cache-latest (work in progress), March 2011. 2699 2743 </td> 2700 2744 </tr> … … 3012 3056 </p> 3013 3057 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> 3014 <div id="rfc.figure.u.7 8"></div> <pre class="inline"><a href="#rule.whitespace" class="smpl">BWS</a> = OWS3058 <div id="rfc.figure.u.77"></div> <pre class="inline"><a href="#rule.whitespace" class="smpl">BWS</a> = OWS 3015 3059 3016 3060 <a href="#abnf.dependencies" class="smpl">Cache-Control</a> = <Cache-Control, defined in [Part6], Section 3.4> … … 3111 3155 <a href="#header.fields" class="smpl">field-value</a> = *( field-content / OWS ) 3112 3156 3113 <a href="#general.header.fields" class="smpl">general-header</a> = Cache-Control / Connection / Date / Pragma / Trailer3114 / Transfer-Encoding / Upgrade / Via / Warning / MIME-Version3115 3116 3157 <a href="#header.fields" class="smpl">header-field</a> = field-name ":" OWS [ field-value ] OWS 3117 3158 <a href="#preferred.date.format" class="smpl">hour</a> = 2DIGIT … … 3198 3239 3199 3240 <a href="#preferred.date.format" class="smpl">year</a> = 4DIGIT 3200 </pre> <div id="rfc.figure.u.79"></div> 3201 <p>ABNF diagnostics:</p><pre class="inline">; Chunked-Body defined but not used 3241 </pre> <div id="rfc.figure.u.78"></div> 3242 <p>ABNF diagnostics:</p><pre class="inline">; Cache-Control defined but not used 3243 ; Chunked-Body defined but not used 3244 ; Connection defined but not used 3202 3245 ; Content-Length defined but not used 3246 ; Date defined but not used 3203 3247 ; HTTP-message defined but not used 3204 3248 ; Host defined but not used 3249 ; MIME-Version defined but not used 3250 ; Pragma defined but not used 3205 3251 ; Request defined but not used 3206 3252 ; Response defined but not used 3207 3253 ; TE defined but not used 3254 ; Trailer defined but not used 3255 ; Transfer-Encoding defined but not used 3208 3256 ; URI-reference defined but not used 3209 ; general-header defined but not used 3257 ; Upgrade defined but not used 3258 ; Via defined but not used 3259 ; Warning defined but not used 3210 3260 ; http-URI defined but not used 3211 3261 ; https-URI defined but not used … … 3510 3560 </li> 3511 3561 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/240">http://tools.ietf.org/wg/httpbis/trac/ticket/240</a>>: "Migrate Upgrade details from RFC2817" 3562 </li> 3563 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>>: "untangle ABNFs for header fields" 3512 3564 </li> 3513 3565 </ul> … … 3564 3616 <li><tt>absolute-URI</tt> <a href="#rfc.iref.g.28"><b>2.6</b></a></li> 3565 3617 <li>ALPHA <a href="#rfc.iref.g.1"><b>1.2</b></a></li> 3566 <li><tt>asctime-date</tt> <a href="#rfc.iref.g.6 9"><b>6.1</b></a></li>3567 <li><tt>attribute</tt> <a href="#rfc.iref.g.7 3"><b>6.2</b></a></li>3618 <li><tt>asctime-date</tt> <a href="#rfc.iref.g.68"><b>6.1</b></a></li> 3619 <li><tt>attribute</tt> <a href="#rfc.iref.g.72"><b>6.2</b></a></li> 3568 3620 <li><tt>authority</tt> <a href="#rfc.iref.g.29"><b>2.6</b></a></li> 3569 3621 <li><tt>BWS</tt> <a href="#rfc.iref.g.15"><b>1.2.2</b></a></li> 3570 <li><tt>chunk</tt> <a href="#rfc.iref.g.7 8"><b>6.2.1</b></a></li>3571 <li><tt>chunk-data</tt> <a href="#rfc.iref.g.8 4"><b>6.2.1</b></a></li>3572 <li><tt>chunk-ext</tt> <a href="#rfc.iref.g.8 1"><b>6.2.1</b></a></li>3573 <li><tt>chunk-ext-name</tt> <a href="#rfc.iref.g.8 2"><b>6.2.1</b></a></li>3574 <li><tt>chunk-ext-val</tt> <a href="#rfc.iref.g.8 3"><b>6.2.1</b></a></li>3575 <li><tt>chunk-size</tt> <a href="#rfc.iref.g.7 9"><b>6.2.1</b></a></li>3576 <li><tt>Chunked-Body</tt> <a href="#rfc.iref.g.7 7"><b>6.2.1</b></a></li>3622 <li><tt>chunk</tt> <a href="#rfc.iref.g.77"><b>6.2.1</b></a></li> 3623 <li><tt>chunk-data</tt> <a href="#rfc.iref.g.83"><b>6.2.1</b></a></li> 3624 <li><tt>chunk-ext</tt> <a href="#rfc.iref.g.80"><b>6.2.1</b></a></li> 3625 <li><tt>chunk-ext-name</tt> <a href="#rfc.iref.g.81"><b>6.2.1</b></a></li> 3626 <li><tt>chunk-ext-val</tt> <a href="#rfc.iref.g.82"><b>6.2.1</b></a></li> 3627 <li><tt>chunk-size</tt> <a href="#rfc.iref.g.78"><b>6.2.1</b></a></li> 3628 <li><tt>Chunked-Body</tt> <a href="#rfc.iref.g.76"><b>6.2.1</b></a></li> 3577 3629 <li><tt>comment</tt> <a href="#rfc.iref.g.41"><b>3.2</b></a></li> 3578 <li><tt>Connection</tt> <a href="#rfc.iref.g.9 2"><b>9.1</b></a></li>3579 <li><tt>connection-token</tt> <a href="#rfc.iref.g.9 4"><b>9.1</b></a></li>3580 <li><tt>Connection-v</tt> <a href="#rfc.iref.g.9 3"><b>9.1</b></a></li>3581 <li><tt>Content-Length</tt> <a href="#rfc.iref.g.9 5"><b>9.2</b></a></li>3582 <li><tt>Content-Length-v</tt> <a href="#rfc.iref.g.9 6"><b>9.2</b></a></li>3630 <li><tt>Connection</tt> <a href="#rfc.iref.g.91"><b>9.1</b></a></li> 3631 <li><tt>connection-token</tt> <a href="#rfc.iref.g.93"><b>9.1</b></a></li> 3632 <li><tt>Connection-v</tt> <a href="#rfc.iref.g.92"><b>9.1</b></a></li> 3633 <li><tt>Content-Length</tt> <a href="#rfc.iref.g.94"><b>9.2</b></a></li> 3634 <li><tt>Content-Length-v</tt> <a href="#rfc.iref.g.95"><b>9.2</b></a></li> 3583 3635 <li>CR <a href="#rfc.iref.g.2"><b>1.2</b></a></li> 3584 3636 <li>CRLF <a href="#rfc.iref.g.3"><b>1.2</b></a></li> 3585 3637 <li><tt>ctext</tt> <a href="#rfc.iref.g.42"><b>3.2</b></a></li> 3586 3638 <li>CTL <a href="#rfc.iref.g.4"><b>1.2</b></a></li> 3587 <li><tt>Date</tt> <a href="#rfc.iref.g.9 7"><b>9.3</b></a></li>3588 <li><tt>Date-v</tt> <a href="#rfc.iref.g.9 8"><b>9.3</b></a></li>3589 <li><tt>date1</tt> <a href="#rfc.iref.g.5 6"><b>6.1</b></a></li>3590 <li><tt>date2</tt> <a href="#rfc.iref.g.7 5"><b>6.2</b></a></li>3591 <li><tt>date3</tt> <a href="#rfc.iref.g.7 6"><b>6.2</b></a></li>3592 <li><tt>day</tt> <a href="#rfc.iref.g.6 3"><b>6.1</b></a></li>3593 <li><tt>day-name</tt> <a href="#rfc.iref.g.6 1"><b>6.1</b></a></li>3594 <li><tt>day-name-l</tt> <a href="#rfc.iref.g.6 2"><b>6.1</b></a></li>3639 <li><tt>Date</tt> <a href="#rfc.iref.g.96"><b>9.3</b></a></li> 3640 <li><tt>Date-v</tt> <a href="#rfc.iref.g.97"><b>9.3</b></a></li> 3641 <li><tt>date1</tt> <a href="#rfc.iref.g.55"><b>6.1</b></a></li> 3642 <li><tt>date2</tt> <a href="#rfc.iref.g.74"><b>6.2</b></a></li> 3643 <li><tt>date3</tt> <a href="#rfc.iref.g.75"><b>6.2</b></a></li> 3644 <li><tt>day</tt> <a href="#rfc.iref.g.62"><b>6.1</b></a></li> 3645 <li><tt>day-name</tt> <a href="#rfc.iref.g.60"><b>6.1</b></a></li> 3646 <li><tt>day-name-l</tt> <a href="#rfc.iref.g.61"><b>6.1</b></a></li> 3595 3647 <li>DIGIT <a href="#rfc.iref.g.5"><b>1.2</b></a></li> 3596 3648 <li>DQUOTE <a href="#rfc.iref.g.6"><b>1.2</b></a></li> … … 3598 3650 <li><tt>field-name</tt> <a href="#rfc.iref.g.38"><b>3.2</b></a></li> 3599 3651 <li><tt>field-value</tt> <a href="#rfc.iref.g.39"><b>3.2</b></a></li> 3600 <li><tt>general-header</tt> <a href="#rfc.iref.g.45"><b>3.4</b></a></li> 3601 <li><tt>GMT</tt> <a href="#rfc.iref.g.66"><b>6.1</b></a></li> 3652 <li><tt>GMT</tt> <a href="#rfc.iref.g.65"><b>6.1</b></a></li> 3602 3653 <li><tt>header-field</tt> <a href="#rfc.iref.g.37"><b>3.2</b></a></li> 3603 3654 <li>HEXDIG <a href="#rfc.iref.g.7"><b>1.2</b></a></li> 3604 <li><tt>Host</tt> <a href="#rfc.iref.g.9 9"><b>9.4</b></a></li>3605 <li><tt>Host-v</tt> <a href="#rfc.iref.g. 100"><b>9.4</b></a></li>3606 <li><tt>hour</tt> <a href="#rfc.iref.g.5 8"><b>6.1</b></a></li>3607 <li><tt>HTTP-date</tt> <a href="#rfc.iref.g.5 4"><b>6.1</b></a></li>3655 <li><tt>Host</tt> <a href="#rfc.iref.g.98"><b>9.4</b></a></li> 3656 <li><tt>Host-v</tt> <a href="#rfc.iref.g.99"><b>9.4</b></a></li> 3657 <li><tt>hour</tt> <a href="#rfc.iref.g.57"><b>6.1</b></a></li> 3658 <li><tt>HTTP-date</tt> <a href="#rfc.iref.g.53"><b>6.1</b></a></li> 3608 3659 <li><tt>HTTP-message</tt> <a href="#rfc.iref.g.36"><b>3</b></a></li> 3609 3660 <li><tt>HTTP-Prot-Name</tt> <a href="#rfc.iref.g.26"><b>2.5</b></a></li> … … 3611 3662 <li><tt>HTTP-Version</tt> <a href="#rfc.iref.g.25"><b>2.5</b></a></li> 3612 3663 <li><tt>https-URI</tt> <a href="#rfc.iref.g.35"><b>2.6.2</b></a></li> 3613 <li><tt>last-chunk</tt> <a href="#rfc.iref.g. 80"><b>6.2.1</b></a></li>3664 <li><tt>last-chunk</tt> <a href="#rfc.iref.g.79"><b>6.2.1</b></a></li> 3614 3665 <li>LF <a href="#rfc.iref.g.8"><b>1.2</b></a></li> 3615 3666 <li><tt>message-body</tt> <a href="#rfc.iref.g.44"><b>3.3</b></a></li> 3616 <li><tt>Method</tt> <a href="#rfc.iref.g.4 8"><b>4.1.1</b></a></li>3617 <li><tt>minute</tt> <a href="#rfc.iref.g.5 9"><b>6.1</b></a></li>3618 <li><tt>month</tt> <a href="#rfc.iref.g.6 4"><b>6.1</b></a></li>3619 <li><tt>obs-date</tt> <a href="#rfc.iref.g.6 7"><b>6.1</b></a></li>3667 <li><tt>Method</tt> <a href="#rfc.iref.g.47"><b>4.1.1</b></a></li> 3668 <li><tt>minute</tt> <a href="#rfc.iref.g.58"><b>6.1</b></a></li> 3669 <li><tt>month</tt> <a href="#rfc.iref.g.63"><b>6.1</b></a></li> 3670 <li><tt>obs-date</tt> <a href="#rfc.iref.g.66"><b>6.1</b></a></li> 3620 3671 <li><tt>obs-text</tt> <a href="#rfc.iref.g.22"><b>1.2.2</b></a></li> 3621 3672 <li>OCTET <a href="#rfc.iref.g.9"><b>1.2</b></a></li> … … 3623 3674 <li><tt>path-absolute</tt> <a href="#rfc.iref.g.30"><b>2.6</b></a></li> 3624 3675 <li><tt>port</tt> <a href="#rfc.iref.g.31"><b>2.6</b></a></li> 3625 <li><tt>product</tt> <a href="#rfc.iref.g.8 9"><b>6.3</b></a></li>3626 <li><tt>product-version</tt> <a href="#rfc.iref.g. 90"><b>6.3</b></a></li>3627 <li><tt>protocol-name</tt> <a href="#rfc.iref.g.11 5"><b>9.9</b></a></li>3628 <li><tt>protocol-version</tt> <a href="#rfc.iref.g.11 6"><b>9.9</b></a></li>3629 <li><tt>pseudonym</tt> <a href="#rfc.iref.g.11 8"><b>9.9</b></a></li>3676 <li><tt>product</tt> <a href="#rfc.iref.g.88"><b>6.3</b></a></li> 3677 <li><tt>product-version</tt> <a href="#rfc.iref.g.89"><b>6.3</b></a></li> 3678 <li><tt>protocol-name</tt> <a href="#rfc.iref.g.114"><b>9.9</b></a></li> 3679 <li><tt>protocol-version</tt> <a href="#rfc.iref.g.115"><b>9.9</b></a></li> 3680 <li><tt>pseudonym</tt> <a href="#rfc.iref.g.117"><b>9.9</b></a></li> 3630 3681 <li><tt>qdtext</tt> <a href="#rfc.iref.g.21"><b>1.2.2</b></a></li> 3631 <li><tt>qdtext-nf</tt> <a href="#rfc.iref.g.8 7"><b>6.2.1</b></a></li>3682 <li><tt>qdtext-nf</tt> <a href="#rfc.iref.g.86"><b>6.2.1</b></a></li> 3632 3683 <li><tt>query</tt> <a href="#rfc.iref.g.32"><b>2.6</b></a></li> 3633 3684 <li><tt>quoted-cpair</tt> <a href="#rfc.iref.g.43"><b>3.2</b></a></li> 3634 3685 <li><tt>quoted-pair</tt> <a href="#rfc.iref.g.23"><b>1.2.2</b></a></li> 3635 <li><tt>quoted-str-nf</tt> <a href="#rfc.iref.g.8 6"><b>6.2.1</b></a></li>3686 <li><tt>quoted-str-nf</tt> <a href="#rfc.iref.g.85"><b>6.2.1</b></a></li> 3636 3687 <li><tt>quoted-string</tt> <a href="#rfc.iref.g.20"><b>1.2.2</b></a></li> 3637 <li><tt>qvalue</tt> <a href="#rfc.iref.g.9 1"><b>6.4</b></a></li>3638 <li><tt>Reason-Phrase</tt> <a href="#rfc.iref.g.5 3"><b>5.1.1</b></a></li>3639 <li><tt>received-by</tt> <a href="#rfc.iref.g.11 7"><b>9.9</b></a></li>3640 <li><tt>received-protocol</tt> <a href="#rfc.iref.g.11 4"><b>9.9</b></a></li>3641 <li><tt>Request</tt> <a href="#rfc.iref.g.4 6"><b>4</b></a></li>3642 <li><tt>Request-Line</tt> <a href="#rfc.iref.g.4 7"><b>4.1</b></a></li>3643 <li><tt>request-target</tt> <a href="#rfc.iref.g.4 9"><b>4.1.2</b></a></li>3644 <li><tt>Response</tt> <a href="#rfc.iref.g. 50"><b>5</b></a></li>3645 <li><tt>rfc1123-date</tt> <a href="#rfc.iref.g.5 5"><b>6.1</b></a></li>3646 <li><tt>rfc850-date</tt> <a href="#rfc.iref.g.6 8"><b>6.1</b></a></li>3688 <li><tt>qvalue</tt> <a href="#rfc.iref.g.90"><b>6.4</b></a></li> 3689 <li><tt>Reason-Phrase</tt> <a href="#rfc.iref.g.52"><b>5.1.1</b></a></li> 3690 <li><tt>received-by</tt> <a href="#rfc.iref.g.116"><b>9.9</b></a></li> 3691 <li><tt>received-protocol</tt> <a href="#rfc.iref.g.113"><b>9.9</b></a></li> 3692 <li><tt>Request</tt> <a href="#rfc.iref.g.45"><b>4</b></a></li> 3693 <li><tt>Request-Line</tt> <a href="#rfc.iref.g.46"><b>4.1</b></a></li> 3694 <li><tt>request-target</tt> <a href="#rfc.iref.g.48"><b>4.1.2</b></a></li> 3695 <li><tt>Response</tt> <a href="#rfc.iref.g.49"><b>5</b></a></li> 3696 <li><tt>rfc1123-date</tt> <a href="#rfc.iref.g.54"><b>6.1</b></a></li> 3697 <li><tt>rfc850-date</tt> <a href="#rfc.iref.g.67"><b>6.1</b></a></li> 3647 3698 <li><tt>RWS</tt> <a href="#rfc.iref.g.14"><b>1.2.2</b></a></li> 3648 <li><tt>second</tt> <a href="#rfc.iref.g. 60"><b>6.1</b></a></li>3699 <li><tt>second</tt> <a href="#rfc.iref.g.59"><b>6.1</b></a></li> 3649 3700 <li>SP <a href="#rfc.iref.g.10"><b>1.2</b></a></li> 3650 3701 <li><tt>special</tt> <a href="#rfc.iref.g.19"><b>1.2.2</b></a></li> 3651 <li><tt>Status-Code</tt> <a href="#rfc.iref.g.5 2"><b>5.1.1</b></a></li>3652 <li><tt>Status-Line</tt> <a href="#rfc.iref.g.5 1"><b>5.1</b></a></li>3653 <li><tt>t-codings</tt> <a href="#rfc.iref.g.10 3"><b>9.5</b></a></li>3702 <li><tt>Status-Code</tt> <a href="#rfc.iref.g.51"><b>5.1.1</b></a></li> 3703 <li><tt>Status-Line</tt> <a href="#rfc.iref.g.50"><b>5.1</b></a></li> 3704 <li><tt>t-codings</tt> <a href="#rfc.iref.g.102"><b>9.5</b></a></li> 3654 3705 <li><tt>tchar</tt> <a href="#rfc.iref.g.18"><b>1.2.2</b></a></li> 3655 <li><tt>TE</tt> <a href="#rfc.iref.g.10 1"><b>9.5</b></a></li>3656 <li><tt>te-ext</tt> <a href="#rfc.iref.g.10 5"><b>9.5</b></a></li>3657 <li><tt>te-params</tt> <a href="#rfc.iref.g.10 4"><b>9.5</b></a></li>3658 <li><tt>TE-v</tt> <a href="#rfc.iref.g.10 2"><b>9.5</b></a></li>3659 <li><tt>time-of-day</tt> <a href="#rfc.iref.g.5 7"><b>6.1</b></a></li>3706 <li><tt>TE</tt> <a href="#rfc.iref.g.100"><b>9.5</b></a></li> 3707 <li><tt>te-ext</tt> <a href="#rfc.iref.g.104"><b>9.5</b></a></li> 3708 <li><tt>te-params</tt> <a href="#rfc.iref.g.103"><b>9.5</b></a></li> 3709 <li><tt>TE-v</tt> <a href="#rfc.iref.g.101"><b>9.5</b></a></li> 3710 <li><tt>time-of-day</tt> <a href="#rfc.iref.g.56"><b>6.1</b></a></li> 3660 3711 <li><tt>token</tt> <a href="#rfc.iref.g.17"><b>1.2.2</b></a></li> 3661 <li><tt>Trailer</tt> <a href="#rfc.iref.g.10 6"><b>9.6</b></a></li>3662 <li><tt>trailer-part</tt> <a href="#rfc.iref.g.8 5"><b>6.2.1</b></a></li>3663 <li><tt>Trailer-v</tt> <a href="#rfc.iref.g.10 7"><b>9.6</b></a></li>3664 <li><tt>transfer-coding</tt> <a href="#rfc.iref.g. 70"><b>6.2</b></a></li>3665 <li><tt>Transfer-Encoding</tt> <a href="#rfc.iref.g.10 8"><b>9.7</b></a></li>3666 <li><tt>Transfer-Encoding-v</tt> <a href="#rfc.iref.g.10 9"><b>9.7</b></a></li>3667 <li><tt>transfer-extension</tt> <a href="#rfc.iref.g.7 1"><b>6.2</b></a></li>3668 <li><tt>transfer-parameter</tt> <a href="#rfc.iref.g.7 2"><b>6.2</b></a></li>3669 <li><tt>Upgrade</tt> <a href="#rfc.iref.g.1 10"><b>9.8</b></a></li>3670 <li><tt>Upgrade-v</tt> <a href="#rfc.iref.g.11 1"><b>9.8</b></a></li>3712 <li><tt>Trailer</tt> <a href="#rfc.iref.g.105"><b>9.6</b></a></li> 3713 <li><tt>trailer-part</tt> <a href="#rfc.iref.g.84"><b>6.2.1</b></a></li> 3714 <li><tt>Trailer-v</tt> <a href="#rfc.iref.g.106"><b>9.6</b></a></li> 3715 <li><tt>transfer-coding</tt> <a href="#rfc.iref.g.69"><b>6.2</b></a></li> 3716 <li><tt>Transfer-Encoding</tt> <a href="#rfc.iref.g.107"><b>9.7</b></a></li> 3717 <li><tt>Transfer-Encoding-v</tt> <a href="#rfc.iref.g.108"><b>9.7</b></a></li> 3718 <li><tt>transfer-extension</tt> <a href="#rfc.iref.g.70"><b>6.2</b></a></li> 3719 <li><tt>transfer-parameter</tt> <a href="#rfc.iref.g.71"><b>6.2</b></a></li> 3720 <li><tt>Upgrade</tt> <a href="#rfc.iref.g.109"><b>9.8</b></a></li> 3721 <li><tt>Upgrade-v</tt> <a href="#rfc.iref.g.110"><b>9.8</b></a></li> 3671 3722 <li><tt>uri-host</tt> <a href="#rfc.iref.g.33"><b>2.6</b></a></li> 3672 3723 <li><tt>URI-reference</tt> <a href="#rfc.iref.g.27"><b>2.6</b></a></li> 3673 <li><tt>value</tt> <a href="#rfc.iref.g.7 4"><b>6.2</b></a></li>3724 <li><tt>value</tt> <a href="#rfc.iref.g.73"><b>6.2</b></a></li> 3674 3725 <li>VCHAR <a href="#rfc.iref.g.11"><b>1.2</b></a></li> 3675 <li><tt>Via</tt> <a href="#rfc.iref.g.11 2"><b>9.9</b></a></li>3676 <li><tt>Via-v</tt> <a href="#rfc.iref.g.11 3"><b>9.9</b></a></li>3726 <li><tt>Via</tt> <a href="#rfc.iref.g.111"><b>9.9</b></a></li> 3727 <li><tt>Via-v</tt> <a href="#rfc.iref.g.112"><b>9.9</b></a></li> 3677 3728 <li><tt>word</tt> <a href="#rfc.iref.g.16"><b>1.2.2</b></a></li> 3678 3729 <li>WSP <a href="#rfc.iref.g.12"><b>1.2</b></a></li> 3679 <li><tt>year</tt> <a href="#rfc.iref.g.6 5"><b>6.1</b></a></li>3730 <li><tt>year</tt> <a href="#rfc.iref.g.64"><b>6.1</b></a></li> 3680 3731 </ul> 3681 3732 </li> 3682 <li>gzip (Coding Format) <a href="#rfc.iref.g.8 8">6.2.2.3</a></li>3733 <li>gzip (Coding Format) <a href="#rfc.iref.g.87">6.2.2.3</a></li> 3683 3734 </ul> 3684 3735 </li> … … 3759 3810 </ul> 3760 3811 </li> 3761 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">1.2.3</a>, <a href="#rfc.xref.Part6.2">1.2.3</a>, <a href="#rfc.xref.Part6.3">1.2.3</a>, <a href="#rfc.xref.Part6.4">2.3</a>, <a href="#rfc.xref.Part6.5">3.3</a>, <a href="#rfc.xref.Part6.6">3.4</a>, <a href="#rfc.xref.Part6.7">3.4</a>, <a href="#rfc.xref.Part6.8"> 3.4</a>, <a href="#rfc.xref.Part6.9">7.1.3.2</a>, <a href="#Part6"><b>13.1</b></a><ul>3812 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">1.2.3</a>, <a href="#rfc.xref.Part6.2">1.2.3</a>, <a href="#rfc.xref.Part6.3">1.2.3</a>, <a href="#rfc.xref.Part6.4">2.3</a>, <a href="#rfc.xref.Part6.5">3.3</a>, <a href="#rfc.xref.Part6.6">3.4</a>, <a href="#rfc.xref.Part6.7">3.4</a>, <a href="#rfc.xref.Part6.8">7.1.3.2</a>, <a href="#Part6"><b>13.1</b></a><ul> 3762 3813 <li><em>Section 2</em> <a href="#rfc.xref.Part6.4">2.3</a></li> 3763 3814 <li><em>Section 2.1.1</em> <a href="#rfc.xref.Part6.5">3.3</a></li> 3764 <li><em>Section 3.2</em> <a href="#rfc.xref.Part6.6">3.4</a></li> 3765 <li><em>Section 3.4</em> <a href="#rfc.xref.Part6.1">1.2.3</a>, <a href="#rfc.xref.Part6.2">1.2.3</a>, <a href="#rfc.xref.Part6.7">3.4</a></li> 3766 <li><em>Section 3.6</em> <a href="#rfc.xref.Part6.3">1.2.3</a>, <a href="#rfc.xref.Part6.8">3.4</a>, <a href="#rfc.xref.Part6.9">7.1.3.2</a></li> 3815 <li><em>Section 3.4</em> <a href="#rfc.xref.Part6.1">1.2.3</a>, <a href="#rfc.xref.Part6.2">1.2.3</a>, <a href="#rfc.xref.Part6.6">3.4</a></li> 3816 <li><em>Section 3.6</em> <a href="#rfc.xref.Part6.3">1.2.3</a>, <a href="#rfc.xref.Part6.7">3.4</a>, <a href="#rfc.xref.Part6.8">7.1.3.2</a></li> 3767 3817 </ul> 3768 3818 </li>
Note: See TracChangeset
for help on using the changeset viewer.