[html5] r2350 - [gwr] (2) Appcache: Check the manifest again after updating the cache to make su [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2008-10-17 16:12:21 -0700 (Fri, 17 Oct 2008)
New Revision: 2350

Modified:
   index
   source
Log:
[gwr] (2) Appcache: Check the manifest again after updating the cache to make sure it hasn't changed.

Modified: index
===================================================================
--- index	2008-10-17 22:40:30 UTC (rev 2349)
+++ index	2008-10-17 23:12:21 UTC (rev 2350)
@@ -34448,9 +34448,9 @@
     returns another 4xx or 5xx response or equivalent, or there is a
     DNS error, or the connection times out, or the user cancels the
     download, or the parser for manifests fails when checking the
-    magic signature), or if the resource is labeled with a MIME type
-    other than <code title="">text/cache-manifest</code>, then run the
-    <a href=#cache-failure-steps>cache failure steps</a>.</p>
+    magic signature), or if the server returned a redirect, or if the
+    resource is labeled with a MIME type other than <code title="">text/cache-manifest</code>, then run the <a href=#cache-failure-steps>cache
+    failure steps</a>.</p>
 
    </li>
 
@@ -34675,12 +34675,34 @@
 
    </li>
 
-   <li><p>Store <var title="">manifest</var> in <var title="">new
-   cache</var>, if it's not there already, and categorize this entry
-   (whether newly added or not) as <a href=#concept-appcache-manifest title=concept-appcache-manifest>the manifest</a>.</li>
+   <li>
 
+    <p><a href=#fetch>Fetch</a> the resource from <var title="">manifest
+    URL</var> again, and let <var title="">second manifest</var> be
+    that resource.</p>
+
+   </li>
+
    <li>
 
+    <p>If the previous step failed for any reason, or if the fetching
+    attempt involved a redirect, or if <var title="">second
+    manifest</var> and <var title="">manifest</var> are not
+    byte-for-byte identical, then schedule a rerun of the entire
+    algorithm with the same parameters after a short delay, and run
+    the <a href=#cache-failure-steps>cache failure steps</a>.</p>
+
+   </li>
+
+   <li>
+
+    <p>Otherwise, store <var title="">manifest</var> in <var title="">new cache</var>, if it's not there already, and
+    categorize this entry (whether newly added or not) as <a href=#concept-appcache-manifest title=concept-appcache-manifest>the manifest</a>.</p>
+
+   </li>
+
+   <li>
+
     <p>If this is a <a href=#concept-appcache-cache title=concept-appcache-cache>cache
     attempt</a>, then:</p>
 

Modified: source
===================================================================
--- source	2008-10-17 22:40:30 UTC (rev 2349)
+++ source	2008-10-17 23:12:21 UTC (rev 2350)
@@ -39116,9 +39116,10 @@
     returns another 4xx or 5xx response or equivalent, or there is a
     DNS error, or the connection times out, or the user cancels the
     download, or the parser for manifests fails when checking the
-    magic signature), or if the resource is labeled with a MIME type
-    other than <code title="">text/cache-manifest</code>, then run the
-    <span>cache failure steps</span>.</p>
+    magic signature), or if the server returned a redirect, or if the
+    resource is labeled with a MIME type other than <code
+    title="">text/cache-manifest</code>, then run the <span>cache
+    failure steps</span>.</p>
 
    </li>
 
@@ -39376,13 +39377,36 @@
 
    </li>
 
-   <li><p>Store <var title="">manifest</var> in <var title="">new
-   cache</var>, if it's not there already, and categorize this entry
-   (whether newly added or not) as <span
-   title="concept-appcache-manifest">the manifest</span>.</p></li>
+   <li>
 
+    <p><span>Fetch</span> the resource from <var title="">manifest
+    URL</var> again, and let <var title="">second manifest</var> be
+    that resource.</p>
+
+   </li>
+
    <li>
 
+    <p>If the previous step failed for any reason, or if the fetching
+    attempt involved a redirect, or if <var title="">second
+    manifest</var> and <var title="">manifest</var> are not
+    byte-for-byte identical, then schedule a rerun of the entire
+    algorithm with the same parameters after a short delay, and run
+    the <span>cache failure steps</span>.</p>
+
+   </li>
+
+   <li>
+
+    <p>Otherwise, store <var title="">manifest</var> in <var
+    title="">new cache</var>, if it's not there already, and
+    categorize this entry (whether newly added or not) as <span
+    title="concept-appcache-manifest">the manifest</span>.</p>
+
+   </li>
+
+   <li>
+
     <p>If this is a <span title="concept-appcache-cache">cache
     attempt</span>, then:</p>