W3C home > Mailing lists > Public > public-html-commits@w3.org > April 2009

html5/spec Overview.html,1.2164,1.2165

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 27 Apr 2009 23:19:19 +0000
To: public-html-commits@w3.org
Message-Id: <E1Lya6Z-00036c-NN@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv11924

Modified Files:
	Overview.html 
Log Message:
Make pushState() affect Referer:, since otherwise analytics results would depend on when the user reloads the source page. (whatwg r3002)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2164
retrieving revision 1.2165
diff -u -d -r1.2164 -r1.2165
--- Overview.html	27 Apr 2009 19:58:58 -0000	1.2164
+++ Overview.html	27 Apr 2009 23:19:16 -0000	1.2165
@@ -4645,7 +4645,7 @@
     </dl></li>
 
   </ol><p class="note">The above algorithm is a willful violation of the
-  HTTP specification. <a href="#references">[RFC2616]</a></p>
+  HTTP specification. <a href="#references">[HTTP]</a></p>
 
 
   <h4 id="content-type-sniffing:-web-pages"><span class="secno">2.7.2 </span>Content-Type sniffing: Web pages</h4>
@@ -6185,7 +6185,10 @@
   a <a href="#scroll-to-fragid" title="navigate-fragid">fragment identifier</a> on the
   page. <span class="impl"><a href="#the-document-s-current-address">The document's current address</a>
   must be set to <a href="#the-document-s-address">the document's address</a> when the
-  <code>Document</code> is created.</span><p>When a <code>Document</code> is created by a <a href="#concept-script" title="concept-script">script</a> using the <code title="">createDocument()</code> API, <a href="#the-document-s-address">the document's
+  <code>Document</code> is created.</span><p>For purposes of generating the <i>address of the resource from
+  which Request-URIs are obtained</i> as required by HTTP for the
+  <code title="http-referer">Referer</code> (sic) header, the user
+  agent must use <a href="#the-document-s-current-address">the document's current address</a>. <a href="#references">[HTTP]</a><p>When a <code>Document</code> is created by a <a href="#concept-script" title="concept-script">script</a> using the <code title="">createDocument()</code> API, <a href="#the-document-s-address">the document's
   address</a> is the same as <a href="#the-document-s-address">the document's address</a> of
   the <a href="#active-document">active document</a> of the <a href="#script-s-browsing-context">script's browsing
   context</a>.<p><code>Document</code> objects are assumed to be <dfn id="xml-documents">XML
@@ -6302,10 +6305,10 @@
 
    <dt><var title="">document</var> . <code title="dom-document-referrer"><a href="#dom-document-referrer">referrer</a></code></dt>
    <dd>
-    <p>Returns <a href="#the-document-s-address" title="the document's address">the address</a>
-    of the <code>Document</code> from which the user navigated to this
-    one, unless it was blocked or there was no such document, in which
-    case it returns the empty string.</p>
+    <p>Returns <a href="#the-document-s-current-address" title="the document's current address">the
+    address</a> of the <code>Document</code> from which the user
+    navigated to this one, unless it was blocked or there was no such
+    document, in which case it returns the empty string.</p>
     <p>The <code title="link-type-noreferrer">noreferrer</code> link
     type can be used to block the referrer.</p>
    </dd>
@@ -6316,10 +6319,10 @@
   attribute must return <a href="#the-document-s-address">the document's address</a>.</p>
 
   <p>The <dfn id="dom-document-referrer" title="dom-document-referrer"><code>referrer</code></dfn> attribute
-  must return either the <a href="#the-document-s-address" title="the document's
-  address">address</a> of the <a href="#active-document">active document</a> of the
-  <a href="#source-browsing-context">source browsing context</a> at the time the navigation was
-  started (that is, the page which <a href="#navigate" title="navigate">navigated</a> the <a href="#browsing-context">browsing context</a>
+  must return either the <a href="#the-document-s-current-address" title="the document's current
+  address">current address</a> of the <a href="#active-document">active document</a>
+  of the <a href="#source-browsing-context">source browsing context</a> <em>at the time the
+  navigation was started</em> (that is, the page which <a href="#navigate" title="navigate">navigated</a> the <a href="#browsing-context">browsing context</a>
   to the current document), or the empty string if there is no such
   originating page, or if the UA has been configured not to report
   referrers in this case, or if the navigation was initiated for a
@@ -8992,7 +8995,7 @@
   the order that they were given in the HTTP entity header.  (URIs in
   these headers are to be processed and resolved according to the
   rules given in HTTP; the rules of <em>this</em> specification don't
-  apply.) <a href="#references">[RFC2616]</a> <a href="#references">[RFC2068]</a></p>
+  apply.) <a href="#references">[HTTP]</a> <a href="#references">[RFC2068]</a></p>
 
   <p>The DOM attributes <dfn id="dom-link-href" title="dom-link-href"><code>href</code></dfn>, <dfn id="dom-link-rel" title="dom-link-rel"><code>rel</code></dfn>, <dfn id="dom-link-media" title="dom-link-media"><code>media</code></dfn>, <dfn id="dom-link-hreflang" title="dom-link-hreflang"><code>hreflang</code></dfn>, and <dfn id="dom-link-type" title="dom-link-type"><code>type</code></dfn>, and <dfn id="dom-link-sizes" title="dom-link-sizes"><code>sizes</code></dfn> each must
   <a href="#reflect">reflect</a> the respective content attributes of the same
@@ -9305,7 +9308,7 @@
 
     <p class="note">This pragma is not exactly equivalent to the HTTP
     <code>Content-Language</code> header, for instance it only
-    supports one language. <a href="#references">[RFC2616]</a></p>
+    supports one language. <a href="#references">[HTTP]</a></p>
 
    </dd>
 
@@ -41538,11 +41541,12 @@
    encrypted connection</dt>
 
    <dd>The request must include a <code title="">Referer</code> (sic)
-   HTTP header [sic] with, as its value, the <a href="#the-document-s-address" title="the
-   document's address">address</a> of the document containing the
-   hyperlink, a <code title="http-ping-from">Ping-From</code> HTTP
-   header with the same value, and a <code title="http-ping-to">Ping-To</code> HTTP header with, as its value,
-   the address of the target of the hyperlink.</dd>
+   HTTP header [sic] with, as its value, the <a href="#the-document-s-current-address" title="the
+   document's current address">current address</a> of the document
+   containing the hyperlink, a <code title="http-ping-from">Ping-From</code> HTTP header with the same
+   value, and a <code title="http-ping-to">Ping-To</code> HTTP header
+   with, as its value, the address of the target of the
+   hyperlink.</dd>
 
    <dt>Otherwise, the origins are different and the document
    containing the hyperlink being audited was retrieved over an
Received on Monday, 27 April 2009 23:19:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 23:19:31 GMT