[html5] r2343 - [gwr] (2) Make fallback namespaces use the whole URL instead of just the path.

whatwg at whatwg.org whatwg at whatwg.org
Wed Oct 15 18:04:34 PDT 2008


Author: ianh
Date: 2008-10-15 18:04:33 -0700 (Wed, 15 Oct 2008)
New Revision: 2343

Modified:
   index
   source
Log:
[gwr] (2) Make fallback namespaces use the whole URL instead of just the path.

Modified: index
===================================================================
--- index	2008-10-16 00:54:29 UTC (rev 2342)
+++ index	2008-10-16 01:04:33 UTC (rev 2343)
@@ -34062,8 +34062,8 @@
   pages to be cached must be listed in explicit sections.</p>
 
   <p><a href=#concept-appcache-fallback-ns title=concept-appcache-fallback-ns>Fallback
-  namespaces</a> must have the <a href=#same-origin>same origin</a> as the
-  manifest itself.</p>
+  namespaces</a> and <a href=#concept-appcache-fallback title=concept-appcache-fallback>fallback entries</a> must have
+  the <a href=#same-origin>same origin</a> as the manifest itself.</p>
 
   <p>A <a href=#concept-appcache-fallback-ns title=concept-appcache-fallback-ns>fallback
   namespace</a> must not be listed more than once.</p>
@@ -34641,24 +34641,25 @@
   fallback namespace</dfn> if there exists an <a href=#application-cache>application
   cache</a> whose <a href=#concept-appcache-manifest title=concept-appcache-manifest>manifest</a>'s URL has the
   <a href=#same-origin>same origin</a> as the URL in question, and if that
-  application cache has a <a href=#concept-appcache-fallback-ns title=concept-appcache-fallback-ns>fallback namespace</a> with
-  a <a href=#url-path title=url-path><path></a> component that is a
-  <a href=#prefix-match>prefix match</a> for the <a href=#url-path title=url-path><path></a> component of the URL being
-  examined. If multiple fallback namespaces match the same URL, the
-  one with the longest <a href=#url-path title=url-path><path></a> component is the one
-  that matches. A URL looking for an fallback namespace can match more
-  than one application cache at a time, but only matches one namespace
-  in each cache.</p>
+  application cache has a <a href=#concept-appcache-fallback-ns title=concept-appcache-fallback-ns>fallback namespace</a> that
+  is a <a href=#prefix-match>prefix match</a> for the URL being examined. If
+  multiple fallback namespaces match the same URL, the longest one is
+  the one that matches. A URL looking for an fallback namespace can
+  match more than one application cache at a time, but only matches
+  one namespace in each cache.</p>
 
   <div class=example>
 
    <p>If a manifest <code title="">http://example.com/app1/manifest</code> declares that
    <code title="">http://example.com/resources/images</code> is a
-   fallback namespace, and the user navigates to <code title="">http://example.com/resources/images/cat.png</code>, then
-   the user agent will decide that the application cache identified by
-   <code title="">http://example.com/app1/manifest</code> contains a
+   fallback namespace, and the user navigates to <code title="">HTTP://EXAMPLE.COM:80/resources/images/cat.png</code>,
+   then the user agent will decide that the application cache
+   identified by <code title="">http://example.com/app1/manifest</code> contains a
    namespace with a match for that URL.</p>
 
+   <!-- "resolve a url" canonicalises the case for the scheme and host
+   and removes the port if it is the default -->
+
   </div>
 
   <p>When the <dfn id=concept-appcache-init-with-attribute title=concept-appcache-init-with-attribute>application cache
@@ -34806,8 +34807,8 @@
 
     <p>If the resource's URL has the <a href=#same-origin>same origin</a> as the
     manifest's URL, and there is a <a href=#concept-appcache-fallback-ns title=concept-appcache-fallback-ns>fallback namespace</a> in
-    the <a href=#application-cache>application cache</a> whose <path> component is
-    a <a href=#prefix-match>prefix match</a> for the resource's URL's <a href=#url-path title=url-path><path></a> component, then:</p>
+    the <a href=#application-cache>application cache</a> that is a <a href=#prefix-match>prefix
+    match</a> for the resource's URL, then:</p>
 
     <p><a href=#fetch>Fetch</a> the resource normally. If this results in a
     redirect to a resource with another <a href=#origin-0>origin</a>

Modified: source
===================================================================
--- source	2008-10-16 00:54:29 UTC (rev 2342)
+++ source	2008-10-16 01:04:33 UTC (rev 2343)
@@ -38656,8 +38656,9 @@
   pages to be cached must be listed in explicit sections.</p>
 
   <p><span title="concept-appcache-fallback-ns">Fallback
-  namespaces</span> must have the <span>same origin</span> as the
-  manifest itself.</p>
+  namespaces</span> and <span
+  title="concept-appcache-fallback">fallback entries</span> must have
+  the <span>same origin</span> as the manifest itself.</p>
 
   <p>A <span title="concept-appcache-fallback-ns">fallback
   namespace</span> must not be listed more than once.</p>
@@ -39343,15 +39344,12 @@
   title="concept-appcache-manifest">manifest</span>'s URL has the
   <span>same origin</span> as the URL in question, and if that
   application cache has a <span
-  title="concept-appcache-fallback-ns">fallback namespace</span> with
-  a <span title="url-path"><path></span> component that is a
-  <span>prefix match</span> for the <span
-  title="url-path"><path></span> component of the URL being
-  examined. If multiple fallback namespaces match the same URL, the
-  one with the longest <span title="url-path"><path></span> component is the one
-  that matches. A URL looking for an fallback namespace can match more
-  than one application cache at a time, but only matches one namespace
-  in each cache.</p>
+  title="concept-appcache-fallback-ns">fallback namespace</span> that
+  is a <span>prefix match</span> for the URL being examined. If
+  multiple fallback namespaces match the same URL, the longest one is
+  the one that matches. A URL looking for an fallback namespace can
+  match more than one application cache at a time, but only matches
+  one namespace in each cache.</p>
 
   <div class="example">
 
@@ -39359,11 +39357,15 @@
    title="">http://example.com/app1/manifest</code> declares that
    <code title="">http://example.com/resources/images</code> is a
    fallback namespace, and the user navigates to <code
-   title="">http://example.com/resources/images/cat.png</code>, then
-   the user agent will decide that the application cache identified by
-   <code title="">http://example.com/app1/manifest</code> contains a
+   title="">HTTP://EXAMPLE.COM:80/resources/images/cat.png</code>,
+   then the user agent will decide that the application cache
+   identified by <code
+   title="">http://example.com/app1/manifest</code> contains a
    namespace with a match for that URL.</p>
 
+   <!-- "resolve a url" canonicalises the case for the scheme and host
+   and removes the port if it is the default -->
+
   </div>
 
   <p>When the <dfn
@@ -39537,9 +39539,8 @@
     <p>If the resource's URL has the <span>same origin</span> as the
     manifest's URL, and there is a <span
     title="concept-appcache-fallback-ns">fallback namespace</span> in
-    the <span>application cache</span> whose <path> component is
-    a <span>prefix match</span> for the resource's URL's <span
-    title="url-path"><path></span> component, then:</p>
+    the <span>application cache</span> that is a <span>prefix
+    match</span> for the resource's URL, then:</p>
 
     <p><span>Fetch</span> the resource normally. If this results in a
     redirect to a resource with another <span>origin</span>




More information about the Commit-Watchers mailing list