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

html5/spec Overview.html,1.2220,1.2221

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Sat, 02 May 2009 20:09:16 +0000
To: public-html-commits@w3.org
Message-Id: <E1M0LWO-00037a-C0@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv11973

Modified Files:
	Overview.html 
Log Message:
Update references to Origin header to match the Origin I-D again. (whatwg r3062)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2220
retrieving revision 1.2221
diff -u -d -r1.2220 -r1.2221
--- Overview.html	2 May 2009 06:05:17 -0000	1.2220
+++ Overview.html	2 May 2009 20:09:13 -0000	1.2221
@@ -1785,6 +1785,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><div class="impl">
 
   <h4 id="common-conformance-requirements-for-apis-exposed-to-javascript"><span class="secno">2.2.3 </span>Common conformance requirements for APIs exposed to
@@ -41245,7 +41248,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
@@ -41280,8 +41283,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
@@ -42160,12 +42161,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
Received on Saturday, 2 May 2009 20:09:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 2 May 2009 20:09:25 GMT