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

RE: Proposed fix for issued 140: 301

From: Manger, James H <James.H.Manger@team.telstra.com>
Date: Mon, 20 Jul 2009 11:19:10 +1000
To: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <255B9BB34FB7D647A506DC292726F6E11225D33DAF@WSMSG3153V.srv.dir.telstra.com>
Browsers (eg Firefox 3.5 & IE8) seem to change the method (eg POST to GET) on 301 "Moved Permanently" redirects as well as on 302 "Found" redirects even with HTTP/1.1 requests & responses, contradicting the spec.

The spec sections on 301 & 302 each have a note about the mismatches -- but the notes are different. The 302 note says "most existing user agents" change the method, while the 301 note says "some existing HTTP/1.0 user agents" change the method. The 301 note does not seem to reflect reality.

I am NOT suggesting a new status code (308 "Permanently Redirect") for unambiguous semantics -- using 307 "Temporary Redirect" with Cache-Control should be close enough.

Perhaps the new text for the 302 note should also be used for the 301 note [issue #140 http://trac.tools.ietf.org/wg/httpbis/trac/ticket/140].


James Manger
James.H.Manger@team.telstra.com
Identity and security team — Chief Technology Office — Telstra

Received on Monday, 20 July 2009 01:20:03 GMT

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