W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

Re: [XHR] setRequestHeader and redirects

From: Anne van Kesteren <annevk@opera.com>
Date: Sat, 25 Jun 2011 20:23:07 +0200
To: "Christian Biesinger" <cbiesinger@gmail.com>, "Julian Reschke" <julian.reschke@gmx.de>
Cc: public-webapps@w3.org, josh@joshmatthews.net
Message-ID: <op.vxm9cttf64w2qv@anne-van-kesterens-macbook-pro.local>
On Sat, 25 Jun 2011 20:17:17 +0200, Christian Biesinger  
<cbiesinger@gmail.com> wrote:
> Well it's clearly not the same request. You'll get different cookie
> headers, for example... HTTP doesn't really deal with an API to set
> headers. It feels like the higher level API, in this case
> XMLHttpRequest, needs to specify what the behaviour should be.

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?

Is that the case Julian?


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Saturday, 25 June 2011 18:23:48 GMT

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