W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2011

Re: Redirects and headers

From: Mark Baker <distobj@acm.org>
Date: Mon, 4 Jul 2011 12:19:24 -0400
Message-ID: <CALcoZirLJ10mb1mc90v0r90iALATckW8nC9Xi6XzOWarKfx0kw@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Mark Nottingham <mnot@mnot.net>, Anne van Kesteren <annevk@opera.com>, HTTP WG <ietf-http-wg@w3.org>
On Mon, Jul 4, 2011 at 11:15 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
> On 2011-07-04 16:34, Mark Baker wrote:
>>
>> FWIW, I can't, off-hand, think of anything that would need to be said
>> about this in the specification for the HTTP protocol.  The meaning of
>> the redirect should be clear from the definition of the status code,
>> and only the client is in a position to understand how to react to
>> such a message when crafting a follow-on request.
>
> Well, the issue is that we have middleware/tools that follow the redirect
> automatically (XHR), thus may not know that "the client's" intent was...

Understood. But IMO, the solution to the problem Anne describes is to
build a better API (and better implementations of that API).

Mark.
Received on Monday, 4 July 2011 16:19:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:43 GMT