Changeset 138


Ignore:
Timestamp:
Jan 3, 2008, 10:03:02 AM (12 years ago)
Author:
julian.reschke@…
Message:

Make the historical change information (RFC2068 -> RFC2616) complete again.

Location:
draft-ietf-httpbis/latest
Files:
8 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r137 r138  
    19431943      <h2 id="rfc.references.1"><a href="#rfc.section.12.1" id="rfc.section.12.1">12.1</a> Normative References
    19441944      </h2>
    1945       <table summary="Normative References">                   
     1945      <table summary="Normative References">                     
    19461946         <tr>
    19471947            <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td>
     
    19591959            <td class="reference"><b id="Part3">[Part3]</b></td>
    19601960            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-latest (work in progress), January&nbsp;2008.
     1961            </td>
     1962         </tr>
     1963         <tr>
     1964            <td class="reference"><b id="Part5">[Part5]</b></td>
     1965            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), January&nbsp;2008.
    19611966            </td>
    19621967         </tr>
     
    22972302      <p id="rfc.section.D.3.p.2">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow
    22982303         for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are
    2299          computed.
     2304         computed. (Sections <a href="#transfer.codings" title="Transfer Codings">3.4</a>, <a href="#message.length" title="Message Length">4.4</a>, <a href="#header.content-length" id="rfc.xref.header.content-length.2" title="Content-Length">8.2</a>, see also <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>)
    23002305      </p>
    23012306      <p id="rfc.section.D.3.p.3">The use and interpretation of HTTP version numbers has been clarified by <a href="#RFC2145" id="rfc.xref.RFC2145.3"><cite title="Use and Interpretation of HTTP Version Numbers">[RFC2145]</cite></a>. Require proxies to upgrade requests to highest protocol version they support to deal with problems discovered in HTTP/1.0
     
    24142419                  <li class="indline1">Connection header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.connection.1">4.5</a>, <a class="iref" href="#rfc.xref.header.connection.2">7.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">7.1.3</a>, <a class="iref" href="#rfc.iref.c.6"><b>8.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.4">8.5</a>, <a class="iref" href="#rfc.xref.header.connection.5">8.8</a>, <a class="iref" href="#rfc.xref.header.connection.6">D.2</a>, <a class="iref" href="#rfc.xref.header.connection.7">D.4</a></li>
    24152420                  <li class="indline1">content negotiation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.2">1.3</a></li>
    2416                   <li class="indline1">Content-Length header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-length.1">4.4</a>, <a class="iref" href="#rfc.iref.c.7"><b>8.2</b></a></li>
     2421                  <li class="indline1">Content-Length header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-length.1">4.4</a>, <a class="iref" href="#rfc.iref.c.7"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">D.3</a></li>
    24172422               </ul>
    24182423            </li>
     
    25222527                     <ul class="ind">
    25232528                        <li class="indline1">Connection&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.connection.1">4.5</a>, <a class="iref" href="#rfc.xref.header.connection.2">7.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">7.1.3</a>, <a class="iref" href="#rfc.iref.h.1"><b>8.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.4">8.5</a>, <a class="iref" href="#rfc.xref.header.connection.5">8.8</a>, <a class="iref" href="#rfc.xref.header.connection.6">D.2</a>, <a class="iref" href="#rfc.xref.header.connection.7">D.4</a></li>
    2524                         <li class="indline1">Content-Length&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-length.1">4.4</a>, <a class="iref" href="#rfc.iref.h.2"><b>8.2</b></a></li>
     2529                        <li class="indline1">Content-Length&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-length.1">4.4</a>, <a class="iref" href="#rfc.iref.h.2"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">D.3</a></li>
    25252530                        <li class="indline1">Date&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.date.1">4.5</a>, <a class="iref" href="#rfc.iref.h.3"><b>8.3</b></a></li>
    25262531                        <li class="indline1">Host&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.5"><b>8.4</b></a>, <a class="iref" href="#rfc.xref.header.host.1">D.1.1</a></li>
     
    25752580                     </ul>
    25762581                  </li>
    2577                   <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1.3</a>, <a class="iref" href="#rfc.xref.Part3.2">1.3</a>, <a class="iref" href="#rfc.xref.Part3.3">1.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.4</a>, <a class="iref" href="#rfc.xref.Part3.5">2.2</a>, <a class="iref" href="#rfc.xref.Part3.6">3.4</a>, <a class="iref" href="#rfc.xref.Part3.7">3.4</a>, <a class="iref" href="#rfc.xref.Part3.8">4.2</a>, <a class="iref" href="#rfc.xref.Part3.9">5</a>, <a class="iref" href="#rfc.xref.Part3.10">6</a>, <a class="iref" href="#rfc.xref.Part3.11">8.5</a>, <a class="iref" href="#Part3"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part3.12">B</a><ul class="ind">
     2582                  <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1.3</a>, <a class="iref" href="#rfc.xref.Part3.2">1.3</a>, <a class="iref" href="#rfc.xref.Part3.3">1.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.4</a>, <a class="iref" href="#rfc.xref.Part3.5">2.2</a>, <a class="iref" href="#rfc.xref.Part3.6">3.4</a>, <a class="iref" href="#rfc.xref.Part3.7">3.4</a>, <a class="iref" href="#rfc.xref.Part3.8">4.2</a>, <a class="iref" href="#rfc.xref.Part3.9">5</a>, <a class="iref" href="#rfc.xref.Part3.10">6</a>, <a class="iref" href="#rfc.xref.Part3.11">8.5</a>, <a class="iref" href="#Part3"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part3.12">B</a>, <a class="iref" href="#rfc.xref.Part3.13">D.3</a><ul class="ind">
    25782583                        <li class="indline1"><em>Section 2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.6">3.4</a>, <a class="iref" href="#rfc.xref.Part3.7">3.4</a></li>
    25792584                        <li class="indline1"><em>Section 2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.5">2.2</a></li>
     
    25852590                     </ul>
    25862591                  </li>
    2587                   <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a>, <a class="iref" href="#rfc.xref.Part6.3">4.5</a>, <a class="iref" href="#rfc.xref.Part6.4">4.5</a>, <a class="iref" href="#rfc.xref.Part6.5">4.5</a>, <a class="iref" href="#Part6"><b>12.1</b></a><ul class="ind">
     2592                  <li class="indline1"><em>Part5</em>&nbsp;&nbsp;<a class="iref" href="#Part5"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part5.1">D.3</a></li>
     2593                  <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a>, <a class="iref" href="#rfc.xref.Part6.3">4.5</a>, <a class="iref" href="#rfc.xref.Part6.4">4.5</a>, <a class="iref" href="#rfc.xref.Part6.5">4.5</a>, <a class="iref" href="#Part6"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part6.6">D.3</a><ul class="ind">
    25882594                        <li class="indline1"><em>Section 2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a></li>
    25892595                        <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.3">4.5</a></li>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r137 r138  
    30163016</reference>
    30173017
     3018<reference anchor="Part5">
     3019  <front>
     3020    <title abbrev="HTTP/1.1">HTTP/1.1, part 5: Range Requests and Partial Responses</title>
     3021    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
     3022      <organization abbrev="Day Software">Day Software</organization>
     3023      <address><email>fielding@gbiv.com</email></address>
     3024    </author>
     3025    <author initials="J." surname="Gettys" fullname="Jim Gettys">
     3026      <organization>One Laptop per Child</organization>
     3027      <address><email>jg@laptop.org</email></address>
     3028    </author>
     3029    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
     3030      <organization abbrev="HP">Hewlett-Packard Company</organization>
     3031      <address><email>JeffMogul@acm.org</email></address>
     3032    </author>
     3033    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
     3034      <organization abbrev="Microsoft">Microsoft Corporation</organization>
     3035      <address><email>henrikn@microsoft.com</email></address>
     3036    </author>
     3037    <author initials="L." surname="Masinter" fullname="Larry Masinter">
     3038      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
     3039      <address><email>LMM@acm.org</email></address>
     3040    </author>
     3041    <author initials="P." surname="Leach" fullname="Paul J. Leach">
     3042      <organization abbrev="Microsoft">Microsoft Corporation</organization>
     3043      <address><email>paulle@microsoft.com</email></address>
     3044    </author>
     3045    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
     3046      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
     3047      <address><email>timbl@w3.org</email></address>
     3048    </author>
     3049    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
     3050      <organization abbrev="W3C">World Wide Web Consortium</organization>
     3051      <address><email>ylafon@w3.org</email></address>
     3052    </author>
     3053    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
     3054      <organization abbrev="greenbytes">greenbytes GmbH</organization>
     3055      <address><email>julian.reschke@greenbytes.de</email></address>
     3056    </author>
     3057    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
     3058  </front>
     3059  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;"/>
     3060  <x:source href="p5-range.xml" basename="p5-range"/>
     3061</reference>
     3062
    30183063<reference anchor="Part6">
    30193064  <front>
     
    38803925   required fixing exactly when chunked encoding is used (to allow for
    38813926   transfer encoding that may not be self delimiting); it was important
    3882    to straighten out exactly how message lengths are computed.
     3927   to straighten out exactly how message lengths are computed. (Sections
     3928   <xref target="transfer.codings" format="counter"/>, <xref target="message.length" format="counter"/>,
     3929   <xref target="header.content-length" format="counter"/>,
     3930   see also <xref target="Part3"/>, <xref target="Part5"/> and <xref target="Part6"/>)
    38833931</t>
    38843932<t>
  • draft-ietf-httpbis/latest/p3-payload.html

    r137 r138  
    14581458      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
    14591459      <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;<a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>
    1460       <p id="rfc.section.C.1.p.1">Charset wildcarding is introduced to avoid explosion of character set names in accept headers. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;5.2</a>)
    1461       </p>
    1462       <p id="rfc.section.C.1.p.2">Content-Base was deleted from the specification: it was not implemented widely, and there is no simple, safe way to introduce
     1460      <p id="rfc.section.C.1.p.1">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow
     1461         for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are
     1462         computed. (<a href="#entity.length" title="Entity Length">Section&nbsp;3.2.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.3"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     1463      </p>
     1464      <p id="rfc.section.C.1.p.2">Charset wildcarding is introduced to avoid explosion of character set names in accept headers. (<a href="#header.accept-charset" id="rfc.xref.header.accept-charset.2" title="Accept-Charset">Section&nbsp;5.2</a>)
     1465      </p>
     1466      <p id="rfc.section.C.1.p.3">Content-Base was deleted from the specification: it was not implemented widely, and there is no simple, safe way to introduce
    14631467         it without a robust extension mechanism. In addition, it is used in a similar, but not identical fashion in MHTML <a href="#RFC2557" id="rfc.xref.RFC2557.2"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>.
    14641468      </p>
    1465       <p id="rfc.section.C.1.p.3">A content-coding of "identity" was introduced, to solve problems discovered in caching. (<a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>)
    1466       </p>
    1467       <p id="rfc.section.C.1.p.4">Quality Values of zero should indicate that "I don't want something" to allow clients to refuse a representation. (<a href="#quality.values" title="Quality Values">Section&nbsp;2.4</a>)
    1468       </p>
    1469       <p id="rfc.section.C.1.p.5">The Alternates<span id="rfc.iref.a.5"></span><span id="rfc.iref.h.11"></span>, Content-Version<span id="rfc.iref.c.8"></span><span id="rfc.iref.h.12"></span>, Derived-From<span id="rfc.iref.d.2"></span><span id="rfc.iref.h.13"></span>, Link<span id="rfc.iref.l.1"></span><span id="rfc.iref.h.14"></span>, URI<span id="rfc.iref.u.1"></span><span id="rfc.iref.h.15"></span>, Public<span id="rfc.iref.p.1"></span><span id="rfc.iref.h.16"></span> and Content-Base<span id="rfc.iref.c.9"></span><span id="rfc.iref.h.17"></span> header fields were defined in previous versions of this specification, but not commonly implemented. See <a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
     1469      <p id="rfc.section.C.1.p.4">A content-coding of "identity" was introduced, to solve problems discovered in caching. (<a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>)
     1470      </p>
     1471      <p id="rfc.section.C.1.p.5">Quality Values of zero should indicate that "I don't want something" to allow clients to refuse a representation. (<a href="#quality.values" title="Quality Values">Section&nbsp;2.4</a>)
     1472      </p>
     1473      <p id="rfc.section.C.1.p.6">The Alternates<span id="rfc.iref.a.5"></span><span id="rfc.iref.h.11"></span>, Content-Version<span id="rfc.iref.c.8"></span><span id="rfc.iref.h.12"></span>, Derived-From<span id="rfc.iref.d.2"></span><span id="rfc.iref.h.13"></span>, Link<span id="rfc.iref.l.1"></span><span id="rfc.iref.h.14"></span>, URI<span id="rfc.iref.u.1"></span><span id="rfc.iref.h.15"></span>, Public<span id="rfc.iref.p.1"></span><span id="rfc.iref.h.16"></span> and Content-Base<span id="rfc.iref.c.9"></span><span id="rfc.iref.h.17"></span> header fields were defined in previous versions of this specification, but not commonly implemented. See <a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.
    14701474      </p>
    14711475      <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
     
    16431647            </li>
    16441648            <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
    1645                   <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">3.1</a>, <a class="iref" href="#rfc.xref.Part1.2">3.2</a>, <a class="iref" href="#rfc.xref.Part1.3">3.2.2</a>, <a class="iref" href="#Part1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part1.4">A.5</a><ul class="ind">
     1649                  <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">3.1</a>, <a class="iref" href="#rfc.xref.Part1.2">3.2</a>, <a class="iref" href="#rfc.xref.Part1.3">3.2.2</a>, <a class="iref" href="#Part1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part1.4">A.5</a>, <a class="iref" href="#rfc.xref.Part1.5">C.1</a><ul class="ind">
    16461650                        <li class="indline1"><em>Section 4.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">3.2</a></li>
    16471651                        <li class="indline1"><em>Section 4.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.3">3.2.2</a></li>
     
    16591663                     </ul>
    16601664                  </li>
    1661                   <li class="indline1"><em>Part5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">2.3.2</a>, <a class="iref" href="#rfc.xref.Part5.2">3.1</a>, <a class="iref" href="#Part5"><b>9.1</b></a><ul class="ind">
     1665                  <li class="indline1"><em>Part5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">2.3.2</a>, <a class="iref" href="#rfc.xref.Part5.2">3.1</a>, <a class="iref" href="#Part5"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part5.3">C.1</a><ul class="ind">
    16621666                        <li class="indline1"><em>Section 5.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.2">3.1</a></li>
    16631667                        <li class="indline1"><em>Section A</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">2.3.2</a></li>
    16641668                     </ul>
    16651669                  </li>
    1666                   <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">3.1</a>, <a class="iref" href="#rfc.xref.Part6.2">4.1</a>, <a class="iref" href="#rfc.xref.Part6.3">5.7</a>, <a class="iref" href="#Part6"><b>9.1</b></a><ul class="ind">
     1670                  <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">3.1</a>, <a class="iref" href="#rfc.xref.Part6.2">4.1</a>, <a class="iref" href="#rfc.xref.Part6.3">5.7</a>, <a class="iref" href="#Part6"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part6.4">C.1</a><ul class="ind">
    16671671                        <li class="indline1"><em>Section 2.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.3">5.7</a></li>
    16681672                        <li class="indline1"><em>Section 3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">3.1</a></li>
  • draft-ietf-httpbis/latest/p3-payload.xml

    r137 r138  
    22752275<section title="Changes from RFC 2068" anchor="changes.from.rfc.2068">
    22762276<t>
     2277   Transfer-coding and message lengths all interact in ways that
     2278   required fixing exactly when chunked encoding is used (to allow for
     2279   transfer encoding that may not be self delimiting); it was important
     2280   to straighten out exactly how message lengths are computed.
     2281   (<xref target="entity.length"/>, see also <xref target="Part1"/>,
     2282   <xref target="Part5"/> and <xref target="Part6"/>).
     2283</t>
     2284<t>
    22772285   Charset wildcarding is introduced to avoid explosion of character set
    22782286   names in accept headers. (<xref target="header.accept-charset"/>)
  • draft-ietf-httpbis/latest/p5-range.html

    r137 r138  
    787787      <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References
    788788      </h2>
    789       <table summary="Normative References">       
     789      <table summary="Normative References">           
    790790         <tr>
    791791            <td class="reference"><b id="Part1">[Part1]</b></td>
     
    794794         </tr>
    795795         <tr>
     796            <td class="reference"><b id="Part3">[Part3]</b></td>
     797            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-latest (work in progress), January&nbsp;2008.
     798            </td>
     799         </tr>
     800         <tr>
    796801            <td class="reference"><b id="Part4">[Part4]</b></td>
    797802            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), January&nbsp;2008.
     803            </td>
     804         </tr>
     805         <tr>
     806            <td class="reference"><b id="Part6">[Part6]</b></td>
     807            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), January&nbsp;2008.
    798808            </td>
    799809         </tr>
     
    885895      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
    886896      <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;<a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>
    887       <p id="rfc.section.B.1.p.1">There are situations where a server (especially a proxy) does not know the full length of a response but is capable of serving
     897      <p id="rfc.section.B.1.p.1">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow
     898         for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are
     899         computed. (<a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>)
     900      </p>
     901      <p id="rfc.section.B.1.p.2">There are situations where a server (especially a proxy) does not know the full length of a response but is capable of serving
    888902         a byterange request. We therefore need a mechanism to allow byteranges with a content-range not indicating the full length
    889          of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range.4" title="Content-Range">Section&nbsp;5.2</a>)
    890       </p>
    891       <p id="rfc.section.B.1.p.2">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send
     903         of the message. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section&nbsp;5.2</a>)
     904      </p>
     905      <p id="rfc.section.B.1.p.3">Range request responses would become very verbose if all meta-data were always returned; by allowing the server to only send
    892906         needed headers in a 206 response, this problem can be avoided.
    893907      </p>
    894       <p id="rfc.section.B.1.p.3">Fix problem with unsatisfiable range requests; there are two cases: syntactic problems, and range doesn't exist in the document.
     908      <p id="rfc.section.B.1.p.4">Fix problem with unsatisfiable range requests; there are two cases: syntactic problems, and range doesn't exist in the document.
    895909         The 416 status code was needed to resolve this ambiguity needed to indicate an error for a byte range request that falls outside
    896          of the actual contents of a document. (Section <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">3.2</a>, <a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">5.2</a>)
     910         of the actual contents of a document. (Section <a href="#status.416" id="rfc.xref.status.416.2" title="416 Requested Range Not Satisfiable">3.2</a>, <a href="#header.content-range" id="rfc.xref.header.content-range.6" title="Content-Range">5.2</a>)
    897911      </p>
    898912      <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
     
    963977            </li>
    964978            <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind">
    965                   <li class="indline1">Content-Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.c.1"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a></li>
     979                  <li class="indline1">Content-Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.c.1"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.6">B.1</a></li>
    966980               </ul>
    967981            </li>
     
    9971011                     <ul class="ind">
    9981012                        <li class="indline1">Accept-Ranges&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.1"><b>5.1</b></a></li>
    999                         <li class="indline1">Content-Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a></li>
     1013                        <li class="indline1">Content-Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-range.1">2</a>, <a class="iref" href="#rfc.xref.header.content-range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.content-range.3">3.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>5.2</b></a>, <a class="iref" href="#rfc.xref.header.content-range.4">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.5">B.1</a>, <a class="iref" href="#rfc.xref.header.content-range.6">B.1</a></li>
    10001014                        <li class="indline1">If-Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.if-range.1">3.1</a>, <a class="iref" href="#rfc.iref.h.3"><b>5.3</b></a>, <a class="iref" href="#rfc.xref.header.if-range.2">5.4.2</a></li>
    10011015                        <li class="indline1">Range&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.range.3">3.2</a>, <a class="iref" href="#rfc.iref.h.4"><b>5.4</b></a></li>
     
    10201034            </li>
    10211035            <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
    1022                   <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">7</a>, <a class="iref" href="#Part1"><b>9.1</b></a></li>
     1036                  <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">7</a>, <a class="iref" href="#Part1"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part1.2">B.1</a></li>
     1037                  <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#Part3"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part3.1">B.1</a></li>
    10231038                  <li class="indline1"><em>Part4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">4</a>, <a class="iref" href="#Part4"><b>9.1</b></a><ul class="ind">
    10241039                        <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part4.1">4</a></li>
    10251040                     </ul>
    10261041                  </li>
     1042                  <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#Part6"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.Part6.1">B.1</a></li>
    10271043               </ul>
    10281044            </li>
  • draft-ietf-httpbis/latest/p5-range.xml

    r137 r138  
    778778</reference>
    779779
     780<reference anchor="Part3">
     781  <front>
     782    <title abbrev="HTTP/1.1">HTTP/1.1, part 3: Message Payload and Content Negotiation</title>
     783    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
     784      <organization abbrev="Day Software">Day Software</organization>
     785      <address><email>fielding@gbiv.com</email></address>
     786    </author>
     787    <author initials="J." surname="Gettys" fullname="Jim Gettys">
     788      <organization>One Laptop per Child</organization>
     789      <address><email>jg@laptop.org</email></address>
     790    </author>
     791    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
     792      <organization abbrev="HP">Hewlett-Packard Company</organization>
     793      <address><email>JeffMogul@acm.org</email></address>
     794    </author>
     795    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
     796      <organization abbrev="Microsoft">Microsoft Corporation</organization>
     797      <address><email>henrikn@microsoft.com</email></address>
     798    </author>
     799    <author initials="L." surname="Masinter" fullname="Larry Masinter">
     800      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
     801      <address><email>LMM@acm.org</email></address>
     802    </author>
     803    <author initials="P." surname="Leach" fullname="Paul J. Leach">
     804      <organization abbrev="Microsoft">Microsoft Corporation</organization>
     805      <address><email>paulle@microsoft.com</email></address>
     806    </author>
     807    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
     808      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
     809      <address><email>timbl@w3.org</email></address>
     810    </author>
     811    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
     812      <organization abbrev="W3C">World Wide Web Consortium</organization>
     813      <address><email>ylafon@w3.org</email></address>
     814    </author>
     815    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
     816      <organization abbrev="greenbytes">greenbytes GmbH</organization>
     817      <address><email>julian.reschke@greenbytes.de</email></address>
     818    </author>
     819    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
     820  </front>
     821  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p3-payload-&ID-VERSION;"/>
     822  <x:source href="p3-payload.xml" basename="p3-payload"/>
     823</reference>
     824
    780825<reference anchor="Part4">
    781826  <front>
     
    821866  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p4-conditional-&ID-VERSION;"/>
    822867  <x:source href="p4-conditional.xml" basename="p4-conditional"/>
     868</reference>
     869
     870<reference anchor="Part6">
     871  <front>
     872    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
     873    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
     874      <organization abbrev="Day Software">Day Software</organization>
     875      <address><email>fielding@gbiv.com</email></address>
     876    </author>
     877    <author initials="J." surname="Gettys" fullname="Jim Gettys">
     878      <organization>One Laptop per Child</organization>
     879      <address><email>jg@laptop.org</email></address>
     880    </author>
     881    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
     882      <organization abbrev="HP">Hewlett-Packard Company</organization>
     883      <address><email>JeffMogul@acm.org</email></address>
     884    </author>
     885    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
     886      <organization abbrev="Microsoft">Microsoft Corporation</organization>
     887      <address><email>henrikn@microsoft.com</email></address>
     888    </author>
     889    <author initials="L." surname="Masinter" fullname="Larry Masinter">
     890      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
     891      <address><email>LMM@acm.org</email></address>
     892    </author>
     893    <author initials="P." surname="Leach" fullname="Paul J. Leach">
     894      <organization abbrev="Microsoft">Microsoft Corporation</organization>
     895      <address><email>paulle@microsoft.com</email></address>
     896    </author>
     897    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
     898      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
     899      <address><email>timbl@w3.org</email></address>
     900    </author>
     901    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
     902      <organization abbrev="W3C">World Wide Web Consortium</organization>
     903      <address><email>ylafon@w3.org</email></address>
     904    </author>
     905    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
     906      <organization abbrev="greenbytes">greenbytes GmbH</organization>
     907      <address><email>julian.reschke@greenbytes.de</email></address>
     908    </author>
     909    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
     910  </front>
     911  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
     912  <x:source href="p6-cache.xml" basename="p6-cache"/>
    823913</reference>
    824914
     
    9721062<section title="Changes from RFC 2068" anchor="changes.from.rfc.2068">
    9731063<t>
     1064   Transfer-coding and message lengths all interact in ways that
     1065   required fixing exactly when chunked encoding is used (to allow for
     1066   transfer encoding that may not be self delimiting); it was important
     1067   to straighten out exactly how message lengths are computed.
     1068   (<xref target="header.content-range"/>,
     1069   see also <xref target="Part1"/>, <xref target="Part3"/> and <xref target="Part6"/>)
     1070</t>
     1071<t>
    9741072   There are situations where a server (especially a proxy) does not
    9751073   know the full length of a response but is capable of serving a
  • draft-ietf-httpbis/latest/p6-cache.html

    r137 r138  
    18141814      <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
    18151815      <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a id="changes.from.rfc.2068" href="#changes.from.rfc.2068">Changes from RFC 2068</a></h2>
    1816       <p id="rfc.section.A.1.p.1">A case was missed in the Cache-Control model of HTTP/1.1; s-maxage was introduced to add this missing case. (Sections <a href="#response.cacheability" title="Response Cacheability">2.4</a>, <a href="#header.cache-control" id="rfc.xref.header.cache-control.11" title="Cache-Control">3.2</a>, <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">3.2.3</a>)
    1817       </p>
    1818       <p id="rfc.section.A.1.p.2">The Cache-Control: max-age directive was not properly defined for responses. (<a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">Section&nbsp;3.2.3</a>)
    1819       </p>
    1820       <p id="rfc.section.A.1.p.3">Warnings could be cached incorrectly, or not updated appropriately. (Section <a href="#warnings" title="Warnings">2.1.2</a>, <a href="#expiration.calculations" title="Expiration Calculations">2.2.4</a>, <a href="#non-modifiable.headers" title="Non-modifiable Headers">2.5.2</a>, <a href="#combining.headers" title="Combining Headers">2.5.3</a>, <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">3.2.3</a>, and <a href="#header.warning" id="rfc.xref.header.warning.6" title="Warning">3.6</a>) Warning also needed to be a general header, as PUT or other methods may have need for it in requests.
     1816      <p id="rfc.section.A.1.p.1">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow
     1817         for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are
     1818         computed. (<a href="#non-modifiable.headers" title="Non-modifiable Headers">Section&nbsp;2.5.2</a>, see also <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> and <a href="#Part5" id="rfc.xref.Part5.3"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>)
     1819      </p>
     1820      <p id="rfc.section.A.1.p.2">A case was missed in the Cache-Control model of HTTP/1.1; s-maxage was introduced to add this missing case. (Sections <a href="#response.cacheability" title="Response Cacheability">2.4</a>, <a href="#header.cache-control" id="rfc.xref.header.cache-control.11" title="Cache-Control">3.2</a>, <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">3.2.3</a>)
     1821      </p>
     1822      <p id="rfc.section.A.1.p.3">The Cache-Control: max-age directive was not properly defined for responses. (<a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">Section&nbsp;3.2.3</a>)
     1823      </p>
     1824      <p id="rfc.section.A.1.p.4">Warnings could be cached incorrectly, or not updated appropriately. (Section <a href="#warnings" title="Warnings">2.1.2</a>, <a href="#expiration.calculations" title="Expiration Calculations">2.2.4</a>, <a href="#non-modifiable.headers" title="Non-modifiable Headers">2.5.2</a>, <a href="#combining.headers" title="Combining Headers">2.5.3</a>, <a href="#modifications.of.the.basic.expiration.mechanism" title="Modifications of the Basic Expiration Mechanism">3.2.3</a>, and <a href="#header.warning" id="rfc.xref.header.warning.6" title="Warning">3.6</a>) Warning also needed to be a general header, as PUT or other methods may have need for it in requests.
    18211825      </p>
    18221826      <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
     
    20182022            </li>
    20192023            <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
    2020                   <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">2.2.3</a>, <a class="iref" href="#rfc.xref.Part1.2">2.5.1</a>, <a class="iref" href="#rfc.xref.Part1.3">2.5.2</a>, <a class="iref" href="#rfc.xref.Part1.4">2.5.2</a>, <a class="iref" href="#rfc.xref.Part1.5">2.6</a>, <a class="iref" href="#rfc.xref.Part1.6">3.3</a>, <a class="iref" href="#Part1"><b>7.1</b></a><ul class="ind">
     2024                  <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">2.2.3</a>, <a class="iref" href="#rfc.xref.Part1.2">2.5.1</a>, <a class="iref" href="#rfc.xref.Part1.3">2.5.2</a>, <a class="iref" href="#rfc.xref.Part1.4">2.5.2</a>, <a class="iref" href="#rfc.xref.Part1.5">2.6</a>, <a class="iref" href="#rfc.xref.Part1.6">3.3</a>, <a class="iref" href="#Part1"><b>7.1</b></a>, <a class="iref" href="#rfc.xref.Part1.7">A.1</a><ul class="ind">
    20212025                        <li class="indline1"><em>Section 3.3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.6">3.3</a></li>
    20222026                        <li class="indline1"><em>Section 4.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.5">2.6</a></li>
     
    20302034                     </ul>
    20312035                  </li>
    2032                   <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">2.5.2</a>, <a class="iref" href="#rfc.xref.Part3.2">2.6</a>, <a class="iref" href="#Part3"><b>7.1</b></a><ul class="ind">
     2036                  <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">2.5.2</a>, <a class="iref" href="#rfc.xref.Part3.2">2.6</a>, <a class="iref" href="#Part3"><b>7.1</b></a>, <a class="iref" href="#rfc.xref.Part3.3">A.1</a><ul class="ind">
    20332037                        <li class="indline1"><em>Section 3.2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">2.5.2</a></li>
    20342038                        <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.2">2.6</a></li>
     
    20412045                     </ul>
    20422046                  </li>
    2043                   <li class="indline1"><em>Part5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">2.5.3</a>, <a class="iref" href="#rfc.xref.Part5.2">2.8</a>, <a class="iref" href="#Part5"><b>7.1</b></a><ul class="ind">
     2047                  <li class="indline1"><em>Part5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">2.5.3</a>, <a class="iref" href="#rfc.xref.Part5.2">2.8</a>, <a class="iref" href="#Part5"><b>7.1</b></a>, <a class="iref" href="#rfc.xref.Part5.3">A.1</a><ul class="ind">
    20442048                        <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">2.5.3</a>, <a class="iref" href="#rfc.xref.Part5.2">2.8</a></li>
    20452049                     </ul>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r137 r138  
    28172817<section title="Changes from RFC 2068" anchor="changes.from.rfc.2068">
    28182818<t>
     2819   Transfer-coding and message lengths all interact in ways that
     2820   required fixing exactly when chunked encoding is used (to allow for
     2821   transfer encoding that may not be self delimiting); it was important
     2822   to straighten out exactly how message lengths are computed.
     2823   (<xref target="non-modifiable.headers"/>,
     2824   see also <xref target="Part1"/>, <xref target="Part3"/> and <xref target="Part5"/>)
     2825</t>
     2826<t>
    28192827   A case was missed in the Cache-Control model of HTTP/1.1; s-maxage
    28202828   was introduced to add this missing case. (Sections <xref target="response.cacheability" format="counter"/>,
Note: See TracChangeset for help on using the changeset viewer.