Changeset 139


Ignore:
Timestamp:
Jan 3, 2008, 1:17:48 PM (12 years ago)
Author:
julian.reschke@…
Message:

Move change note from p1 to p6 (where the changed text lives)

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

Legend:

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

    r138 r139  
    23072307         implementations (<a href="#http.version" title="HTTP Version">Section&nbsp;3.1</a>)
    23082308      </p>
    2309       <p id="rfc.section.D.3.p.4">Proxies should be able to add Content-Length when appropriate.</p>
    2310       <p id="rfc.section.D.3.p.5">Transfer-coding had significant problems, particularly with interactions with chunked encoding. The solution is that transfer-codings
     2309      <p id="rfc.section.D.3.p.4">Transfer-coding had significant problems, particularly with interactions with chunked encoding. The solution is that transfer-codings
    23112310         become as full fledged as content-codings. This involves adding an IANA registry for transfer-codings (separate from content
    23122311         codings), a new header field (TE) and enabling trailer headers in the future. Transfer encoding is a major performance benefit,
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r138 r139  
    39373937</t>
    39383938<t>
    3939    Proxies should be able to add Content-Length when appropriate.
    3940 </t>
    3941 <t>
    39423939   Transfer-coding had significant problems, particularly with
    39433940   interactions with chunked encoding. The solution is that transfer-codings
  • draft-ietf-httpbis/latest/p6-cache.html

    r138 r139  
    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">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow
     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">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow
    18171819         for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are
    18181820         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>)
    18191821      </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.
     1822      <p id="rfc.section.A.1.p.3">Proxies should be able to add Content-Length when appropriate. (<a href="#non-modifiable.headers" title="Non-modifiable Headers">Section&nbsp;2.5.2</a>)
     1823      </p>
     1824      <p id="rfc.section.A.1.p.4">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>)
     1825      </p>
     1826      <p id="rfc.section.A.1.p.5">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.
    18251827      </p>
    18261828      <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>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r138 r139  
    28172817<section title="Changes from RFC 2068" anchor="changes.from.rfc.2068">
    28182818<t>
     2819   A case was missed in the Cache-Control model of HTTP/1.1; s-maxage
     2820   was introduced to add this missing case. (Sections <xref target="response.cacheability" format="counter"/>,
     2821   <xref target="header.cache-control" format="counter"/>,
     2822   <xref target="modifications.of.the.basic.expiration.mechanism" format="counter"/>)
     2823</t>
     2824<t>
    28192825   Transfer-coding and message lengths all interact in ways that
    28202826   required fixing exactly when chunked encoding is used (to allow for
     
    28252831</t>
    28262832<t>
    2827    A case was missed in the Cache-Control model of HTTP/1.1; s-maxage
    2828    was introduced to add this missing case. (Sections <xref target="response.cacheability" format="counter"/>,
    2829    <xref target="header.cache-control" format="counter"/>,
    2830    <xref target="modifications.of.the.basic.expiration.mechanism" format="counter"/>)
     2833   Proxies should be able to add Content-Length when appropriate.
     2834   (<xref target="non-modifiable.headers"/>)
    28312835</t>
    28322836<t>
Note: See TracChangeset for help on using the changeset viewer.