W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2012

Re: [XHR] setRequestHeader and redirects

From: Anne van Kesteren <annevk@opera.com>
Date: Mon, 06 Feb 2012 19:33:31 +0100
To: public-webapps@w3.org, "Boris Zbarsky" <bzbarsky@mit.edu>, "cbiesinger@gmail.com" <cbiesinger@gmail.com>
Message-ID: <op.v89sh5x464w2qv@annevk-macbookpro.local>
On Sat, 02 Jul 2011 10:13:25 +0200, Anne van Kesteren <annevk@opera.com>  
wrote:
> On Sun, 26 Jun 2011 16:46:23 +0200, Boris Zbarsky <bzbarsky@mit.edu>  
> wrote:
>> On 6/25/11 2:23 PM, Anne van Kesteren wrote:
>>> So each specification that deals with custom headers of some kind (e.g.
>>> EventSource has Last-Event-ID and Cache-Control) needs to say what
>>> happens to them in the face of redirects?
>>
>> On the face of it, yes.  Especially because different redirect response  
>> codes have different semantics (well, in theory), so some headers may  
>> need to be preserved across some of them but not others.  And without  
>> knowing the meaning of the header, it's impossible to say when it  
>> should be preserved across the redirect and when it only makes sense in  
>> the context of the original request.
>
> I raised this with the HTTP WG:
>
> http://lists.w3.org/Archives/Public/ietf-http-wg/2011AprJun/0489.html
>
> It seems they are going to do something about it:
>
> http://lists.w3.org/Archives/Public/ietf-http-wg/2011AprJun/0490.html
>
> I guess we should evaluate again when that is done.

This ended up coming back to us. HTML fetching will hopefully address this  
issue:

https://www.w3.org/Bugs/Public/show_bug.cgi?id=15228


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Monday, 6 February 2012 18:34:03 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:50 GMT