Skip to content
Permalink
Browse files

[gwr] (2) Make fallback namespaces use the whole URL instead of just …

…the path.

git-svn-id: http://svn.whatwg.org/webapps@2343 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
Hixie committed Oct 16, 2008
1 parent c17e465 commit acfdd0a582896b3f571d10ccdbb33a228d4ab8a1
Showing with 34 additions and 32 deletions.
  1. +16 −15 index
  2. +18 −17 source
31 index
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>
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>&lt;path&gt;</a> component that is a
<a href=#prefix-match>prefix match</a> for the <a href=#url-path title=url-path>&lt;path&gt;</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>&lt;path&gt;</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

<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 &lt;path&gt; component is
a <a href=#prefix-match>prefix match</a> for the resource's URL's <a href=#url-path title=url-path>&lt;path&gt;</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>
35 source
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>
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
<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>

0 comments on commit acfdd0a

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