Changeset 139

Timestamp:

03/01/08 21:17:48 (15 years ago)

Author:

julian.reschke@…

Message:

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

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (1 diff)
• p1-messaging.xml (modified) (1 diff)
• p6-cache.html (modified) (1 diff)
• p6-cache.xml (modified) (2 diffs)

draft-ietf-httpbis/latest/p1-messaging.html

@@ -2307 +2307 @@
          implementations (<a href="#http.version" title="HTTP Version">Section&nbsp;3.1</a>)
       </p>
-      <p id="rfc.section.D.3.p.4">Proxies should be able to add Content-Length when appropriate.</p>
-      <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
+      <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
          become as full fledged as content-codings. This involves adding an IANA registry for transfer-codings (separate from content
          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

@@ -3937 +3937 @@
 </t>
 <t>
-   Proxies should be able to add Content-Length when appropriate.
-</t>
-<t>
    Transfer-coding had significant problems, particularly with
    interactions with chunked encoding. The solution is that transfer-codings

draft-ietf-httpbis/latest/p6-cache.html

@@ -1814 +1814 @@
       <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
       <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>
-      <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
+      <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>)
+      </p>
+      <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
          for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are
          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>)
       </p>
-      <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>)
-      </p>
-      <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>)
-      </p>
-      <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.
+      <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>)
+      </p>
+      <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>)
+      </p>
+      <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.
       </p>
       <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

@@ -2817 +2817 @@
 <section title="Changes from RFC 2068" anchor="changes.from.rfc.2068">
 <t>
+   A case was missed in the Cache-Control model of HTTP/1.1; s-maxage
+   was introduced to add this missing case. (Sections <xref target="response.cacheability" format="counter"/>,
+   <xref target="header.cache-control" format="counter"/>,
+   <xref target="modifications.of.the.basic.expiration.mechanism" format="counter"/>)
+</t>
+<t>
    Transfer-coding and message lengths all interact in ways that
    required fixing exactly when chunked encoding is used (to allow for
@@ -2825 +2831 @@
 </t>
 <t>
-   A case was missed in the Cache-Control model of HTTP/1.1; s-maxage
-   was introduced to add this missing case. (Sections <xref target="response.cacheability" format="counter"/>,
-   <xref target="header.cache-control" format="counter"/>,
-   <xref target="modifications.of.the.basic.expiration.mechanism" format="counter"/>)
+   Proxies should be able to add Content-Length when appropriate.
+   (<xref target="non-modifiable.headers"/>)
 </t>
 <t>