HTML Standard Tracker

Diff (omit for latest revision)
Filter

Short URL: http://html5.org/r/2343

File a bug

SVNBugCommentTime (UTC)
2343[Gecko] [Webkit] [Google Gears] Make fallback namespaces use the whole URL instead of just the path.2008-10-16 01:04
Index: source
===================================================================
--- source	(revision 2342)
+++ source	(revision 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">&lt;path&gt;</span> component that is a
-  <span>prefix match</span> for the <span
-  title="url-path">&lt;path&gt;</span> component of the URL being
-  examined. If multiple fallback namespaces match the same URL, the
-  one with the longest <span title="url-path">&lt;path&gt;</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 &lt;path&gt; component is
-    a <span>prefix match</span> for the resource's URL's <span
-    title="url-path">&lt;path&gt;</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>

|