Changeset 560 for draft-ietf-httpbis
- Timestamp:
- 12/03/09 10:55:19 (13 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 7 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r547 r560 375 375 <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D"> 376 376 <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E"> 377 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 6, 2009-03-07 10:31:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">377 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.427, 2009-03-12 09:45:39, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 378 378 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 379 379 <meta name="DC.Creator" content="Fielding, R."> … … 471 471 <tr> 472 472 <td class="header left"></td> 473 <td class="header right">March 7, 2009</td>473 <td class="header right">March 12, 2009</td> 474 474 </tr> 475 475 </table> … … 843 843 <div id="rfc.iref.u.2"></div> 844 844 <h3 id="rfc.section.2.1.2"><a href="#rfc.section.2.1.2">2.1.2</a> <a id="https.uri" href="#https.uri">https URI scheme</a></h3> 845 <p id="rfc.section.2.1.2.p.1"> <span class="comment" >[rfc.comment.1: TBD: Define and explain purpose of https scheme.]</span>845 <p id="rfc.section.2.1.2.p.1"> <span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: TBD: Define and explain purpose of https scheme.]</span> 846 846 </p> 847 847 <dl class="empty"> … … 927 927 </p> 928 928 <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a> <a id="http.proxy" href="#http.proxy">Use of HTTP for proxy communication</a></h2> 929 <p id="rfc.section.2.3.p.1"> <span class="comment" >[rfc.comment.2: TBD: Configured to use HTTP to proxy HTTP or other protocols.]</span>929 <p id="rfc.section.2.3.p.1"> <span class="comment" id="rfc.comment.2">[<a href="#rfc.comment.2" class="smpl">rfc.comment.2</a>: TBD: Configured to use HTTP to proxy HTTP or other protocols.]</span> 930 930 </p> 931 931 <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a> <a id="http.intercept" href="#http.intercept">Interception of HTTP for access control</a></h2> 932 <p id="rfc.section.2.4.p.1"> <span class="comment" >[rfc.comment.3: TBD: Interception of HTTP traffic for initiating access control.]</span>932 <p id="rfc.section.2.4.p.1"> <span class="comment" id="rfc.comment.3">[<a href="#rfc.comment.3" class="smpl">rfc.comment.3</a>: TBD: Interception of HTTP traffic for initiating access control.]</span> 933 933 </p> 934 934 <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a> <a id="http.others" href="#http.others">Use of HTTP by other protocols</a></h2> 935 <p id="rfc.section.2.5.p.1"> <span class="comment" >[rfc.comment.4: TBD: Profiles of HTTP defined by other protocol. Extensions of HTTP like WebDAV.]</span>935 <p id="rfc.section.2.5.p.1"> <span class="comment" id="rfc.comment.4">[<a href="#rfc.comment.4" class="smpl">rfc.comment.4</a>: TBD: Profiles of HTTP defined by other protocol. Extensions of HTTP like WebDAV.]</span> 936 936 </p> 937 937 <h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a> <a id="http.media" href="#http.media">Use of HTTP by media type specification</a></h2> 938 <p id="rfc.section.2.6.p.1"> <span class="comment" >[rfc.comment.5: TBD: Instructions on composing HTTP requests via hypertext formats.]</span>938 <p id="rfc.section.2.6.p.1"> <span class="comment" id="rfc.comment.5">[<a href="#rfc.comment.5" class="smpl">rfc.comment.5</a>: TBD: Instructions on composing HTTP requests via hypertext formats.]</span> 939 939 </p> 940 940 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1> -
draft-ietf-httpbis/latest/p2-semantics.html
r547 r560 371 371 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 372 372 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 373 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 6, 2009-03-07 10:31:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">373 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.427, 2009-03-12 09:45:39, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 374 374 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 375 375 <meta name="DC.Creator" content="Fielding, R."> … … 468 468 <tr> 469 469 <td class="header left"></td> 470 <td class="header right">March 7, 2009</td>470 <td class="header right">March 12, 2009</td> 471 471 </tr> 472 472 </table> -
draft-ietf-httpbis/latest/p3-payload.html
r547 r560 379 379 <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D"> 380 380 <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E"> 381 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 6, 2009-03-07 10:31:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">381 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.427, 2009-03-12 09:45:39, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 382 382 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 383 383 <meta name="DC.Creator" content="Fielding, R."> … … 475 475 <tr> 476 476 <td class="header left"></td> 477 <td class="header right">March 7, 2009</td>477 <td class="header right">March 12, 2009</td> 478 478 </tr> 479 479 </table> -
draft-ietf-httpbis/latest/p4-conditional.html
r547 r560 368 368 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 369 369 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 370 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 6, 2009-03-07 10:31:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">370 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.427, 2009-03-12 09:45:39, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 371 371 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 372 372 <meta name="DC.Creator" content="Fielding, R."> … … 464 464 <tr> 465 465 <td class="header left"></td> 466 <td class="header right">March 7, 2009</td>466 <td class="header right">March 12, 2009</td> 467 467 </tr> 468 468 </table> -
draft-ietf-httpbis/latest/p5-range.html
r547 r560 368 368 <link rel="Appendix" title="C Collected ABNF" href="#rfc.section.C"> 369 369 <link rel="Appendix" title="D Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.D"> 370 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 6, 2009-03-07 10:31:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">370 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.427, 2009-03-12 09:45:39, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 371 371 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 372 372 <meta name="DC.Creator" content="Fielding, R."> … … 464 464 <tr> 465 465 <td class="header left"></td> 466 <td class="header right">March 7, 2009</td>466 <td class="header right">March 12, 2009</td> 467 467 </tr> 468 468 </table> -
draft-ietf-httpbis/latest/p6-cache.html
r555 r560 372 372 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 373 373 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 374 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 6, 2009-03-07 10:31:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">374 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.427, 2009-03-12 09:45:39, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 375 375 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 376 376 <meta name="DC.Creator" content="Fielding, R."> … … 468 468 <tr> 469 469 <td class="header left"></td> 470 <td class="header right">March 1 1, 2009</td>470 <td class="header right">March 12, 2009</td> 471 471 </tr> 472 472 </table> … … 719 719 </p> 720 720 <ul> 721 <li>The presented Request-URI and that of the stored response match (see <span class="comment" >[rfc.comment.1: TBD]</span>), and721 <li>The presented Request-URI and that of the stored response match (see <span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: TBD]</span>), and 722 722 </li> 723 723 <li>the request method associated with the stored response allows it to be used for the presented request, and</li> … … 737 737 </li> 738 738 </ul> 739 <p id="rfc.section.2.2.p.2"> <span class="comment" >[rfc.comment.2: TODO: define method cacheability for GET, HEAD and POST in p2-semantics.]</span>740 </p> 741 <p id="rfc.section.2.2.p.3">When a stored response is used to satisfy a request, caches <em class="bcp14">MUST</em> include a single Age header field <a href="#header.age" id="rfc.xref.header.age.1" title="Age">Section 3.1</a> in the response with a value equal to the stored response's current_age; see <a href="#age.calculations" title="Calculating Age">Section 2.3.2</a>. <span class="comment" >[rfc.comment.3: DISCUSS: this currently includes successfully validated responses.]</span>739 <p id="rfc.section.2.2.p.2"> <span class="comment" id="rfc.comment.2">[<a href="#rfc.comment.2" class="smpl">rfc.comment.2</a>: TODO: define method cacheability for GET, HEAD and POST in p2-semantics.]</span> 740 </p> 741 <p id="rfc.section.2.2.p.3">When a stored response is used to satisfy a request, caches <em class="bcp14">MUST</em> include a single Age header field <a href="#header.age" id="rfc.xref.header.age.1" title="Age">Section 3.1</a> in the response with a value equal to the stored response's current_age; see <a href="#age.calculations" title="Calculating Age">Section 2.3.2</a>. <span class="comment" id="rfc.comment.3">[<a href="#rfc.comment.3" class="smpl">rfc.comment.3</a>: DISCUSS: this currently includes successfully validated responses.]</span> 742 742 </p> 743 743 <p id="rfc.section.2.2.p.4">Requests with methods that are unsafe (<a href="p2-semantics.html#safe.methods" title="Safe Methods">Section 7.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) <em class="bcp14">MUST</em> be written through the cache to the origin server; i.e., A cache must not reply to such a request before having forwarded … … 749 749 forward a request with "Cache-Control: max-age=0" or "Cache-Control: no-cache" to disambiguate which response to use. 750 750 </p> 751 <p id="rfc.section.2.2.p.7"> <span class="comment" >[rfc.comment.4: TODO: end-to-end and hop-by-hop headers, non-modifiable headers removed; re-spec in p1]</span>751 <p id="rfc.section.2.2.p.7"> <span class="comment" id="rfc.comment.4">[<a href="#rfc.comment.4" class="smpl">rfc.comment.4</a>: TODO: end-to-end and hop-by-hop headers, non-modifiable headers removed; re-spec in p1]</span> 752 752 </p> 753 753 <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a> <a id="expiration.model" href="#expiration.model">Freshness Model</a></h2> … … 760 760 </p> 761 761 <p id="rfc.section.2.3.p.3">If an origin server wishes to force a cache to validate every request, it can assign an explicit expiration time in the past. 762 This means that the response is always stale, so that caches should validate it before using it for subsequent requests. <span class="comment" >[rfc.comment.5: This wording may cause confusion, because the response may still be served stale.]</span>762 This means that the response is always stale, so that caches should validate it before using it for subsequent requests. <span class="comment" id="rfc.comment.5">[<a href="#rfc.comment.5" class="smpl">rfc.comment.5</a>: This wording may cause confusion, because the response may still be served stale.]</span> 763 763 </p> 764 764 <p id="rfc.section.2.3.p.4">Since origin servers do not always provide explicit expiration times, HTTP caches may also assign heuristic expiration times … … 774 774 with the effect of either increasing or loosening constraints on freshness. See <a href="#cache-request-directive" title="Request Cache-Control Directives">Section 3.2.1</a>. 775 775 </p> 776 <p id="rfc.section.2.3.p.8"> <span class="comment" >[rfc.comment.6: ISSUE: there are not requirements directly applying to cache-request-directives and freshness.]</span>776 <p id="rfc.section.2.3.p.8"> <span class="comment" id="rfc.comment.6">[<a href="#rfc.comment.6" class="smpl">rfc.comment.6</a>: ISSUE: there are not requirements directly applying to cache-request-directives and freshness.]</span> 777 777 </p> 778 778 <p id="rfc.section.2.3.p.9">Note that freshness applies only to cache operation; it cannot be used to force a user agent to refresh its display or reload … … 801 801 <p id="rfc.section.2.3.1.1.p.3">Also, if the response has a Last-Modified header (<a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 6.6</a> of <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>), the heuristic expiration value <em class="bcp14">SHOULD</em> be no more than some fraction of the interval since that time. A typical setting of this fraction might be 10%. 802 802 </p> 803 <p id="rfc.section.2.3.1.1.p.4"> <span class="comment" >[rfc.comment.7: REVIEW: took away HTTP/1.0 query string heuristic uncacheability.]</span>803 <p id="rfc.section.2.3.1.1.p.4"> <span class="comment" id="rfc.comment.7">[<a href="#rfc.comment.7" class="smpl">rfc.comment.7</a>: REVIEW: took away HTTP/1.0 query string heuristic uncacheability.]</span> 804 804 </p> 805 805 <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a> <a id="age.calculations" href="#age.calculations">Calculating Age</a></h3> … … 874 874 </p> 875 875 <p id="rfc.section.2.4.p.4">If instead the cache receives a full response (i.e., one with a response body), it is used to satisfy the request and replace 876 the stored response. <span class="comment" >[rfc.comment.8: Should there be a requirement here?]</span>876 the stored response. <span class="comment" id="rfc.comment.8">[<a href="#rfc.comment.8" class="smpl">rfc.comment.8</a>: Should there be a requirement here?]</span> 877 877 </p> 878 878 <p id="rfc.section.2.4.p.5">If a cache receives a 5xx response while attempting to validate a response, it <em class="bcp14">MAY</em> either forward this response to the requesting client, or act as if the server failed to respond. In the latter case, it <em class="bcp14">MAY</em> return a previously stored response (which <em class="bcp14">SHOULD</em> include the 111 warn-code; see <a href="#header.warning" id="rfc.xref.header.warning.2" title="Warning">Section 3.6</a>) unless the stored response includes the "must-revalidate" cache directive (see <a href="#serving.stale.responses" title="Serving Stale Responses">Section 2.3.3</a>). … … 891 891 attacks. 892 892 </p> 893 <p id="rfc.section.2.5.p.4"> <span class="comment" >[rfc.comment.9: TODO: "host part" needs to be specified better.]</span>893 <p id="rfc.section.2.5.p.4"> <span class="comment" id="rfc.comment.9">[<a href="#rfc.comment.9" class="smpl">rfc.comment.9</a>: TODO: "host part" needs to be specified better.]</span> 894 894 </p> 895 895 <p id="rfc.section.2.5.p.5">A cache that passes through requests for methods it does not understand <em class="bcp14">SHOULD</em> invalidate the Request-URI. … … 901 901 change at the origin server might not have gone through the cache where a response is stored. 902 902 </p> 903 <p id="rfc.section.2.5.p.8"> <span class="comment" >[rfc.comment.10: TODO: specify that only successful (2xx, 3xx?) responses invalidate.]</span>903 <p id="rfc.section.2.5.p.8"> <span class="comment" id="rfc.comment.10">[<a href="#rfc.comment.10" class="smpl">rfc.comment.10</a>: TODO: specify that only successful (2xx, 3xx?) responses invalidate.]</span> 904 904 </p> 905 905 <h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a> <a id="caching.negotiated.responses" href="#caching.negotiated.responses">Caching Negotiated Responses</a></h2> … … 910 910 </p> 911 911 <p id="rfc.section.2.6.p.3">The selecting request-headers from two requests are defined to match if and only if the selecting request-headers in the first 912 request can be transformed to the selecting request-headers in the second request by adding or removing linear white space <span class="comment" >[rfc.comment.11: [ref]]</span> at places where this is allowed by the corresponding ABNF, and/or combining multiple message-header fields with the same field913 name following the rules about message headers in <a href="p1-messaging.html#message.headers" title="Message Headers">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. <span class="comment" >[rfc.comment.12: DISCUSS: header-specific canonicalisation]</span>912 request can be transformed to the selecting request-headers in the second request by adding or removing linear white space <span class="comment" id="rfc.comment.11">[<a href="#rfc.comment.11" class="smpl">rfc.comment.11</a>: [ref]]</span> at places where this is allowed by the corresponding ABNF, and/or combining multiple message-header fields with the same field 913 name following the rules about message headers in <a href="p1-messaging.html#message.headers" title="Message Headers">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. <span class="comment" id="rfc.comment.12">[<a href="#rfc.comment.12" class="smpl">rfc.comment.12</a>: DISCUSS: header-specific canonicalisation]</span> 914 914 </p> 915 915 <p id="rfc.section.2.6.p.4">A Vary header field-value of "*" always fails to match, and subsequent requests to that resource can only be properly interpreted … … 924 924 <p id="rfc.section.2.6.p.7">If a cache receives a successful response whose Content-Location field matches that of an existing stored response for the 925 925 same Request-URI, whose entity-tag differs from that of the existing stored response, and whose Date is more recent than that 926 of the existing response, the existing response <em class="bcp14">SHOULD NOT</em> be returned in response to future requests and <em class="bcp14">SHOULD</em> be deleted from the cache.<span class="comment" >[rfc.comment.13: DISCUSS: Not sure if this is necessary.]</span>926 of the existing response, the existing response <em class="bcp14">SHOULD NOT</em> be returned in response to future requests and <em class="bcp14">SHOULD</em> be deleted from the cache.<span class="comment" id="rfc.comment.13">[<a href="#rfc.comment.13" class="smpl">rfc.comment.13</a>: DISCUSS: Not sure if this is necessary.]</span> 927 927 </p> 928 928 <h2 id="rfc.section.2.7"><a href="#rfc.section.2.7">2.7</a> <a id="combining.headers" href="#combining.headers">Combining Responses</a></h2> … … 947 947 all such old headers <em class="bcp14">MUST</em> be replaced. It <em class="bcp14">MAY</em> store the combined entity-body. 948 948 </p> 949 <p id="rfc.section.2.7.p.5"> <span class="comment" >[rfc.comment.14: ISSUE: discuss how to handle HEAD updates]</span>949 <p id="rfc.section.2.7.p.5"> <span class="comment" id="rfc.comment.14">[<a href="#rfc.comment.14" class="smpl">rfc.comment.14</a>: ISSUE: discuss how to handle HEAD updates]</span> 950 950 </p> 951 951 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="header.fields" href="#header.fields">Header Field Definitions</a></h1> … … 1033 1033 time. If max-stale is assigned a value, then the client is willing to accept a response that has exceeded its expiration time 1034 1034 by no more than the specified number of seconds. If no value is assigned to max-stale, then the client is willing to accept 1035 a stale response of any age. <span class="comment" >[rfc.comment.15: of any staleness? --mnot]</span></dd>1035 a stale response of any age. <span class="comment" id="rfc.comment.15">[<a href="#rfc.comment.15" class="smpl">rfc.comment.15</a>: of any staleness? --mnot]</span></dd> 1036 1036 </dl> 1037 1037 <p id="rfc.section.3.2.1.p.6"> <span id="rfc.iref.c.8"></span> <span id="rfc.iref.m.3"></span> min-fresh … … 1534 1534 <p id="rfc.section.A.1.p.2">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow 1535 1535 for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are 1536 computed. (see also <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> and <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) <span class="comment" >[rfc.comment.16: This used to refer to the text about non-modifiable headers, and will have to be updated later on. --jre]</span>1537 </p> 1538 <p id="rfc.section.A.1.p.3">Proxies should be able to add Content-Length when appropriate. <span class="comment" >[rfc.comment.17: This used to refer to the text about non-modifiable headers, and will have to be updated later on. --jre]</span>1536 computed. (see also <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> and <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) <span class="comment" id="rfc.comment.16">[<a href="#rfc.comment.16" class="smpl">rfc.comment.16</a>: This used to refer to the text about non-modifiable headers, and will have to be updated later on. --jre]</span> 1537 </p> 1538 <p id="rfc.section.A.1.p.3">Proxies should be able to add Content-Length when appropriate. <span class="comment" id="rfc.comment.17">[<a href="#rfc.comment.17" class="smpl">rfc.comment.17</a>: This used to refer to the text about non-modifiable headers, and will have to be updated later on. --jre]</span> 1539 1539 </p> 1540 1540 <p id="rfc.section.A.1.p.4">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send -
draft-ietf-httpbis/latest/p7-auth.html
r547 r560 365 365 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> 366 366 <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C"> 367 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.42 6, 2009-03-07 10:31:10, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">367 <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.427, 2009-03-12 09:45:39, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 368 368 <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 369 369 <meta name="DC.Creator" content="Fielding, R."> … … 462 462 <tr> 463 463 <td class="header left"></td> 464 <td class="header right">March 7, 2009</td>464 <td class="header right">March 12, 2009</td> 465 465 </tr> 466 466 </table> … … 747 747 </p> 748 748 <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="ack" href="#ack">Acknowledgments</a></h1> 749 <p id="rfc.section.6.p.1"> <span class="comment" >[rfc.comment.1: TBD.]</span>749 <p id="rfc.section.6.p.1"> <span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: TBD.]</span> 750 750 </p> 751 751 <h1 id="rfc.references"><a id="rfc.section.7" href="#rfc.section.7">7.</a> References
Note: See TracChangeset
for help on using the changeset viewer.