[html5] r5492 - [e] (0) Add an example of absolute URLs in appcaches. Fixing http://www.w3.org/B [...]
whatwg at whatwg.org
whatwg at whatwg.org
Sat Sep 25 11:12:20 PDT 2010
Author: ianh
Date: 2010-09-25 11:12:19 -0700 (Sat, 25 Sep 2010)
New Revision: 5492
Modified:
complete.html
index
source
Log:
[e] (0) Add an example of absolute URLs in appcaches.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=10499
Modified: complete.html
===================================================================
--- complete.html 2010-09-25 18:05:31 UTC (rev 5491)
+++ complete.html 2010-09-25 18:12:19 UTC (rev 5492)
@@ -880,7 +880,7 @@
<li><a href=#appcache><span class=secno>6.6.2 </span>Application caches</a></li>
<li><a href=#manifests><span class=secno>6.6.3 </span>The cache manifest syntax</a>
<ol>
- <li><a href=#a-sample-manifest><span class=secno>6.6.3.1 </span>A sample manifest</a></li>
+ <li><a href=#some-sample-manifests><span class=secno>6.6.3.1 </span>Some sample manifests</a></li>
<li><a href=#writing-cache-manifests><span class=secno>6.6.3.2 </span>Writing cache manifests</a></li>
<li><a href=#parsing-cache-manifests><span class=secno>6.6.3.3 </span>Parsing cache manifests</a></ol></li>
<li><a href=#downloading-or-updating-an-application-cache><span class=secno>6.6.4 </span>Downloading or updating an application cache</a></li>
@@ -62339,14 +62339,16 @@
<h4 id=manifests><span class=secno>6.6.3 </span>The cache manifest syntax</h4>
- <h5 id=a-sample-manifest><span class=secno>6.6.3.1 </span>A sample manifest</h5>
+ <h5 id=some-sample-manifests><span class=secno>6.6.3.1 </span>Some sample manifests</h5>
<p><i>This section is non-normative.</i></p>
- <p>This example manifest requires two images and a style sheet to be
- cached and whitelists a CGI script.</p>
+ <div class=example>
- <pre>CACHE MANIFEST
+ <p>This example manifest requires two images and a style sheet to be
+ cached and whitelists a CGI script.</p>
+
+ <pre>CACHE MANIFEST
# the above line is required
# this is a comment
@@ -62374,9 +62376,9 @@
CACHE:
style/default.css</pre>
- <p>It could equally well be written as follows:</p>
+ <p>It could equally well be written as follows:</p>
- <pre>CACHE MANIFEST
+ <pre>CACHE MANIFEST
NETWORK:
comm.cgi
CACHE:
@@ -62384,31 +62386,55 @@
images/sound-icon.png
images/background.png</pre>
- <hr><p>The following manifest defines a catch-all error page that is
- displayed for any page on the site while the user is offline. It
- also specifies that the <a href=#concept-appcache-onlinewhitelist-wildcard title=concept-appcache-onlinewhitelist-wildcard>online whitelist
- wildcard flag</a> is <i title="">open</i>, meaning that accesses
- to resources on other sites will not be blocked. (Resources on the
- same site are already not blocked because of the catch-all fallback
- namespace.)</p>
+ </div>
- <p>So long as all pages on the site reference this manifest, they
- will get cached locally as they are fetched, so that subsequent hits
- to the same page will load the page immediately from the
- cache. Until the manifest is changed, those pages will not be
- fetched from the server again. When the manifest changes, then all
- the files will be redownloaded.</p>
+ <div class=example>
- <p>Subresources, such as style sheets, images, etc, would only be
- cached using the regular HTTP caching semantics, however.</p>
+ <p>Offline application cache manifests can use absolute paths or
+ even absolute URLs:</p>
- <pre>CACHE MANIFEST
+ <pre>CACHE MANIFEST
+
+/main/home
+/main/app.js
+/settings/home
+/settings/app.js
+http://img.example.com/logo.png
+http://img.example.com/check.png
+http://img.example.com/cross.png</pre>
+
+ </div>
+
+ <div class=example>
+
+ <p>The following manifest defines a catch-all error page that is
+ displayed for any page on the site while the user is offline. It
+ also specifies that the <a href=#concept-appcache-onlinewhitelist-wildcard title=concept-appcache-onlinewhitelist-wildcard>online whitelist
+ wildcard flag</a> is <i title="">open</i>, meaning that accesses
+ to resources on other sites will not be blocked. (Resources on the
+ same site are already not blocked because of the catch-all fallback
+ namespace.)</p>
+
+ <p>So long as all pages on the site reference this manifest, they
+ will get cached locally as they are fetched, so that subsequent hits
+ to the same page will load the page immediately from the
+ cache. Until the manifest is changed, those pages will not be
+ fetched from the server again. When the manifest changes, then all
+ the files will be redownloaded.</p>
+
+ <p>Subresources, such as style sheets, images, etc, would only be
+ cached using the regular HTTP caching semantics, however.</p>
+
+ <pre>CACHE MANIFEST
FALLBACK:
/ /offline.html
NETWORK:
*</pre>
+ </div>
+
+
<h5 id=writing-cache-manifests><span class=secno>6.6.3.2 </span>Writing cache manifests</h5>
<p>Manifests must be served using the
Modified: index
===================================================================
--- index 2010-09-25 18:05:31 UTC (rev 5491)
+++ index 2010-09-25 18:12:19 UTC (rev 5492)
@@ -887,7 +887,7 @@
<li><a href=#appcache><span class=secno>6.6.2 </span>Application caches</a></li>
<li><a href=#manifests><span class=secno>6.6.3 </span>The cache manifest syntax</a>
<ol>
- <li><a href=#a-sample-manifest><span class=secno>6.6.3.1 </span>A sample manifest</a></li>
+ <li><a href=#some-sample-manifests><span class=secno>6.6.3.1 </span>Some sample manifests</a></li>
<li><a href=#writing-cache-manifests><span class=secno>6.6.3.2 </span>Writing cache manifests</a></li>
<li><a href=#parsing-cache-manifests><span class=secno>6.6.3.3 </span>Parsing cache manifests</a></ol></li>
<li><a href=#downloading-or-updating-an-application-cache><span class=secno>6.6.4 </span>Downloading or updating an application cache</a></li>
@@ -62328,14 +62328,16 @@
<h4 id=manifests><span class=secno>6.6.3 </span>The cache manifest syntax</h4>
- <h5 id=a-sample-manifest><span class=secno>6.6.3.1 </span>A sample manifest</h5>
+ <h5 id=some-sample-manifests><span class=secno>6.6.3.1 </span>Some sample manifests</h5>
<p><i>This section is non-normative.</i></p>
- <p>This example manifest requires two images and a style sheet to be
- cached and whitelists a CGI script.</p>
+ <div class=example>
- <pre>CACHE MANIFEST
+ <p>This example manifest requires two images and a style sheet to be
+ cached and whitelists a CGI script.</p>
+
+ <pre>CACHE MANIFEST
# the above line is required
# this is a comment
@@ -62363,9 +62365,9 @@
CACHE:
style/default.css</pre>
- <p>It could equally well be written as follows:</p>
+ <p>It could equally well be written as follows:</p>
- <pre>CACHE MANIFEST
+ <pre>CACHE MANIFEST
NETWORK:
comm.cgi
CACHE:
@@ -62373,31 +62375,55 @@
images/sound-icon.png
images/background.png</pre>
- <hr><p>The following manifest defines a catch-all error page that is
- displayed for any page on the site while the user is offline. It
- also specifies that the <a href=#concept-appcache-onlinewhitelist-wildcard title=concept-appcache-onlinewhitelist-wildcard>online whitelist
- wildcard flag</a> is <i title="">open</i>, meaning that accesses
- to resources on other sites will not be blocked. (Resources on the
- same site are already not blocked because of the catch-all fallback
- namespace.)</p>
+ </div>
- <p>So long as all pages on the site reference this manifest, they
- will get cached locally as they are fetched, so that subsequent hits
- to the same page will load the page immediately from the
- cache. Until the manifest is changed, those pages will not be
- fetched from the server again. When the manifest changes, then all
- the files will be redownloaded.</p>
+ <div class=example>
- <p>Subresources, such as style sheets, images, etc, would only be
- cached using the regular HTTP caching semantics, however.</p>
+ <p>Offline application cache manifests can use absolute paths or
+ even absolute URLs:</p>
- <pre>CACHE MANIFEST
+ <pre>CACHE MANIFEST
+
+/main/home
+/main/app.js
+/settings/home
+/settings/app.js
+http://img.example.com/logo.png
+http://img.example.com/check.png
+http://img.example.com/cross.png</pre>
+
+ </div>
+
+ <div class=example>
+
+ <p>The following manifest defines a catch-all error page that is
+ displayed for any page on the site while the user is offline. It
+ also specifies that the <a href=#concept-appcache-onlinewhitelist-wildcard title=concept-appcache-onlinewhitelist-wildcard>online whitelist
+ wildcard flag</a> is <i title="">open</i>, meaning that accesses
+ to resources on other sites will not be blocked. (Resources on the
+ same site are already not blocked because of the catch-all fallback
+ namespace.)</p>
+
+ <p>So long as all pages on the site reference this manifest, they
+ will get cached locally as they are fetched, so that subsequent hits
+ to the same page will load the page immediately from the
+ cache. Until the manifest is changed, those pages will not be
+ fetched from the server again. When the manifest changes, then all
+ the files will be redownloaded.</p>
+
+ <p>Subresources, such as style sheets, images, etc, would only be
+ cached using the regular HTTP caching semantics, however.</p>
+
+ <pre>CACHE MANIFEST
FALLBACK:
/ /offline.html
NETWORK:
*</pre>
+ </div>
+
+
<h5 id=writing-cache-manifests><span class=secno>6.6.3.2 </span>Writing cache manifests</h5>
<p>Manifests must be served using the
Modified: source
===================================================================
--- source 2010-09-25 18:05:31 UTC (rev 5491)
+++ source 2010-09-25 18:12:19 UTC (rev 5492)
@@ -70499,14 +70499,16 @@
<h4 id="manifests">The cache manifest syntax</h4>
- <h5>A sample manifest</h5>
+ <h5>Some sample manifests</h5>
<p><i>This section is non-normative.</i></p>
- <p>This example manifest requires two images and a style sheet to be
- cached and whitelists a CGI script.</p>
+ <div class="example">
- <pre>CACHE MANIFEST
+ <p>This example manifest requires two images and a style sheet to be
+ cached and whitelists a CGI script.</p>
+
+ <pre>CACHE MANIFEST
# the above line is required
# this is a comment
@@ -70534,9 +70536,9 @@
CACHE:
style/default.css</pre>
- <p>It could equally well be written as follows:</p>
+ <p>It could equally well be written as follows:</p>
- <pre>CACHE MANIFEST
+ <pre>CACHE MANIFEST
NETWORK:
comm.cgi
CACHE:
@@ -70544,34 +70546,56 @@
images/sound-icon.png
images/background.png</pre>
- <hr>
+ </div>
- <p>The following manifest defines a catch-all error page that is
- displayed for any page on the site while the user is offline. It
- also specifies that the <span
- title="concept-appcache-onlinewhitelist-wildcard">online whitelist
- wildcard flag</span> is <i title="">open</i>, meaning that accesses
- to resources on other sites will not be blocked. (Resources on the
- same site are already not blocked because of the catch-all fallback
- namespace.)</p>
+ <div class="example">
- <p>So long as all pages on the site reference this manifest, they
- will get cached locally as they are fetched, so that subsequent hits
- to the same page will load the page immediately from the
- cache. Until the manifest is changed, those pages will not be
- fetched from the server again. When the manifest changes, then all
- the files will be redownloaded.</p>
+ <p>Offline application cache manifests can use absolute paths or
+ even absolute URLs:</p>
- <p>Subresources, such as style sheets, images, etc, would only be
- cached using the regular HTTP caching semantics, however.</p>
+ <pre>CACHE MANIFEST
- <pre>CACHE MANIFEST
+/main/home
+/main/app.js
+/settings/home
+/settings/app.js
+http://img.example.com/logo.png
+http://img.example.com/check.png
+http://img.example.com/cross.png</pre>
+
+ </div>
+
+ <div class="example">
+
+ <p>The following manifest defines a catch-all error page that is
+ displayed for any page on the site while the user is offline. It
+ also specifies that the <span
+ title="concept-appcache-onlinewhitelist-wildcard">online whitelist
+ wildcard flag</span> is <i title="">open</i>, meaning that accesses
+ to resources on other sites will not be blocked. (Resources on the
+ same site are already not blocked because of the catch-all fallback
+ namespace.)</p>
+
+ <p>So long as all pages on the site reference this manifest, they
+ will get cached locally as they are fetched, so that subsequent hits
+ to the same page will load the page immediately from the
+ cache. Until the manifest is changed, those pages will not be
+ fetched from the server again. When the manifest changes, then all
+ the files will be redownloaded.</p>
+
+ <p>Subresources, such as style sheets, images, etc, would only be
+ cached using the regular HTTP caching semantics, however.</p>
+
+ <pre>CACHE MANIFEST
FALLBACK:
/ /offline.html
NETWORK:
*</pre>
+ </div>
+
+
<h5>Writing cache manifests</h5>
<p>Manifests must be served using the
More information about the Commit-Watchers
mailing list