This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This was was cloned from bug 15228 as part of operation convergence. Originally filed: 2011-12-16 10:04:00 +0000 ================================================================================ #0 contributor@whatwg.org 2011-12-16 10:04:09 +0000 -------------------------------------------------------------------------------- Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/fetching-resources.html Multipage: http://www.whatwg.org/C#fetching-resources Complete: http://www.whatwg.org/c#fetching-resources Comment: Be more explicit about headers in redirects. Posted from: 83.85.115.123 by annevk@opera.com User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.7.2; U; en) Presto/2.10.229 Version/11.60 ================================================================================ #1 Anne 2011-12-16 10:05:55 +0000 -------------------------------------------------------------------------------- Apparently it depends on the header whether it is preserved in redirects or not and it is not possible to make a general rule for them. However, all headers have to deal with ("author request headers" in XMLHttpRequest, Last-Event-ID, Ping-To, Ping-From) need to be preserved across redirects so we should make that extra clear in the fetching algorithm. ================================================================================ #2 Anne 2011-12-16 10:07:01 +0000 -------------------------------------------------------------------------------- See also: http://lists.w3.org/Archives/Public/ietf-http-wg/2011OctDec/0420.html http://lists.w3.org/Archives/Public/ietf-http-wg/2011OctDec/0441.html ================================================================================ #3 Ian 'Hixie' Hickson 2012-01-28 22:07:12 +0000 -------------------------------------------------------------------------------- So... what do I put in the spec here? ================================================================================ #4 Ian 'Hixie' Hickson 2012-02-01 00:21:23 +0000 -------------------------------------------------------------------------------- (waiting for anne's return) ================================================================================ #5 Anne 2012-02-02 18:32:00 +0000 -------------------------------------------------------------------------------- Something along the lines of "when following a redirect, include each header included in the original request, unless there are specific requirements for the header in question (e.g. Referer changes during redirects)". ================================================================================
Ok.
Checked in as WHATWG revision r7436. Check-in comment: Define what happens with our HTTP headers in redirects. (Hopefully HTTP defines what happens with most headers.) http://html5.org/tools/web-apps-tracker?from=7435&to=7436