mcavic - 5:13 am on Aug 3, 2006 (gmt 0)
RFC 1945 and RFC 2068 specify that the client is not allowed to change the method on the redirected request. However, most existing user agent implementations treat 302 as if it were a 303 response, performing a GET on the Location field-value regardless of the original request method. The status codes 303 and 307 have been added for servers that wish to make unambiguously clear which kind of reaction is expected of the client.
Interesting. I've always used 301 and 302 to redirect after handling a POST, and the browsers have always changed the POST request to a GET, just like I wanted them to. I guess I should start using 303.
Many pre-HTTP/1.1 user agents do not understand the 303 status.
And I guess this isn't a concern, since pre-HTTP/1.1 user agents also don't understand name virtual hosts?