3 ms·
Incorrect. The IE behavior is also wrong, just in a different way: http://www.ietf.org/rfc/rfc1945.txt http://www.ietf.org/rfc/rfc1945.txt
by ldar15 15y ago
Incorrect. The IE behavior is also wrong, just in a different way: http://www.ietf.org/rfc/rfc1945.txt http://www.ietf.org/rfc/rfc1945.txt
- dw0rm 15y agoAccording to http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.3 http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10... 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.