- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sun, 26 Jun 2011 01:05:10 +0200
- To: Anne van Kesteren <annevk@opera.com>
- CC: Christian Biesinger <cbiesinger@gmail.com>, public-webapps@w3.org, josh@joshmatthews.net
On 2011-06-25 20:23, Anne van Kesteren wrote: > 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? I can confirm that HTTP doesn't tell you the answer. I'm not sure it' *supposed* to tell you. Maybe the proper fix is to have APIs where following redirects is controller by the caller? Best regards, Julian
Received on Saturday, 25 June 2011 23:06:02 UTC