RE: Proposed fix for issued 140: 301

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].

James Manger
Identity and security team — Chief Technology Office — Telstra

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