[] (0) Define what happens with our HTTP headers in redirects. (Hopef…

…ully HTTP defines what happens with most headers.) Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=17903 Affected topics: HTML git-svn-id: http://svn.whatwg.org/webapps@7436 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Oct 5, 2012 · eed7391 · eed7391
1 parent 965220b
commit eed7391
Show file tree

Hide file tree

Showing 3 changed files with 16 additions and 12 deletions.
diff --git a/complete.html b/complete.html
@@ -8549,10 +8549,11 @@ <h4 id=processing-model><span class=secno>2.7.2 </span>Processing model</h4>
 
      <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

diff --git a/index b/index
@@ -8549,10 +8549,11 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
 
      <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

diff --git a/source b/source
@@ -8490,10 +8490,12 @@ is conforming depends on which specs apply, and leaves it at that. -->
 
      <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