HTML Standard Tracker

Filter

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
@@ -38649,22 +38649,23 @@ style/default.css</pre>
   empty.</p>
 
   <p>URLs that are to be fallback pages associated with <span
   title="concept-appcache-fallback-ns">fallback namespaces</span>, and
   those namespaces themselves, must be given in fallback sections,
   with the namespace being the first URL of the data line, and the
   corresponding fallback page being the second URL. All the other
   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>
 
   <p>URLs that the user agent is to put into the <span
   title="concept-appcache-onlinewhitelist">online whitelist</span>
   must all be specified in online whitelist sections. (This is needed
   for any URL that the page is intending to use to communicate back to
   the server.)</p>
 
@@ -39336,41 +39337,42 @@ style/default.css</pre>
   Web applications is part of the <span
   title="navigate">navigation</span> model, but references the
   algorithms defined in this section.</p>
 
   <p>A URL <dfn title="concept-appcache-matches-fallback">matches a
   fallback namespace</dfn> if there exists an <span>application
   cache</span> whose <span
   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">
 
    <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
+   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
   title="concept-appcache-init-with-attribute">application cache
   selection algorithm</dfn> algorithm is invoked with a manifest URL,
   the user agent must run the first applicable set of steps from the
   following list:</p>
 
   <dl class="switch">
 
@@ -39530,23 +39532,22 @@ style/default.css</pre>
    title="concept-appcache-fallback">a fallback entry</span>, or a
    <span title="concept-appcache-dynamic">dynamic entry</span> in the
    <span>application cache</span>, then get the resource from the
    cache (instead of fetching it), and abort these steps.</p></li>
 
    <li>
 
     <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>
     (indicative of a captive portal), or a 4xx or 5xx status code or
     equivalent, or if there were network errors (but not if the user
     canceled the download), then instead get, from the cache, the
     resource of the <span title="concept-appcache-fallback">fallback
     entry</span> corresponding to the namespace with the longest
     matching <span title="url-path">&lt;path&gt;</span>
     component. Abort these steps.</p>

|