Short URL: http://html5.org/r/7436
| SVN | Bug | Comment | Time (UTC) |
|---|---|---|---|
| 7436 | 17903 | Define what happens with our HTTP headers in redirects. (Hopefully HTTP defines what happens with most headers.) | 2012-10-05 23:02 |
Index: source
===================================================================
--- source (revision 7435)
+++ source (revision 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