15228 2011-12-16 10:04:09 +0000 Be more explicit about headers in redirects. 2012-10-14 12:59:12 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#fetching-resources P3 normal --- 1 contributor silviapfeiffer1 annevk ian mike public-html-admin public-html-wg-issue-tracking silviapfeiffer1 public-html-bugzilla oldest_to_newest 61652 0 contributor 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 61653 1 annevk 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. 61654 2 annevk 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 63252 3 ian 2012-01-28 22:07:12 +0000 So... what do I put in the spec here? 63492 4 ian 2012-02-01 00:21:23 +0000 (waiting for anne's return) 63606 5 annevk 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)". 70275 6 contributor 2012-07-18 07:15:13 +0000 This bug was cloned to create bug 17903 as part of operation convergence. 76252 7 silviapfeiffer1 2012-10-14 12:59:12 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy-v2.html Status: Accepted Change Description: https://github.com/w3c/html/commit/1cae474ed786803cdca2b15bcadecc41ed9afa3c Rationale: accepted WHATWG change