[html5] r3062 - [] (0) Update references to Origin header to match the Origin I-D again.

[whatwg at whatwg.org]

Author: ianh
Date: 2009-05-02 13:09:06 -0700 (Sat, 02 May 2009)
New Revision: 3062

Modified:
   index
   source
Log:
[] (0) Update references to Origin header to match the Origin I-D again.

Modified: index
===================================================================
--- index	2009-05-02 06:05:12 UTC (rev 3061)
+++ index	2009-05-02 20:09:06 UTC (rev 3062)
@@ -2001,6 +2001,9 @@
   <!--XXX empty title attribute is equivalent to missing attribute for
   purposes of alternative style sheet processing -->
 
+  <!-- XXX The <dfn title="http-origin"><code>Origin</code></dfn> HTTP header -->
+  <!-- http://tools.ietf.org/html/draft-abarth-origin -->
+
   </div>
 
 
@@ -46037,7 +46040,7 @@
     already been obtained<!-- it's obtained by <object>, for instance
     -->. 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>XXX-Origin</code>
+    agent must include an <code title=http-origin>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
@@ -46072,8 +46075,6 @@
     <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>XXX-Origin</code> header to become "<code title="">null</code>" on subsequent requests in the chain.</p>
-
    </li>
 
    <li><p>Wait for one or more bytes to be available or for the user
@@ -46993,12 +46994,11 @@
    nor include a <code title=http-ping-from>Ping-From</code> HTTP
    header.</dd>
 
-  </dl><p>In addition, an <code title=http-origin>XXX-Origin</code> header
+  </dl><p>In addition, an <code title=http-origin>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 <code>Document</code> containing the
-  <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>
+  <a href=#hyperlink>hyperlink</a>.</p>
 
   <p class=note>To save bandwidth, implementors might also wish to
   consider omitting optional headers such as <code>Accept</code> from

Modified: source
===================================================================
--- source	2009-05-02 06:05:12 UTC (rev 3061)
+++ source	2009-05-02 20:09:06 UTC (rev 3062)
@@ -1038,6 +1038,9 @@
   <!--XXX empty title attribute is equivalent to missing attribute for
   purposes of alternative style sheet processing -->
 
+  <!-- XXX The <dfn title="http-origin"><code>Origin</code></dfn> HTTP header -->
+  <!-- http://tools.ietf.org/html/draft-abarth-origin -->
+
   </div>
 
 
@@ -52140,7 +52143,7 @@
     already been obtained<!-- it's obtained by <object>, for instance
     -->. 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">XXX-Origin</code>
+    agent must include an <code title="http-origin">Origin</code>
     header whose value is determined as follows:</p>
 
     <dl class="switch">
@@ -52181,10 +52184,6 @@
     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">XXX-Origin</code> header to become "<code
-    title="">null</code>" on subsequent requests in the chain.</p>
-
    </li>
 
    <li><p>Wait for one or more bytes to be available or for the user
@@ -54837,16 +54836,11 @@
 
   </dl>
 
-  <p>In addition, an <code title="http-origin">XXX-Origin</code> header
+  <p>In addition, an <code title="http-origin">Origin</code> header
   must always be included, whose value is the <span title="ASCII
   serialization of an origin">ASCII serialization</span> of the
   <span>origin</span> of the <code>Document</code> containing the
-  <span>hyperlink</span>. 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 <span
-  title="origin">origins</span> of all the <span
-  title="URL">URLs</span> involved are not the <span title="same
-  origin">same</span>.</p>
+  <span>hyperlink</span>.</p>
 
   <p class="note">To save bandwidth, implementors might also wish to
   consider omitting optional headers such as <code>Accept</code> from
@@ -62866,7 +62860,7 @@
 
     <pre>0d 0a</pre>
 
-    <p class="note">The string "Origin: ", the origin, and CRLF.</p>
+    <p class="note">The string "Origin: ", the origin, and CRLF.</p> <!-- http-origin -->
 
    </li>
 
@@ -63471,7 +63465,7 @@
 
    </dd>
 
-   <dt>Origin (bytes 4f 72 69 67 69 6e)</dt>
+   <dt>Origin (bytes 4f 72 69 67 69 6e)</dt> <!-- http-origin -->
 
    <dd>