- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Wed, 07 Dec 2011 15:08:30 +0100
- To: Willy Tarreau <w@1wt.eu>
- CC: 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 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
Received on Wednesday, 7 December 2011 14:09:16 UTC