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

Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 07 Dec 2011 16:50:39 +0100
Message-ID: <4EDF8B4F.90507@gmx.de>
To: Cameron Heavon-Jones <cmhjones@gmail.com>
CC: Willy Tarreau <w@1wt.eu>, Mark Nottingham <mnot@mnot.net>, "Roy T. Fielding" <fielding@gbiv.com>, Amos Jeffries <squid3@treenet.co.nz>, ietf-http-wg@w3.org
On 2011-12-07 16:43, Cameron Heavon-Jones wrote:
> On 07/12/2011, at 2:08 PM, Julian Reschke wrote:
>
>> On 2011-12-07 14:45, Willy Tarreau wrote:
>>> ...
>>> I don't think we should say something like this. For instance a new 3xx
>>> might provide a Location header which would only be conditionnally used.
>>> Requiring UAs to process 3xx like 302 if they see a Location header seems
>>> problematic for the long term.
>>>
>>> Why not say that a Location header might be used in conjunction with new 3xx
>>> headers but UAs must not use it unless they understand this 3xx ?
>>> ...
>>
>> Well, the question is what UAs should do with a 3xx + Location. AFAIR, Safari follows the redirect, while others do not.
>>
>> Safari's behavior is "good" as it would allow to define 308 (as the permanent version of 307), and nothing needs to be changed in the browser.
>>
>> Best regards, Julian
>>
>
> these test results might be of interest:
>
> http://www.cmhjones.com/browser-http-test-matrix.html

...so Safari follows an unknown redirect only if the response doesn't 
have a payload.

Best regards, Julian
Received on Wednesday, 7 December 2011 15:51:26 GMT

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