html5/spec Overview.html,1.1522,1.1523

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv15971

Modified Files:
	Overview.html 
Log Message:
Appcache: Check the manifest again after updating the cache to make sure it hasn't changed. (whatwg r2350)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1522
retrieving revision 1.1523
diff -u -d -r1.1522 -r1.1523
--- Overview.html	17 Oct 2008 22:40:35 -0000	1.1522
+++ Overview.html	17 Oct 2008 23:12:25 -0000	1.1523
@@ -27871,9 +27871,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>
 
@@ -28098,9 +28098,31 @@
 
    </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>

Received on Friday, 17 October 2008 23:12:39 UTC