W3C home > Mailing lists > Public > public-html-diffs@w3.org > January 2009

spec/Overview.html 1.1839 2669 Rename the 'Origin' header to 'XXX-Origi

From: poot <cvsmail@w3.org>
Date: Thu, 15 Jan 2009 07:08:44 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20090114220845.1FC922BC79@toro.w3.mag.keio.ac.jp>

Rename the 'Origin' header to 'XXX-Origin' for now, pending a conclusion
from public-webapps. (whatwg r2669)

Fragment identifiers: If the absolute URL of the new resource is the same as the address of the active document of the browsing context being navigated, ignoring any <fragment> components of those URLs, and the new resource is to be fetched using HTTP GET or equivalent, then navigate to that fragment identifier and abort these steps.
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1839.html#navigate-fragid-step
5.11.2.1 Hyperlink auditing
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1839.html#hyperlink-auditing

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1838&r2=1.1839&f=h
http://html5.org/tools/web-apps-tracker?from=2668&to=2669

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1838
retrieving revision 1.1839
diff -u -d -r1.1838 -r1.1839
--- Overview.html	14 Jan 2009 20:41:19 -0000	1.1838
+++ Overview.html	14 Jan 2009 22:05:54 -0000	1.1839
@@ -31142,7 +31142,7 @@
     <p>Otherwise, <a href=#fetch>fetch</a> the new resource. If the resource
     is being fetched using HTTP, and the method is not GET<!-- or HEAD
     (but that can't happen) -->, then the user agent must include an
-    <code title=http-origin>Origin</code> header whose value is
+    <code title=http-origin>XXX-Origin</code> header whose value is
     determined as follows:</p>
 
     <dl class=switch><dt>If the <a href=#navigate title=navigate>navigation</a> algorithm has
@@ -31177,7 +31177,7 @@
     <p>If fetching the resource results in a redirect, return to <a href=#navigate-fragid-step>the step labeled "fragment
     identifiers"</a> with the new resource.</p>
 
-    <p class=note>Cross-origin redirects cause the <code title=http-origin>Origin</code> header to become "<code title="">null</code>" on subsequent requests in the chain.</p>
+    <p class=note>Cross-origin redirects cause the <code title=http-origin>XXX-Origin</code> header to become "<code title="">null</code>" on subsequent requests in the chain.</p>
 
    </li>
 
@@ -32702,11 +32702,11 @@
    include a <code title=http-ping-from>Ping-From</code> HTTP
    header.</dd>
 
-  </dl><p>In addition, an <code title=http-origin>Origin</code> header
+  </dl><p>In addition, an <code title=http-origin>XXX-Origin</code> header
   must always be included, whose value is the <a href=#ascii-serialization-of-an-origin title="ASCII
   serialization of an origin">ASCII serialization</a> of the
   <a href=#origin-0>origin</a> of the the <code>Document</code> containing the
-  <a href=#hyperlink>hyperlink</a>. The value of the <code title=http-origin>Origin</code> header must be set to "<code title="">null</code>" when following redirects if the <a href=#origin-0 title=origin>origins</a> of all the <a href=#url title=URL>URLs</a> involved are not the <a href=#same-origin title="same
+  <a href=#hyperlink>hyperlink</a>. The value of the <code title=http-origin>XXX-Origin</code> header must be set to "<code title="">null</code>" when following redirects if the <a href=#origin-0 title=origin>origins</a> of all the <a href=#url title=URL>URLs</a> involved are not the <a href=#same-origin title="same
   origin">same</a>.<p class=note>To save bandwidth, implementors might also wish to
   consider omitting optional headers such as <code>Accept</code> from
   these requests.<p>User agents must, unless otherwise specified by the user, honor
Received on Wednesday, 14 January 2009 22:09:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:13:57 GMT