Skip to content
Permalink
Browse files

[gwr] (2) Appcache: Check the manifest again after updating the cache…

… to make sure it hasn't changed.

git-svn-id: http://svn.whatwg.org/webapps@2350 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
Hixie committed Oct 17, 2008
1 parent a1ca34b commit 1007b2aa694c5cbe251f335fedb9696e921b66f5
Showing with 59 additions and 13 deletions.
  1. +28 −6 index
  2. +31 −7 source
34 index
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>


</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>

38 source
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>


</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>

0 comments on commit 1007b2a

Please sign in to comment.
You can’t perform that action at this time.