[html5] r7436 - [] (0) Define what happens with our HTTP headers in redirects. (Hopefully HTTP d [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2012-10-05 16:02:56 -0700 (Fri, 05 Oct 2012)
New Revision: 7436

Modified:
   complete.html
   index
   source
Log:
[] (0) Define what happens with our HTTP headers in redirects. (Hopefully HTTP defines what happens with most headers.)
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=17903
Affected topics: HTML

Modified: complete.html
===================================================================
--- complete.html	2012-10-05 22:50:23 UTC (rev 7435)
+++ complete.html	2012-10-05 23:02:56 UTC (rev 7436)
@@ -8549,10 +8549,11 @@
 
      <dd>
 
-      <p>First, apply any relevant requirements for redirects (such as
-      showing any appropriate prompts). Then, redo <i>main step</i>,
-      but using the target of the redirect as the resource to fetch,
-      rather than the original resource.</p>
+      <p>First, apply any relevant requirements for redirects (such as showing any appropriate
+      prompts). Then, redo <i>main step</i>, but using the target of the redirect as the resource to
+      fetch, rather than the original resource. For HTTP requests, the new request must include the
+      same headers as the original request, except for headers for which other requirements are
+      specified (such as the <code title=http-host>Host</code> header). <a href=#refsHTTP>[HTTP]</a></p>
 
       <p class=note>The HTTP specification requires that 301, 302,
       and 307 redirects, when applied to methods other than the safe

Modified: index
===================================================================
--- index	2012-10-05 22:50:23 UTC (rev 7435)
+++ index	2012-10-05 23:02:56 UTC (rev 7436)
@@ -8549,10 +8549,11 @@
 
      <dd>
 
-      <p>First, apply any relevant requirements for redirects (such as
-      showing any appropriate prompts). Then, redo <i>main step</i>,
-      but using the target of the redirect as the resource to fetch,
-      rather than the original resource.</p>
+      <p>First, apply any relevant requirements for redirects (such as showing any appropriate
+      prompts). Then, redo <i>main step</i>, but using the target of the redirect as the resource to
+      fetch, rather than the original resource. For HTTP requests, the new request must include the
+      same headers as the original request, except for headers for which other requirements are
+      specified (such as the <code title=http-host>Host</code> header). <a href=#refsHTTP>[HTTP]</a></p>
 
       <p class=note>The HTTP specification requires that 301, 302,
       and 307 redirects, when applied to methods other than the safe

Modified: source
===================================================================
--- source	2012-10-05 22:50:23 UTC (rev 7435)
+++ source	2012-10-05 23:02:56 UTC (rev 7436)
@@ -8490,10 +8490,12 @@
 
      <dd>
 
-      <p>First, apply any relevant requirements for redirects (such as
-      showing any appropriate prompts). Then, redo <i>main step</i>,
-      but using the target of the redirect as the resource to fetch,
-      rather than the original resource.</p>
+      <p>First, apply any relevant requirements for redirects (such as showing any appropriate
+      prompts). Then, redo <i>main step</i>, but using the target of the redirect as the resource to
+      fetch, rather than the original resource. For HTTP requests, the new request must include the
+      same headers as the original request, except for headers for which other requirements are
+      specified (such as the <code title="http-host">Host</code> header). <a
+      href="#refsHTTP">[HTTP]</a></p>
 
       <p class="note">The HTTP specification requires that 301, 302,
       and 307 redirects, when applied to methods other than the safe