[html5] r2348 - [gwr] (2) Appcache: Handle errors for dynamic and master entries differently, si [...]

whatwg at whatwg.org whatwg at whatwg.org
Fri Oct 17 15:38:19 PDT 2008


Author: ianh
Date: 2008-10-17 15:38:18 -0700 (Fri, 17 Oct 2008)
New Revision: 2348

Modified:
   index
   source
Log:
[gwr] (2) Appcache: Handle errors for dynamic and master entries differently, since they aren't representative of manifest errors.

Modified: index
===================================================================
--- index	2008-10-16 10:53:23 UTC (rev 2347)
+++ index	2008-10-17 22:38:18 UTC (rev 2348)
@@ -16,7 +16,7 @@
   <div class=head>
    <p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
    <h1>HTML 5</h1>
-   <h2 class="no-num no-toc" id=draft-recommendation-—-date:-01-jan-1901>Draft Recommendation — 16 October 2008</h2>
+   <h2 class="no-num no-toc" id=draft-recommendation-—-date:-01-jan-1901>Draft Recommendation — 17 October 2008</h2>
    <p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
    <p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
    <dl><dt>Multiple-page version:</dt>
@@ -34567,20 +34567,56 @@
 
      <li>
 
-      <p>If the previous steps fails (e.g. the server returns a 4xx or
+      <p>If the previous step fails (e.g. the server returns a 4xx or
       5xx response or equivalent, or there is a DNS error, or the
       connection times out, or the user cancels the download), or if
-      the server returned a redirect, then run the <a href=#cache-failure-steps>cache failure
-      steps</a>.</p>
+      the server returned a redirect, then run the first appropriate
+      step from the following list:</p>
 
-      <p class=note>Redirects are fatal because they are either
-      indicative of a network problem (e.g. a captive portal); or
-      would allow resources to be added to the cache under URLs that
-      differ from any URL that the networking model will allow access
-      to, leaving orphan entries; or would allow resources to be
-      stored under URLs different than their true URLs. All of these
-      situations are bad.</p>
+      <dl class=switch><dt>If the URL being processed was flagged as an "explicit
+       entry" or a "fallback entry"</dt>
 
+       <dd>
+
+        <p>Run the <a href=#cache-failure-steps>cache failure steps</a>.</p>
+
+        <p class=note>Redirects are fatal because they are either
+        indicative of a network problem (e.g. a captive portal); or
+        would allow resources to be added to the cache under URLs that
+        differ from any URL that the networking model will allow
+        access to, leaving orphan entries; or would allow resources to
+        be stored under URLs different than their true URLs. All of
+        these situations are bad.</p>
+
+       </dd>
+
+       <dt>If the error was a 404 or 410 HTTP response or
+       equivalent</dt>
+
+       <dd>
+
+        <p>Skip this resource. It is dropped from the cache.</p>
+
+       </dd>
+
+       <dt>Otherwise</dt>
+
+       <dd>
+
+        <p>Copy the resource and its metadata from <var title="">cache</var>, and ignore the resource obtained from
+        the network.</p>
+
+       </dd>
+
+      </dl><p>User agents may warn the user of these errors as an aid to
+      development.</p>
+
+      <p class=note>These rules make errors for resources listed in
+      the manifest fatal, while making it possible for other resources
+      to be removed from caches when they are removed from the server,
+      without errors, and making non-manifest resources survive
+      server-side errors.
+
      </li>
 
      <li><p>Otherwise, the fetching succeeded. Store the resource in

Modified: source
===================================================================
--- source	2008-10-16 10:53:23 UTC (rev 2347)
+++ source	2008-10-17 22:38:18 UTC (rev 2348)
@@ -39256,20 +39256,61 @@
 
      <li>
 
-      <p>If the previous steps fails (e.g. the server returns a 4xx or
+      <p>If the previous step fails (e.g. the server returns a 4xx or
       5xx response or equivalent, or there is a DNS error, or the
       connection times out, or the user cancels the download), or if
-      the server returned a redirect, then run the <span>cache failure
-      steps</span>.</p>
+      the server returned a redirect, then run the first appropriate
+      step from the following list:</p>
 
-      <p class="note">Redirects are fatal because they are either
-      indicative of a network problem (e.g. a captive portal); or
-      would allow resources to be added to the cache under URLs that
-      differ from any URL that the networking model will allow access
-      to, leaving orphan entries; or would allow resources to be
-      stored under URLs different than their true URLs. All of these
-      situations are bad.</p>
+      <dl class="switch">
 
+       <dt>If the URL being processed was flagged as an "explicit
+       entry" or a "fallback entry"</dt>
+
+       <dd>
+
+        <p>Run the <span>cache failure steps</span>.</p>
+
+        <p class="note">Redirects are fatal because they are either
+        indicative of a network problem (e.g. a captive portal); or
+        would allow resources to be added to the cache under URLs that
+        differ from any URL that the networking model will allow
+        access to, leaving orphan entries; or would allow resources to
+        be stored under URLs different than their true URLs. All of
+        these situations are bad.</p>
+
+       </dd>
+
+       <dt>If the error was a 404 or 410 HTTP response or
+       equivalent</dt>
+
+       <dd>
+
+        <p>Skip this resource. It is dropped from the cache.</p>
+
+       </dd>
+
+       <dt>Otherwise</dt>
+
+       <dd>
+
+        <p>Copy the resource and its metadata from <var
+        title="">cache</var>, and ignore the resource obtained from
+        the network.</p>
+
+       </dd>
+
+      </dl>
+
+      <p>User agents may warn the user of these errors as an aid to
+      development.</p>
+
+      <p class="note">These rules make errors for resources listed in
+      the manifest fatal, while making it possible for other resources
+      to be removed from caches when they are removed from the server,
+      without errors, and making non-manifest resources survive
+      server-side errors.
+
      </li>
 
      <li><p>Otherwise, the fetching succeeded. Store the resource in




More information about the Commit-Watchers mailing list