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: Willy Tarreau <w@1wt.eu>
Date: Wed, 14 Dec 2011 15:09:22 +0100
To: Mark Nottingham <mnot@mnot.net>
Cc: Julian Reschke <julian.reschke@gmx.de>, Cameron Heavon-Jones <cmhjones@gmail.com>, "Roy T. Fielding" <fielding@gbiv.com>, Amos Jeffries <squid3@treenet.co.nz>, ietf-http-wg@w3.org
Message-ID: <20111214140922.GA2467@1wt.eu>
On Wed, Dec 14, 2011 at 09:58:23PM +1100, Mark Nottingham wrote:
> Hi Willy,
> 
> How is Safari's behaviour more like handling 302 than 300? 300 states:
> 
> >    If the server has a preferred choice of representation, it SHOULD
> >    include the specific URI for that representation in the Location
> >    field; user agents MAY use the Location field value for automatic
> >    redirection.

In Cameron's matrix it's indicated that Safari does not redirect on 300,
while it does on almost all 3xx except 304. If we're logical, it should
apply the 300 rule to all unknown 3xx.

> Also, the use cases you talk about could be addressed by using a header other than Location (i.e., omitting Location from a 3xx response), just as 304 does.

Indeed, we could do that too.

Best regards,
Willy
Received on Wednesday, 14 December 2011 14:13:40 GMT

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