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

Re: [XHR] setRequestHeader and redirects

From: Christian Biesinger <cbiesinger@gmail.com>
Date: Sat, 25 Jun 2011 20:17:17 +0200
Message-ID: <BANLkTinqQ9LBkVS+hF00ZKBM9gbdA-HzdX9aeHYX=JFqoFKkWQ@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: public-webapps@w3.org, josh@joshmatthews.net
On Sat, Jun 25, 2011 at 8:11 PM, Anne van Kesteren <annevk@opera.com> wrote:
> It was pointed out to me that I never replied to this message from over a
> year ago:
> http://lists.w3.org/Archives/Public/public-webapps/2010JanMar/0881.html
> My apologies, that was not intended.
> It seems to me that this issue is with HTTP (if there is an issue to begin
> with) and not XMLHttpRequest. If HTTP 3xx means that the same request is to
> be issued at the new target URL, that would be the same for XMLHttpRequest.
> I suspect the fix for Gecko therefore might need some amendment to make this
> more broadly applicable than XMLHttpRequest.

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.

Received on Saturday, 25 June 2011 18:17:44 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:32 UTC