- From: Mark Nottingham <mnot@mnot.net>
- Date: Wed, 14 Dec 2011 15:47:46 +1100
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Cameron Heavon-Jones <cmhjones@gmail.com>, Willy Tarreau <w@1wt.eu>, "Roy T. Fielding" <fielding@gbiv.com>, Amos Jeffries <squid3@treenet.co.nz>, ietf-http-wg@w3.org
Do we have agreement that a 3xx + Location can / should trigger an automatic redirect (taking into account user notification -- a separate issue)? Regards, On 08/12/2011, at 2:50 AM, Julian Reschke wrote: > 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 > -- Mark Nottingham http://www.mnot.net/
Received on Wednesday, 14 December 2011 04:48:16 UTC