1339 | | <x:h>Note:</x:h> <xref target="RFC1945"/> and <xref target="RFC2068"/> specify that the client is not allowed |
1340 | | to change the method on the redirected request. However, most |
1341 | | existing user agent implementations treat 302 as if it were a 303 |
1342 | | response, performing a GET on the Location field-value regardless |
1343 | | of the original request method. The status codes 303 and 307 have |
1344 | | been added for servers that wish to make unambiguously clear which |
1345 | | kind of reaction is expected of the client. |
| 1339 | <x:h>Note:</x:h> HTTP/1.0 (<xref target="RFC1945" x:fmt="," x:sec="9.3"/>) |
| 1340 | and the first version of HTTP/1.1 (<xref target="RFC2068" x:fmt="," x:sec ="10.3.3"/>) |
| 1341 | specify that the client is not allowed to change the method on the |
| 1342 | redirected request. However, most existing user agent implementations |
| 1343 | treat 302 as if it were a 303 response, performing a GET on the Location |
| 1344 | field-value regardless of the original request method. Therefore, a |
| 1345 | previous version of this specification |
| 1346 | (<xref target="RFC2616" x:fmt="," x:sec="10.3.3"/>) has added the |
| 1347 | status codes |
| 1348 | <xref target="status.303" format="none">303</xref> and |
| 1349 | <xref target="status.307" format="none">307</xref> for servers that wish |
| 1350 | to make unambiguously clear which kind of reaction is expected of the |
| 1351 | client. |