[html5] r4692 - [e] (0) Add a note to the 'fetch' algorithm about redirects. I'm sure it'll need [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2010-02-12 01:50:27 -0800 (Fri, 12 Feb 2010)
New Revision: 4692

Modified:
   complete.html
   index
   source
Log:
[e] (0) Add a note to the 'fetch' algorithm about redirects. I'm sure it'll need tweaking later, since browsers ignore HTTP here for compatibility with deployed content. Also, tweak the W3C postmsg draft's boilerplate.

Modified: complete.html
===================================================================
--- complete.html	2010-02-11 11:12:48 UTC (rev 4691)
+++ complete.html	2010-02-12 09:50:27 UTC (rev 4692)
@@ -157,7 +157,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
    <hgroup><h1>Web Applications 1.0</h1>
-    <h2 class="no-num no-toc">Draft Standard — 11 February 2010</h2>
+    <h2 class="no-num no-toc">Draft Standard — 12 February 2010</h2>
    </hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
    <p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
    <!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -5240,6 +5240,10 @@
     redirects, <a href=#concept-js-deref title=concept-js-deref>dereferencing <span title="javascript protocol"><code title="">javascript:</code>
     URLs</span></a>, etc).</p>
 
+    <p class=note>The HTTP specification requires that 301, 302, and
+    307 redirects, when applied to methods other than GET or HEAD, not
+    be followed without user confirmation.</p>
+
     <p>For the purposes of the <code title=http-referer>Referer</code> (sic) header, use the
     <i>address of the resource from which Request-URIs are
     obtained</i> generated in the earlier step.</p>

Modified: index
===================================================================
--- index	2010-02-11 11:12:48 UTC (rev 4691)
+++ index	2010-02-12 09:50:27 UTC (rev 4692)
@@ -159,7 +159,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
    <hgroup><h1>HTML5 (including next generation additions still in development)</h1>
-    <h2 class="no-num no-toc">Draft Standard — 11 February 2010</h2>
+    <h2 class="no-num no-toc">Draft Standard — 12 February 2010</h2>
    </hgroup><p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
    <p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
    <!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -5139,6 +5139,10 @@
     redirects, <a href=#concept-js-deref title=concept-js-deref>dereferencing <span title="javascript protocol"><code title="">javascript:</code>
     URLs</span></a>, etc).</p>
 
+    <p class=note>The HTTP specification requires that 301, 302, and
+    307 redirects, when applied to methods other than GET or HEAD, not
+    be followed without user confirmation.</p>
+
     <p>For the purposes of the <code title=http-referer>Referer</code> (sic) header, use the
     <i>address of the resource from which Request-URIs are
     obtained</i> generated in the earlier step.</p>

Modified: source
===================================================================
--- source	2010-02-11 11:12:48 UTC (rev 4691)
+++ source	2010-02-12 09:50:27 UTC (rev 4692)
@@ -4766,6 +4766,10 @@
     title="javascript protocol"><code title="">javascript:</code>
     URLs</span></span>, etc).</p>
 
+    <p class="note">The HTTP specification requires that 301, 302, and
+    307 redirects, when applied to methods other than GET or HEAD, not
+    be followed without user confirmation.</p>
+
     <p>For the purposes of the <code
     title="http-referer">Referer</code> (sic) header, use the
     <i>address of the resource from which Request-URIs are