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

Re: #160: Redirects and non-GET methods

From: Mark Nottingham <mnot@mnot.net>
Date: Mon, 18 Jul 2011 20:54:20 +1000
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <8243D01D-0257-4174-BAA2-715FB19F4A3E@mnot.net>
To: Yves Lafon <ylafon@w3.org>

On 18/07/2011, at 7:23 PM, Yves Lafon wrote:

>> ? Safari/533.21.1 - all 301, 302, 307 rewritten to GET; 303 methods are preserved
>> ? Firefox/5.0.1 - all 301, 302 rewritten to GET; 303 and 307 methods are preserved
>> ? Chrome/14.0.814.0 - all 301, 302 rewritten to GET; 303 and 307 methods are preserved
>> ? Opera/11.50 - all 301, 302 rewritten to GET; 303 methods are preserved; 307 tests crash the browser
>> ? MSIE/9.0 (latest) - all 301, 302 methods preserved except POST (changed to GET); all 303, 307 methods are preserved
>> 
>> So, many browsers rewrite many methods to GET on 301 and 302. whereas most browsers preserve methods on 303 and 307*.
> 
> Note that the results above are for the XHR-based test.
> I tried 307 for POST "natively"
> * For Opera/11.50 POST -> 307, popup to chose to redirect while preserving
>  the method.
> * For Safari 5.0.5 (6533.21.1), POST redirected without a prompt to
>  another POST on the new URI.
> * Firefox/5.0.1 redirect 307 preserving the method, and warn the user.


How are those different (besides not crashing Opera, of course)?


--
Mark Nottingham   http://www.mnot.net/
Received on Monday, 18 July 2011 10:54:50 GMT

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