[html5] r6749 - [e] (0) Talk more about HTTP caching semantics in the context of appcache. Fixin [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2011-10-24 20:18:41 -0700 (Mon, 24 Oct 2011)
New Revision: 6749

Modified:
   complete.html
   index
   source
Log:
[e] (0) Talk more about HTTP caching semantics in the context of appcache.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=14431

Modified: complete.html
===================================================================
--- complete.html	2011-10-25 03:09:46 UTC (rev 6748)
+++ complete.html	2011-10-25 03:18:41 UTC (rev 6749)
@@ -67112,8 +67112,9 @@
     <p><i>Fetching the manifest</i>: <a href=#fetch>Fetch</a> the resource
     from <var title="">manifest URL</var> with the <i>synchronous
     flag</i> set, and let <var title="">manifest</var> be that
-    resource.</p> <!-- http-origin privacy sensitive, though it
-    doesn't matter, since this can never be cross-origin -->
+    resource. HTTP caching semantics should be honored for this
+    request.</p> <!-- http-origin privacy sensitive, though it doesn't
+    matter, since this can never be cross-origin -->
 
     <p>If the resource is labeled with the <a href=#mime-type>MIME type</a>
     <code><a href=#text/cache-manifest>text/cache-manifest</a></code>, either with no parameters or
@@ -67443,8 +67444,9 @@
       server-side errors.</p>
 
       <p class=note>Except for the "no-store" directive, HTTP
-      caching rules are ignored for the purposes of the
-      <a href=#application-cache-download-process>application cache download process</a>.</p>
+      caching rules that would cause a file to be expired or otherwise
+      not cached are ignored for the purposes of the <a href=#application-cache-download-process>application
+      cache download process</a>.</p>
 
      </li>
 
@@ -67566,10 +67568,18 @@
 
     <p><a href=#fetch>Fetch</a> the resource from <var title="">manifest
     URL</var> again, with the <i>synchronous flag</i> set, and let
-    <var title="">second manifest</var> be that resource.</p> <!--
+    <var title="">second manifest</var> be that resource. HTTP caching
+    semantics should again be honored for this request.</p> <!--
     http-origin privacy sensitive, though it doesn't matter, since
     this can never be cross-origin -->
 
+    <p class=note>Since caching can be honored, authors are
+    encouraged to avoid setting the cache headers on the manifest in
+    such a way that the user agent would simply not contact the
+    network for this second request; otherwise, the user agent would
+    not notice if the cache had changed during the cache update
+    process.</p>
+
    </li>
 
    <li>

Modified: index
===================================================================
--- index	2011-10-25 03:09:46 UTC (rev 6748)
+++ index	2011-10-25 03:18:41 UTC (rev 6749)
@@ -67112,8 +67112,9 @@
     <p><i>Fetching the manifest</i>: <a href=#fetch>Fetch</a> the resource
     from <var title="">manifest URL</var> with the <i>synchronous
     flag</i> set, and let <var title="">manifest</var> be that
-    resource.</p> <!-- http-origin privacy sensitive, though it
-    doesn't matter, since this can never be cross-origin -->
+    resource. HTTP caching semantics should be honored for this
+    request.</p> <!-- http-origin privacy sensitive, though it doesn't
+    matter, since this can never be cross-origin -->
 
     <p>If the resource is labeled with the <a href=#mime-type>MIME type</a>
     <code><a href=#text/cache-manifest>text/cache-manifest</a></code>, either with no parameters or
@@ -67443,8 +67444,9 @@
       server-side errors.</p>
 
       <p class=note>Except for the "no-store" directive, HTTP
-      caching rules are ignored for the purposes of the
-      <a href=#application-cache-download-process>application cache download process</a>.</p>
+      caching rules that would cause a file to be expired or otherwise
+      not cached are ignored for the purposes of the <a href=#application-cache-download-process>application
+      cache download process</a>.</p>
 
      </li>
 
@@ -67566,10 +67568,18 @@
 
     <p><a href=#fetch>Fetch</a> the resource from <var title="">manifest
     URL</var> again, with the <i>synchronous flag</i> set, and let
-    <var title="">second manifest</var> be that resource.</p> <!--
+    <var title="">second manifest</var> be that resource. HTTP caching
+    semantics should again be honored for this request.</p> <!--
     http-origin privacy sensitive, though it doesn't matter, since
     this can never be cross-origin -->
 
+    <p class=note>Since caching can be honored, authors are
+    encouraged to avoid setting the cache headers on the manifest in
+    such a way that the user agent would simply not contact the
+    network for this second request; otherwise, the user agent would
+    not notice if the cache had changed during the cache update
+    process.</p>
+
    </li>
 
    <li>

Modified: source
===================================================================
--- source	2011-10-25 03:09:46 UTC (rev 6748)
+++ source	2011-10-25 03:18:41 UTC (rev 6749)
@@ -76249,8 +76249,9 @@
     <p><i>Fetching the manifest</i>: <span>Fetch</span> the resource
     from <var title="">manifest URL</var> with the <i>synchronous
     flag</i> set, and let <var title="">manifest</var> be that
-    resource.</p> <!-- http-origin privacy sensitive, though it
-    doesn't matter, since this can never be cross-origin -->
+    resource. HTTP caching semantics should be honored for this
+    request.</p> <!-- http-origin privacy sensitive, though it doesn't
+    matter, since this can never be cross-origin -->
 
     <p>If the resource is labeled with the <span>MIME type</span>
     <code>text/cache-manifest</code>, either with no parameters or
@@ -76642,8 +76643,9 @@
       server-side errors.</p>
 
       <p class="note">Except for the "no-store" directive, HTTP
-      caching rules are ignored for the purposes of the
-      <span>application cache download process</span>.</p>
+      caching rules that would cause a file to be expired or otherwise
+      not cached are ignored for the purposes of the <span>application
+      cache download process</span>.</p>
 
      </li>
 
@@ -76789,10 +76791,18 @@
 
     <p><span>Fetch</span> the resource from <var title="">manifest
     URL</var> again, with the <i>synchronous flag</i> set, and let
-    <var title="">second manifest</var> be that resource.</p> <!--
+    <var title="">second manifest</var> be that resource. HTTP caching
+    semantics should again be honored for this request.</p> <!--
     http-origin privacy sensitive, though it doesn't matter, since
     this can never be cross-origin -->
 
+    <p class="note">Since caching can be honored, authors are
+    encouraged to avoid setting the cache headers on the manifest in
+    such a way that the user agent would simply not contact the
+    network for this second request; otherwise, the user agent would
+    not notice if the cache had changed during the cache update
+    process.</p>
+
    </li>
 
    <li>