[html5] r8791 - [giow] (3) Make appcache requests have no referrer, since it's not clear what re [...]
whatwg at whatwg.org
whatwg at whatwg.org
Fri Sep 19 10:52:21 PDT 2014
Author: ianh
Date: 2014-09-19 10:52:16 -0700 (Fri, 19 Sep 2014)
New Revision: 8791
Modified:
complete.html
index
source
Log:
[giow] (3) Make appcache requests have no referrer, since it's not clear what referrer to use.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=17687
Affected topics: HTML, Offline Web Applications
Modified: complete.html
===================================================================
--- complete.html 2014-09-19 17:39:29 UTC (rev 8790)
+++ complete.html 2014-09-19 17:52:16 UTC (rev 8791)
@@ -4473,7 +4473,7 @@
<p>Let <var>document</var> be the appropriate <code id=processing-model:document><a href=#document>Document</a></code> as given by the
following list:</p>
- <dl class=switch><dt>If there is a specific <i>override referrer source</i><dd>The <i>override referrer source</i>.<dt>When <a href=#navigate id=processing-model:navigate>navigating</a><dd>The <a href=#active-document id=processing-model:active-document>active document</a> of the <a href=#source-browsing-context id=processing-model:source-browsing-context>source browsing context</a>.<dt>When fetching resources for an element<dd>The element's <a id=processing-model:node-document href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a>.</dl>
+ <dl class=switch><dt>If there is a specific <i>override referrer source</i> (which might be null)<dd>The <i>override referrer source</i>.<dt>When <a href=#navigate id=processing-model:navigate>navigating</a><dd>The <a href=#active-document id=processing-model:active-document>active document</a> of the <a href=#source-browsing-context id=processing-model:source-browsing-context>source browsing context</a>.<dt>When fetching resources for an element<dd>The element's <a id=processing-model:node-document href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a>.</dl>
<li>
@@ -4483,8 +4483,8 @@
<li>
- <p>If the <a href=#origin-2 id=processing-model:origin-2>origin</a> of <var>Document</var> is not a scheme/host/port tuple,
- then set <var>referrer</var> to the empty string and jump to the step labeled <i>clean
+ <p>If <var>document</var> is null, or if the <a href=#origin-2 id=processing-model:origin-2>origin</a> of <var>document</var> is not a scheme/host/port tuple,
+ then set <var>referrer</var> to the empty string and jump to the step labeled <i>cleaned
referrer</i>.</p>
<li>
@@ -4502,7 +4502,7 @@
<li>
- <p>If <var>referrer</var> is not the empty string, is not a <a href=http://tools.ietf.org/html/rfc2397#section-2 id=processing-model:data-protocol data-x-internal=data-protocol><code>data:</code> URL</a>, and is not the <a href=#url id=processing-model:url-4>URL</a>
+ <p><i>Cleaned referrer</i>: If <var>referrer</var> is not the empty string, is not a <a href=http://tools.ietf.org/html/rfc2397#section-2 id=processing-model:data-protocol data-x-internal=data-protocol><code>data:</code> URL</a>, and is not the <a href=#url id=processing-model:url-4>URL</a>
"<code id=processing-model:about:blank><a href=#about:blank>about:blank</a></code>", then generate the <i>address of the resource from which Request-URIs
are obtained</i> as required by HTTP for the <code id=processing-model:http-referer><a href=#http-referer>Referer</a></code> (sic)
header from <var>referrer</var>. <a href=#refsHTTP>[HTTP]</a></p>
@@ -60651,7 +60651,7 @@
- <h3 id=offline>7.7 Offline Web applications</h3>
+ <h3 id=offline>7.7 Offline Web applications</h3>
@@ -61529,7 +61529,7 @@
the availability of updates.<li>
<p><i>Fetching the manifest</i>: <a href=#fetch id=downloading-or-updating-an-application-cache:fetch>Fetch</a> the resource from <var>manifest URL</var> with the <i>synchronous flag</i> set, and let <var>manifest</var> be that resource. HTTP caching semantics should be honored for this
- request.</p>
+ request. The <i>override referrer source</i> must be null.</p>
<p>Parse <var>manifest</var> according to the <a href=#parse-a-manifest id=downloading-or-updating-an-application-cache:parse-a-manifest>rules for
parsing manifests</a>, obtaining a list of <a href=#concept-appcache-explicit id=downloading-or-updating-an-application-cache:concept-appcache-explicit>explicit
@@ -61671,7 +61671,7 @@
<a href=#url id=downloading-or-updating-an-application-cache:url-3>URL</a> <var>manifest URL</var>, with the <i>synchronous flag</i> set and
the <i>manual redirect flag</i> set. If this is an <a href=#concept-appcache-upgrade id=downloading-or-updating-an-application-cache:concept-appcache-upgrade-3>upgrade attempt</a>, then use the <a href=#concept-appcache-newer id=downloading-or-updating-an-application-cache:concept-appcache-newer-4>newest</a> <a href=#application-cache id=downloading-or-updating-an-application-cache:application-cache-15>application cache</a> in <var>cache group</var> as an HTTP cache, and honor HTTP caching semantics (such as
expiration, ETags, and so forth) with respect to that cache. User agents may also have other
- caches in place that are also honored.</p>
+ caches in place that are also honored. The <i>override referrer source</i> must be null.</p>
<p class=note>If the resource in question is already being downloaded for other reasons then
the existing download process can sometimes be used for the purposes of this step, as defined
@@ -61798,7 +61798,7 @@
<p><a href=#fetch id=downloading-or-updating-an-application-cache:fetch-5>Fetch</a> the resource from <var>manifest URL</var> again, with
the <i>synchronous flag</i> set, and let <var>second manifest</var> be that resource.
- HTTP caching semantics should again be honored for this request.</p>
+ HTTP caching semantics should again be honored for this request. The <i>override referrer source</i> must be null.</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
Modified: index
===================================================================
--- index 2014-09-19 17:39:29 UTC (rev 8790)
+++ index 2014-09-19 17:52:16 UTC (rev 8791)
@@ -4473,7 +4473,7 @@
<p>Let <var>document</var> be the appropriate <code id=processing-model:document><a href=#document>Document</a></code> as given by the
following list:</p>
- <dl class=switch><dt>If there is a specific <i>override referrer source</i><dd>The <i>override referrer source</i>.<dt>When <a href=#navigate id=processing-model:navigate>navigating</a><dd>The <a href=#active-document id=processing-model:active-document>active document</a> of the <a href=#source-browsing-context id=processing-model:source-browsing-context>source browsing context</a>.<dt>When fetching resources for an element<dd>The element's <a id=processing-model:node-document href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a>.</dl>
+ <dl class=switch><dt>If there is a specific <i>override referrer source</i> (which might be null)<dd>The <i>override referrer source</i>.<dt>When <a href=#navigate id=processing-model:navigate>navigating</a><dd>The <a href=#active-document id=processing-model:active-document>active document</a> of the <a href=#source-browsing-context id=processing-model:source-browsing-context>source browsing context</a>.<dt>When fetching resources for an element<dd>The element's <a id=processing-model:node-document href=https://dom.spec.whatwg.org/#concept-node-document data-x-internal=node-document>node document</a>.</dl>
<li>
@@ -4483,8 +4483,8 @@
<li>
- <p>If the <a href=#origin-2 id=processing-model:origin-2>origin</a> of <var>Document</var> is not a scheme/host/port tuple,
- then set <var>referrer</var> to the empty string and jump to the step labeled <i>clean
+ <p>If <var>document</var> is null, or if the <a href=#origin-2 id=processing-model:origin-2>origin</a> of <var>document</var> is not a scheme/host/port tuple,
+ then set <var>referrer</var> to the empty string and jump to the step labeled <i>cleaned
referrer</i>.</p>
<li>
@@ -4502,7 +4502,7 @@
<li>
- <p>If <var>referrer</var> is not the empty string, is not a <a href=http://tools.ietf.org/html/rfc2397#section-2 id=processing-model:data-protocol data-x-internal=data-protocol><code>data:</code> URL</a>, and is not the <a href=#url id=processing-model:url-4>URL</a>
+ <p><i>Cleaned referrer</i>: If <var>referrer</var> is not the empty string, is not a <a href=http://tools.ietf.org/html/rfc2397#section-2 id=processing-model:data-protocol data-x-internal=data-protocol><code>data:</code> URL</a>, and is not the <a href=#url id=processing-model:url-4>URL</a>
"<code id=processing-model:about:blank><a href=#about:blank>about:blank</a></code>", then generate the <i>address of the resource from which Request-URIs
are obtained</i> as required by HTTP for the <code id=processing-model:http-referer><a href=#http-referer>Referer</a></code> (sic)
header from <var>referrer</var>. <a href=#refsHTTP>[HTTP]</a></p>
@@ -60651,7 +60651,7 @@
- <h3 id=offline>7.7 Offline Web applications</h3>
+ <h3 id=offline>7.7 Offline Web applications</h3>
@@ -61529,7 +61529,7 @@
the availability of updates.<li>
<p><i>Fetching the manifest</i>: <a href=#fetch id=downloading-or-updating-an-application-cache:fetch>Fetch</a> the resource from <var>manifest URL</var> with the <i>synchronous flag</i> set, and let <var>manifest</var> be that resource. HTTP caching semantics should be honored for this
- request.</p>
+ request. The <i>override referrer source</i> must be null.</p>
<p>Parse <var>manifest</var> according to the <a href=#parse-a-manifest id=downloading-or-updating-an-application-cache:parse-a-manifest>rules for
parsing manifests</a>, obtaining a list of <a href=#concept-appcache-explicit id=downloading-or-updating-an-application-cache:concept-appcache-explicit>explicit
@@ -61671,7 +61671,7 @@
<a href=#url id=downloading-or-updating-an-application-cache:url-3>URL</a> <var>manifest URL</var>, with the <i>synchronous flag</i> set and
the <i>manual redirect flag</i> set. If this is an <a href=#concept-appcache-upgrade id=downloading-or-updating-an-application-cache:concept-appcache-upgrade-3>upgrade attempt</a>, then use the <a href=#concept-appcache-newer id=downloading-or-updating-an-application-cache:concept-appcache-newer-4>newest</a> <a href=#application-cache id=downloading-or-updating-an-application-cache:application-cache-15>application cache</a> in <var>cache group</var> as an HTTP cache, and honor HTTP caching semantics (such as
expiration, ETags, and so forth) with respect to that cache. User agents may also have other
- caches in place that are also honored.</p>
+ caches in place that are also honored. The <i>override referrer source</i> must be null.</p>
<p class=note>If the resource in question is already being downloaded for other reasons then
the existing download process can sometimes be used for the purposes of this step, as defined
@@ -61798,7 +61798,7 @@
<p><a href=#fetch id=downloading-or-updating-an-application-cache:fetch-5>Fetch</a> the resource from <var>manifest URL</var> again, with
the <i>synchronous flag</i> set, and let <var>second manifest</var> be that resource.
- HTTP caching semantics should again be honored for this request.</p>
+ HTTP caching semantics should again be honored for this request. The <i>override referrer source</i> must be null.</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
Modified: source
===================================================================
--- source 2014-09-19 17:39:29 UTC (rev 8790)
+++ source 2014-09-19 17:52:16 UTC (rev 8791)
@@ -6657,7 +6657,7 @@
<dl class="switch">
- <dt>If there is a specific <i>override referrer source</i></dt>
+ <dt>If there is a specific <i>override referrer source</i> (which might be null)</dt>
<dd>The <i>override referrer source</i>.</dd>
@@ -6687,8 +6687,8 @@
<li>
- <p>If the <span>origin</span> of <var>Document</var> is not a scheme/host/port tuple,
- then set <var>referrer</var> to the empty string and jump to the step labeled <i>clean
+ <p>If <var>document</var> is null, or if the <span>origin</span> of <var>document</var> is not a scheme/host/port tuple,
+ then set <var>referrer</var> to the empty string and jump to the step labeled <i>cleaned
referrer</i>.</p>
</li>
@@ -6716,7 +6716,7 @@
<li>
- <p>If <var>referrer</var> is not the empty string, is not a <span data-x="data
+ <p><i>Cleaned referrer</i>: If <var>referrer</var> is not the empty string, is not a <span data-x="data
protocol"><code>data:</code> URL</span>, and is not the <span>URL</span>
"<code>about:blank</code>", then generate the <i>address of the resource from which Request-URIs
are obtained</i> as required by HTTP for the <code data-x="http-referer">Referer</code> (sic)
@@ -81933,7 +81933,7 @@
<!--TOPIC:Offline Web Applications-->
- <h3 id="offline">Offline Web applications</h3>
+ <h3 id="offline">Offline Web applications</h3> <!--APPCACHE-->
<!-- v2 ideas for appcache:
@@ -83088,7 +83088,7 @@
<li>
<p><i>Fetching the manifest</i>: <span>Fetch</span><!--FETCH--> the resource from <var>manifest URL</var> with the <i>synchronous flag</i> set, and let <var>manifest</var> be that resource. HTTP caching semantics should be honored for this
- request.</p> <!-- http-origin privacy sensitive, though it doesn't matter, since this can never
+ request. The <i>override referrer source</i> must be null.</p> <!-- http-origin privacy sensitive, though it doesn't matter, since this can never
be cross-origin -->
<p>Parse <var>manifest</var> according to the <span data-x="parse a manifest">rules for
@@ -83322,7 +83322,7 @@
data-x="concept-appcache-upgrade">upgrade attempt</span>, then use the <span
data-x="concept-appcache-newer">newest</span> <span>application cache</span> in <var>cache group</var> as an HTTP cache, and honor HTTP caching semantics (such as
expiration, ETags, and so forth) with respect to that cache. User agents may also have other
- caches in place that are also honored.</p> <!-- not http-origin privacy sensitive -->
+ caches in place that are also honored. The <i>override referrer source</i> must be null.</p> <!-- not http-origin privacy sensitive -->
<p class="note">If the resource in question is already being downloaded for other reasons then
the existing download process can sometimes be used for the purposes of this step, as defined
@@ -83516,7 +83516,7 @@
<p><span>Fetch</span><!--FETCH--> the resource from <var>manifest URL</var> again, with
the <i>synchronous flag</i> set, and let <var>second manifest</var> be that resource.
- HTTP caching semantics should again be honored for this request.</p> <!-- http-origin privacy
+ HTTP caching semantics should again be honored for this request. The <i>override referrer source</i> must be null.</p> <!-- http-origin privacy
sensitive, though it doesn't matter, since this can never be cross-origin -->
<p class="note">Since caching can be honored, authors are encouraged to avoid setting the cache
More information about the Commit-Watchers
mailing list