- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 25 Oct 2011 03:22:47 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv12789 Modified Files: Overview.html Log Message: Talk more about HTTP caching semantics in the context of appcache. (whatwg r6749) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.5409 retrieving revision 1.5410 diff -u -d -r1.5409 -r1.5410 --- Overview.html 25 Oct 2011 03:13:49 -0000 1.5409 +++ Overview.html 25 Oct 2011 03:22:43 -0000 1.5410 @@ -48559,7 +48559,8 @@ <p><i>Fetching the manifest</i>: <a href="#fetch">Fetch</a> the resource from <var title="">manifest URL</var> with the <i>synchronous flag</i> set, and let <var title="">manifest</var> be that - resource.</p> + resource. HTTP caching semantics should be honored for this + request.</p> <p>If the resource is labeled with the <a href="#mime-type">MIME type</a> <code><a href="#text-cache-manifest">text/cache-manifest</a></code>, either with no parameters or with a single parameter with the name "<code title="">charset</code>" whose value is an <a href="#ascii-case-insensitive">ASCII @@ -48888,8 +48889,9 @@ server-side errors.</p> <p class="note">Except for the "no-store" directive, HTTP - caching rules are ignored for the purposes of the - <a href="#application-cache-download-process">application cache download process</a>.</p> + caching rules that would cause a file to be expired or otherwise + not cached are ignored for the purposes of the <a href="#application-cache-download-process">application + cache download process</a>.</p> </li> @@ -49011,7 +49013,15 @@ <p><a href="#fetch">Fetch</a> the resource from <var title="">manifest URL</var> again, with the <i>synchronous flag</i> set, and let - <var title="">second manifest</var> be that resource.</p> + <var title="">second manifest</var> be that resource. HTTP caching + semantics should again be honored for this request.</p> + <p class="note">Since caching can be honored, authors are + encouraged to avoid setting the cache headers on the manifest in + such a way that the user agent would simply not contact the + network for this second request; otherwise, the user agent would + not notice if the cache had changed during the cache update + process.</p> + </li> <li>
Received on Tuesday, 25 October 2011 03:23:06 UTC